What we look for
The headings on these pages skip a level, for example an H2 followed straight by an H4, or the first heading on the page is not an H1 (the main heading).
Why it matters
People using screen readers move through a page by its headings, so skipped levels make the outline harder to follow.
How to fix
Use heading levels in order in the page template and content, one H1 then H2, H3 and so on, and change how a heading looks with styling rather than by picking another level.
Where you’ll see it
The id is stable, and every surface uses it, so it’s the thing to search for or hand to an agent.
- Terminal
- When it is one of the five findings under Fix first,
raptor crawlprints the id under it.Check: headings.
non_ sequential - crawl.json and the CSV
- The crawl JSON names the finding by this id, and so do the CSV and
raptor_query."check_
id": "headings. non_ sequential" - The HTML report
- This link opens the finding in the report, and each finding shows its id.
crawl.
html# finding= headings. non_ sequential - MCP
raptor_findingswith thischeck_idreturns the finding in full, with a fix brief ready to paste into a task. If it didn’t fire, it says why.raptor_
findings { "job_ id": ". . . ", "check_ id": "headings. non_ sequential" }