Levels ReadyTheme and HTML H1 Tag

[joseibarra]

We have a non ReadyTheme store and are moving some of it (categories/products) to a new store using a Levels ReadyTheme.

In our current store when we made a category we built into the category header what we think is an effect HTML H1 tag - every category comes with a H1 tag built in.

We see in the Levels ReadyTheme that Miva wants to add it's own H1 tag that is really the category Name field.

Since the category we are bringing over from our old store already has a H1 the new store shows two H1s on our category pages. I'm pretty sure that two H1s is not a good idea and those HTML analyzers would be quick to point out the problem of multiple H1s on a page.

Since we believe that H1 tags are important for SEO we have worded them carefully and prefer our better H1 words to just using the category name.

I see in the ReadyTheme admin User Interface, Settings, Global Header where I might just comment out the H1 that Miva sticks in leaving the H1 in our category header.

Is there any reason not to comment out that little H1 section in the Global Header, is there a better idea, has this already been talked about someplace else with better ideas?

[Matt Zimmermann]

Correct, more than one H1 tag on a page is bad form, especially from an SEO standpoint. In Levels, the H1 tag for the category page is contained in the Header code for the page itself. You could either comment out the existing tag, remove it, or replace it with your custom code.

[joseibarra]

I got it on the CTGY page in the Header & Footter section I commented out the H1 like this:

<mvt:comment>
<h1 class="column whole large-np page-title">&mvte:category:name;</h1>
</mvt:comment>

Much better now and maybe needed in more places later...

[William Davis]

We have a non ReadyTheme store and are moving some of it (categories/products) to a new store using a Levels ReadyTheme.

In our current store when we made a category we built into the category header what we think is an effect HTML H1 tag - every category comes with a H1 tag built in.

We see in the Levels ReadyTheme that Miva wants to add it's own H1 tag that is really the category Name field.

Since the category we are bringing over from our old store already has a H1 the new store shows two H1s on our category pages. I'm pretty sure that two H1s is not a good idea and those HTML analyzers would be quick to point out the problem of multiple H1s on a page.

Since we believe that H1 tags are important for SEO we have worded them carefully and prefer our better H1 words to just using the category name.

I see in the ReadyTheme admin User Interface, Settings, Global Header where I might just comment out the H1 that Miva sticks in leaving the H1 in our category header.

Is there any reason not to comment out that little H1 section in the Global Header, is there a better idea, has this already been talked about someplace else with better ideas?

I might be mistaken and thus you should confirm this, but it is my understanding that there will be some upcoming changes to all ReadyThemes frameworks wherein it may be best to postpone committing to current framework version until new version is released.

[lesliekirk]

I might be mistaken and thus you should confirm this, but it is my understanding that there will be some upcoming changes to all ReadyThemes frameworks wherein it may be best to postpone committing to current framework version until new version is released.

While there may be changes coming out, I don't think there is going to be an easy way to update to the latest version. When you apply a ReadyThemes framework it overwrites the existing framework. Still hoping that Miva can come up with a child theme configuration like what WordPress has.

[William Davis]

While there may be changes coming out, I don't think there is going to be an easy way to update to the latest version. When you apply a ReadyThemes framework it overwrites the existing framework. Still hoping that Miva can come up with a child theme configuration like what WordPress has.

Unless I misunderstood what your saying, that is exactly why I suggested to consider the possibility of postponing their project until Miva releases their framework updates. I've had some framework update experience, its not at all easy especially if you have made many changes to existing framework.

As to "child theme configuration similar to WordPress, I would not be at all surprise if those discussions have already taken place, it just a matter project-prioritization based on a mix of multiple strategic initiatives.

[lesliekirk]

Unless I misunderstood what your saying, that is exactly why I suggested to consider the possibility of postponing their project until Miva releases their framework updates. I've had some framework update experience, its not at all easy especially if you have made many changes to existing framework.

As to "child theme configuration similar to WordPress, I would not be at all surprise if those discussions have already taken place, it just a matter project-prioritization based on a mix of multiple strategic initiatives.

Sometimes projects can't wait for updates.

Yes, I would hope that Miva continues the discussions about "child themes", I've been squawking about needing them for a LONG time now.

[AHerb]

I got it on the CTGY page in the Header & Footter section I commented out the H1 like this:

<mvt:comment>
<h1 class="column whole large-np page-title">&mvte:category:name;</h1>
</mvt:comment>

Much better now and maybe needed in more places later...

I would say that it worth spending some time and removing H1 from category itself. It'll never come back to the old standard, but all your future migrations, all your new categories in the future will require extra work.