Structured Data QA: Testing Markup Without Making Unsupported Claims

Structured data can describe entities and page content in a machine-readable form. A green validation result does not prove that a claim is true or that Google will show a particular feature. Good QA separates syntax, meaning, eligibility and observed search appearance.

Inventory the output and its owners

Inspect the rendered page for all JSON-LD and other markup, including output from the theme, SEO plugin, review widget and custom code. Multiple systems can create contradictory organisations, duplicate primary entities or different canonical URLs.

Record which system owns each entity and how it will be maintained. Do not add another plugin simply because the page already has incomplete or confusing markup; resolve the ownership problem first.

Check the claims against the visible page

Verify business names, addresses, URLs, services, prices and relationships against current evidence. Ratings, testimonials and credentials need appropriate support and must follow the relevant feature policies. Do not manufacture an aggregate rating from selected comments or mark up a service as a product solely to seek stars.

Google's structured data policies explain the importance of accurate, representative content and feature-specific rules. Schema.org vocabulary and Google's supported search features are related but are not the same catalogue.

Use the right test for the question

Use a schema validator to investigate vocabulary and syntax, and Google's Rich Results Test for supported Google feature checks. Review required and recommended properties in the current documentation. An unsupported type may still be valid vocabulary without producing a Google rich result.

Test the published output as well as a draft code snippet. Check whether a consent tool, plugin conflict or template condition changes what the page actually contains. Keep a copy of the test date, URL, tool and relevant findings.

Illustrative conflict review

Imagine a business moves offices but its theme still outputs the old address while the SEO plugin shows the new one. Both blocks may be syntactically valid. The repair is to identify the maintained source, remove the contradiction through the responsible system and verify the rendered result.

Similarly, a correct LocalBusiness entity does not justify claiming that structured data has guaranteed a local ranking or an AI recommendation. The practical schema guide explains the broader implementation choices.

Monitor changes without chasing obsolete features

Review markup after redesigns, plugin changes and updates to the business information. Check Search Console reports where relevant and distinguish a detected enhancement from a guaranteed appearance or traffic gain.

Feature support changes: Google retired FAQ rich results in 2026. Do not sell an old search presentation as a current benefit. Our AI search and structured information support connects accurate entity information with a documented and maintainable QA process.