What we look for
The HTML the server sends for these pages has no H1 heading (the main heading at the top of a page); one appears only after the page's JavaScript runs in a browser.
Why it matters
Search engines that read only the server's HTML see no main heading, and Google sees it only when it renders the page, which can come later.
How to fix
Put the H1 heading in the HTML the server sends, through the page template or your framework's server rendering, instead of adding it with a script.
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: javascript.
js_ injected_ h1 - crawl.json and the CSV
- The crawl JSON names the finding by this id, and so do the CSV and
raptor_query."check_
id": "javascript. js_ injected_ h1" - The HTML report
- This link opens the finding in the report, and each finding shows its id.
crawl.
html# finding= javascript. js_ injected_ h1 - 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": "javascript. js_ injected_ h1" }