Check the structured data on every crawled page

Crawl Audit now checks the JSON-LD on every crawled page, not just whether it is there. Each block is parsed, its @context and @type confirmed, and items of the types Google turns into search features (Article, Product and Offer, BreadcrumbList, FAQPage, LocalBusiness, Event, Recipe, VideoObject, JobPosting and others) are compared with a short list of required and recommended properties. Dates, URLs, prices, currencies, ratings and breadcrumb positions are checked for a plausible shape, and @id references inside a @graph must resolve. Every problem names the block, the item type, the property and a path inside the block, so you can go straight to the line that needs fixing. Search-bot activity on each affected page shows which ones Google is actually reading.

Errors are pages where a block does not parse, an item has no type, or a required property is missing or the wrong shape; warnings cover recommended properties, doubtful values, unknown types and markup that was not checked. The profile is a dated snapshot of Google's documentation (version 1, 25 September 2026), kept deliberately short and conservative. It is not the Rich Results Test: an error does not mean a rich result was lost, and a clean page is not a promise that one will appear.

The check reads the original HTML only. Structured data added by JavaScript is not read, and microdata and RDFa are counted as present but not validated, so those pages are listed as unchecked rather than clean. Very large or deeply nested blocks are reported as unavailable with the reason. Start a new Salience crawl to collect the evidence; crawls captured before this release show the check as unavailable.

See Crawl Audit help for the type list, what each severity means and how to read a problem's path.