-
Notifications
You must be signed in to change notification settings - Fork 9.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
new audit: only a single h1 on a page #7208
Comments
@rviscomi wdyt |
@Onderhond do you have any supporting documentation that not having 1 H1 is bad? For example this video by John Mueller suggests that it doesn't really matter either way: https://www.youtube.com/watch?v=WsgrSxCmMbM |
Ah! Given that's the stance, I think we can close this proposal. |
Two things: 1/ the video talks about using multiple h1 elements, not about not using any. There's a big difference there. So yeah, I still think it's very relevant to have at least one h1 one a page, there's nothing in the video contradicting that or making it sound like it doesn't matter. Furthermore, using just h1 tags probably has some accessibility impact too. Here's a pretty nice rundown of the current situation: https://www.hobo-web.co.uk/headers/
I know SEO is a bit of black box wizardry, but everything I've read so far seems to indicate that having at least one h1 tag on a page is beneficial. @paulirish also noticed you changed the topic of this post to something it wasn't about. This is not about multiple h1 tags on a single page, it's about having at least one of them on a single page. |
Chatted with someone from the Search team about this. They suggested a generalized version of this feature request that validates that there is at least one heading element on the page (H1-H6). @Onderhond does that sound good to you? |
🛎 @Onderhond ping. Let us know if having at least one H1-H6 would address your concern. |
@rviscomi Well, not quite my personal concern, but it would definitely be useful in general I think. As I stated in the original post, an external SEO audit on a site we recently made stated the lack of h1s, which was due to a misconfig in one of my html (twig) components. I didn't can't the problem myself and the Lighthouse check didn't ever (it gave my pages a 100% rating), which ultimately reflected poorly on the work we did. Now maybe this external SEO audit had ulterior motives or the people who conducted it were badly informed themselves, but in my 15 years of FE experience, I've always heard the H1 carries a lot of weight. I've been googling a little and every article I find states the importance of the h1 and its extra SEO weight over other heading tags (h2-h6). I was wondering if I'm missing something and if you guys have info that hints that this information is outdated or quite simply wrong? |
Chiming in here: I think from an SEO perspective, making sure that
I think it's that an audit that at least covers (1) & (2) is quite important. |
Note that e.g. Twitter or Yelp have a homepage H1 on desktop but not on mobile. Lots of news websites don't use H1's on their homepage, but do on article pages. (The sites I tested are just homepages.) For hierarchy I checked that there's an h1 at the top level and that no levels are skipped. Not sure it matters for SEO though and I don't think an H1 needs to be the first heading on the page, if there are less important headings further up in the document. |
We've decided to split the concerns of #7208 (comment) into two audits.
|
Feature request summary
SEO/Best practice check: the appearance of H1s in a page.
Willing but not able I'm afraid. I'm a HTML/CSS guy with extremely limited knowledge of JS :)
What is the motivation or use case for changing this?
I'm using Lighthouse for quick-checking my code. It reported a 100% score for SEO but it turned out there was a misconfiguration in my components that caused the H1s to render as H2s. While actual SEO impact always involves some guess work, it's an age old best practice to have your H1s mark up the main heading of a page. It's fairly easy to check (is there one or is there none) I think.
Also, it might be useful to check if there's ONLY one, since I believe the system with multiple H1s has been made unofficial again, with search engines pledging they'll follow this decision in months to come.
How is this beneficial to Lighthouse?
It gives more trust in the SEO/best practice scores. I think this is a generally accepted implementation with generally accepted benefits, when Lighthouse doesn't report it, it kind of makes me question the other things it might be missing.
The text was updated successfully, but these errors were encountered: