Structured data helps Google understand a page and can earn it a rich result: stars, prices, FAQs or breadcrumbs. One misspelled type or a missing required property is enough to lose it.
AD2SPIDER extracts the structured data from every page (JSON-LD, Microdata and RDFa), validates it against the schema.org vocabulary and Google's rich result requirements, and tells you which pages have errors, which have warnings and which rich result features it detects.
Structured data errors
They stop the page from working or being indexed properly. Fix them first.
Structured data parse error
- Why it matters
- A structured data block cannot be read (malformed JSON, trailing commas…): search engines ignore it entirely.
- How to fix it
- Fix the syntax; the JSON-LD Playground or Google's Rich Results Test point to the exact line.
Structured data validation errors
- Why it matters
- There are types or properties that do not exist in schema.org, or required properties of a Google rich result are missing: that item cannot be shown as such.
- How to fix it
- Fix the names (following the schema.org vocabulary) and add the required properties listed.
Structured data warnings
Real problems worth fixing.
Structured data validation warnings
- Why it matters
- Recommended properties of a rich result are missing: it is eligible, but with less information it may display worse.
- How to fix it
- Add the recommended properties that make sense for the page.
Structured data information
Data to understand the site; not errors in themselves.
Missing structured data
- Why it matters
- The page has no JSON-LD, Microdata or RDFa: it cannot qualify for rich results.
- How to fix it
- Add structured data (JSON-LD is Google's recommended format) if the page fits a rich result type.
Rich result feature detected
- Why it matters
- The page has structured data of a type Google can show as a rich result.
- How to fix it
- Inventory: review the errors and warnings for those features.