June 12, 2018 at 15:58 UTC - Views: 21 #54960
We do SEO for some of our clients and all our Xtreme sites are getting flagged by our SEO reporting software as having duplicate H1 tags. When you look at the source for a page, it looks as though Xtreme puts the site title and tagline in an H1 tagl:
<h1 id=”site-title” class=”hide font-inherit”>Nick Irelan-Hill Painter & Decorator in Chippenham</h1>
Is there any way around this please? Other themes we use don’t do this. Ideally we’ll be able to set unique H1 tags for each page.
AndyJune 12, 2018 at 20:31 UTC - Views: 17 #54966
The h1 polemic has been discussed to death (search the forum)
Final words, this is not a legitimate concern and should be ignoredJune 13, 2018 at 15:51 UTC - Views: 12 #54982
The discussions where this has been done to death date back over the passed few years…things change and evolve in the SEO world as we all know. Could it be that duplicate H1 tags are an issue now when they possibly weren’t? I’m inclined to trust a report coming from a dedicated ‘premium’ SEO tool. We’re working on trying to get our clients sites as technically sound as possible from an SEO perspective.
I appreciate a comment that Bruce makes on an earlier thread saying that updating the theme to change the way it puts the site title in H1 would potentially affect 10s of thousands of sites. Could you consider a checkbox that allows a user to take the H1 tag out if they want to?
If the subject keeps coming up then this could be a good solution??
AndyJune 13, 2018 at 16:41 UTC - Views: 11 #54987
I will let @weaver comment if he deems necessary, but as far as I know things have not changed in the h1 regards.June 13, 2018 at 17:05 UTC - Views: 8 #54989
There is nothing to be changed. As far as I know, the H1 thing is still a myth.
As recently as a year ago, a person of some note at Google said “Use as many H1 tags as you want”.
While not all themes do this, Weaver Xtreme always wraps the site title in an H1. It also uses an H1 for the page title (but not blog pages).
But the Google response seems to be the ultimate answer, still.
And the current use complies with HTML5, which is nearly 100% used these days.
You must be logged in to reply to this topic.