Structured data
JSON-LD that lets AI engines read each page as an entity.
What it tells you
Part of AI readability. These checks read the JSON-LD markup that describes each page to machines: what it is, who is behind it, and how its parts connect.
Checks
Structured data present and valid
The page publishes no JSON-LD structured data. Search engines and AI assistants have no machine-readable description of what this page is about, so they must infer everything from the raw text.
The JSON-LD does not parse. Nothing in it is read.
The page carries structured data, but not the type expected for this kind of page. A product page without Product markup, for example, cannot appear in the results that depend on it.
Read the documentation ›Required schema properties present
A property Google requires for this type is missing, so the object is ineligible for the results that depend on it.
Read the documentation ›Recommended schema properties present
The structured data omits properties Google lists as recommended for this type. The object parses, but the fields an assistant would quote, hours, price, rating, author, are not there to quote.
Read the documentation ›Schema carries sameAs links
No sameAs links. sameAs is how an entity is matched to its profiles elsewhere; without it the brand is harder to disambiguate.
Read the documentation ›sameAs links are absolute
A sameAs link is relative. sameAs exists to point at the brand elsewhere on the web, so a relative value cannot do its job of connecting this entity to an external profile.
Read the documentation ›sameAs links cover the main profiles
Few sameAs links. Three or more trusted profile URLs is where the entity signal starts to hold.
Read the documentation ›Schema URLs are absolute
Structured data contains relative URLs. Most consumers resolve them against the page, but absolute URLs remove the ambiguity.
Read the documentation ›Schema dates are valid
A date inside the structured data is not valid ISO 8601. Consumers usually drop the field rather than the whole object, so freshness signals are lost but the entity still resolves.
Read the documentation ›Schema dates are in order
dateModified is earlier than datePublished. The dates contradict each other, which undermines any freshness signal drawn from them.
Read the documentation ›Schema nodes are linked
The JSON-LD nodes do not reference each other. Linked nodes describe one entity; unlinked ones describe several unrelated things.
Read the documentation ›Contact details match the brand record
Assistants read the brand's name, address, phone and email from several places. When they differ, an assistant may state the wrong one or none.
Read the documentation ›Seen in the app on: Technical Audit
See how the brand's site does on these checks.Related guides
- How the audit score is built
One score out of 100 for the brand's site: how well AI models can reach and read it, and how sound it is, with AI readability counting most.
- AI readability and site health
AI readability is whether AI models can reach and understand the brand's pages; site health is how fast, safe and sound they are.
Still stuck? Contact support ›