What we look for
The HTML the server sends for these pages has no structured data (code that describes the page's content to search engines); it appears only after the page's JavaScript runs in a browser.
Why it matters
Search engines that read only the server's HTML miss it, and Google sees it only when it renders the page, which can delay rich results.
How to fix
Put the JSON-LD block in the HTML the server sends, through the page template, your framework's server rendering or an SEO plugin, 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_ structured_ data - 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_ structured_ data" - The HTML report
- This link opens the finding in the report, and each finding shows its id.
crawl.
html# finding= javascript. js_ injected_ structured_ data - 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_ structured_ data" }