Schema markup audit: each check and its fix
What our audit looks at in structured data, in the words its report uses. Each check comes with the example block that fixes it.
What the audit reads
Read from the audit’s own code on 14 Oct 2026.
- It reads only
<script type="application/ld+json">elements. Microdata and RDFa are not counted. - It reads lists and @graph at the top of a block, and @type as one name or a list. It checks the fields each type needs.
- Every field error comes with the same fix: “Populate all required schema fields with valid data.”
- Across the site, the report counts pages with structured data, pages with errors and pages with malformed JSON-LD. It lists each type with up to three sample pages.
- The JSON-LD validator runs the same block checks on markup you paste. Every example block below passes it.
Checks on every page
These run on each page the audit reads, whatever kind of page it is.
| When the audit reports it | The report says | The block that fixes it |
|---|---|---|
| A JSON-LD block does not parse as JSON | The report says“Page contains malformed JSON-LD blocks.”Its fix: “Fix invalid JSON-LD syntax.” | The block that fixes itThe four blocksEach of the four parses. The same block also gets a field error that starts “Malformed JSON-LD:” and quotes the parser. |
| The page has no typed JSON-LD block | The report says“Page has zero JSON-LD schema blocks.”Its fix: “Add JSON-LD structured data appropriate for the page type.” | The block that fixes itThe four blocksPick the block for that kind of page. |
| No page in the crawl has any JSON-LD | The report says“The audit found zero JSON-LD schema across the crawled HTML pages.”Its fix: “Add structured data to the homepage and major content templates.” | The block that fixes itOrganization blockStart with the home page. |
Checks on article pages
The audit treats a page as an article when it has og:type article, an article element, or a path with /blog/, /news/, /guide/ or a similar folder.
| When the audit reports it | The report says | The block that fixes it |
|---|---|---|
| No block typed Article. BlogPosting or NewsArticle alone does not count | The report says“Article-like page is missing Article JSON-LD.”Its fix: “Add Article schema with headline, dates, author, publisher, and image.” | The block that fixes itArticle block |
| No author meta tag and no author in the JSON-LD | The report says“Article-like page has no author meta tag or JSON-LD author, reducing citation credibility.”Its fix: “Add a <meta name="author"> tag or author field in Article JSON-LD.” | The block that fixes itArticle blockThe block carries author. |
| No article:published_time meta tag and no datePublished in the JSON-LD | The report says“Article-like page has no article:published_time, making it harder for AI to assess freshness.”Its fix: “Add <meta property="article:published_time"> with an ISO 8601 date.” | The block that fixes itArticle blockThe block carries datePublished, which the audit also reads. |
Checks on Product blocks
The field checks run on every Product block. The missing-block check runs on pages with og:type product, or a path such as /products/ with a title or heading that says price, rating or buy.
| When the audit reports it | The report says | The block that fixes it |
|---|---|---|
| A product page has no Product block | The report says“Product-like page is missing Product JSON-LD.”Its fix: “Add Product schema with offers and aggregateRating.” | The block that fixes itProduct with Offer blockThe block carries offers. Add aggregateRating only when the page shows a rating. |
| A Product block has no name | The report says“Product missing required field name” | The block that fixes itProduct with Offer block |
| A Product block has no offers, review or aggregateRating | The report says“Product missing offers, review, or aggregateRating for rich-result eligibility” | The block that fixes itProduct with Offer block |
| No offer in a Product block has a price | The report says“Product offers missing price or priceSpecification.price” | The block that fixes itProduct with Offer block |
Checks on FAQ blocks
Google no longer shows FAQ rich results, and the audit says so. It still checks every FAQPage block it finds.
| When the audit reports it | The report says | The block that fixes it |
|---|---|---|
| An FAQPage block has no mainEntity | The report says“FAQPage missing required field mainEntity” | The block that fixes itFAQPage block |
| mainEntity is not a list | The report says“FAQPage mainEntity must be an array” | The block that fixes itFAQPage block |
| An item in mainEntity is not a Question | The report says“FAQPage mainEntity item is not a Question” | The block that fixes itFAQPage block |
| A question has no acceptedAnswer | The report says“FAQPage question missing acceptedAnswer” | The block that fixes itFAQPage block |
| The page has an FAQPage block but no visible questions | The report says“FAQPage markup is present but the page does not appear to expose visible FAQ-style content.”Its fix: “Ensure FAQPage markup exactly matches visible question-and-answer content.” | The block that fixes itFAQPage blockThe block helps only when the same questions show on the page. |
| The page shows questions and has no FAQPage block | The report says“The page contains FAQ or how-to style content without matching structured data. This is an experimental completeness signal, not evidence of AI-search visibility.”Its fix: “Add only currently supported structured data that accurately matches visible content.” | The block that fixes itFAQPage blockThe block clears it. It is a note, not an error, and the fix asks for supported types only. |
| Any FAQPage block, as a note rather than an error | The report says“FAQ rich results are no longer shown in Google Search (from 7 May 2026).”Its fix: “Do not count this markup as a current Google Search opportunity.” | The block that fixes itFAQPage blockEvery FAQPage block gets this note, ours included. |
Checks with no example block
The audit runs these too. None of the four blocks fixes them, so start from the type’s page on schema.org.
| Type | The report says |
|---|---|
| BreadcrumbList (opens in a new tab) | The report says
|
| Review (opens in a new tab) | The report says
|
| VideoObject (opens in a new tab) | The report says
|
| HowTo (opens in a new tab) | The report says
|
| WebSite (opens in a new tab) | The report says
|
| LocalBusiness (opens in a new tab) | The report says
|
| SoftwareApplication (opens in a new tab) | The report says
|
| ImageObject (opens in a new tab) | The report says
|
| ProfilePage (opens in a new tab) | The report says
|
The BreadcrumbList check runs on article, product, review, FAQ, how-to and video pages.
Valid is not the same as true
- Google’s guidelines say (opens in a new tab) “Your structured data must be a true representation of the page content.” The audit checks one part of that: FAQPage markup on a page with no visible questions.
- Google also says (opens in a new tab) “Google does not guarantee that your structured data will show up in search results”.
- On 15 Jun 2026 Google wrote (opens in a new tab) “The FAQ rich result feature is no longer shown in Google Search results”. The audit marks FAQPage as a type Google Search no longer supports.
Questions
What is a schema markup audit?
It reads the structured data on each page and reports what is broken, missing or no longer used by Google Search. Ours reads JSON-LD only.
What does AEOprobe check in structured data?
It parses each JSON-LD block, lists its types, checks the fields each type needs and looks for the block each kind of page needs. Every check is listed on this page with what the report says.
Why is valid markup not enough?
Google says structured data must be a true representation of the page content. Markup can be valid and still describe something the page does not show. Even true markup comes with no promise of a rich result.
What should I fix first?
The audit rates malformed JSON-LD, field errors and missing Article or Product blocks as high severity. Fix those before BreadcrumbList, Review and VideoObject.
See which checks your site fails today
Run the free audit. It reads the JSON-LD on each page and reports every check on this page that fails.
Run free audit