[wp-trac] [WordPress Trac] #52675: Twenty Nineteen: On an a blog page set to display full posts, post titles are downgraded from h1 to h2, but original h2 headings remain h2
WordPress Trac
noreply at wordpress.org
Fri Mar 5 21:59:14 UTC 2021
#52675: Twenty Nineteen: On an a blog page set to display full posts, post titles
are downgraded from h1 to h2, but original h2 headings remain h2
---------------------------+--------------------------------
Reporter: asafm7 | Owner: (none)
Type: defect (bug) | Status: closed
Priority: normal | Milestone:
Component: Bundled Theme | Version:
Severity: normal | Resolution: maybelater
Keywords: | Focuses: ui, accessibility
---------------------------+--------------------------------
Comment (by asafm7):
Hi @ryokuhi ,
Thank you so much for the update.
Here are my thoughts:
- I'm not sure about it being an edge case - it happens every time there
is a subheading in a post, which is quite common I guess, and the blog
page is set to display full posts, which is one of 2 available settings.
- I'm not sure about it being in the plugin territory. Such basic HTML
feels core-y to me...
- I understand it is not just Twenty Nineteen related - maybe it should
move to another forum?
- There are 3 possible issues here:
1. Confusing design - subheadings look like posts titles
2. Accessibility
3. SEO (which I didn't mention before). I'm not an expert, but archive
pages are getting indexed by search engines. It makes sense that the
flattened heading hierarchy makes it more difficult for search engines to
understand what's on the page. In general, I believe that headings are
crucial and basic SEO factors.
- About the issue with h6 - I thought about it too. But I believe this is
a ''true'' edge case. I believe not many blog posts use h6, and then you
add the conditions needed to reproduce the issue - which makes it even
less likely for h6 to be an issue. Anyway, an h6 heading can't be mistaken
as a post title (it has a different size and design than a post title).
The biggest issue is h1 and h2 being merged together and being mistaken
for each other (both by humans and robots). It makes sense that content-
wise as well h6 are less significant - and so having less effect on SEO.
So, the solution for h6 doesn't need to be perfect. It can stay, for
example, as h6.
These are my thoughts anyway.
Thanks again.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/52675#comment:5>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list