What we look for
These pages hold a block of structured data (code that describes the page's content to search engines) written as JSON-LD that has a syntax error, so it cannot be read.
Why it matters
Search engines ignore structured data they cannot read, so the page loses any rich results (extras such as stars, prices or dates in search results) the block was meant to earn.
How to fix
Run the page through Google's Rich Results Test to find the error, then fix the JSON-LD in the page template or the plugin that writes it. A missing comma or quote mark is often the cause.
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: structured_
data. parse_ errors - crawl.json and the CSV
- The crawl JSON names the finding by this id, and so do the CSV and
raptor_query."check_
id": "structured_ data. parse_ errors" - The HTML report
- This link opens the finding in the report, and each finding shows its id.
crawl.
html# finding= structured_ data. parse_ errors - 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": "structured_ data. parse_ errors" }