Why structured data matters
It helps automated systems recognise the type of content, its properties and relationships more clearly. It does not replace sound HTML or content quality, but it can make a page easier to interpret and more likely to qualify for selected result presentations.
Most commonly used types
- Article / BlogPosting: articles and blog posts.
- Product + Offer + AggregateRating: e-commerce and reviews.
- FAQPage and HowTo: vocabulary types that do not imply Google FAQ or HowTo rich-result support.
- Organization, LocalBusiness, BreadcrumbList: company data and navigation.
- DefinedTerm / DefinedTermSet: glossaries and term dictionaries.
Best practices
Markup must describe content actually visible on the page, because a mismatch risks a manual action. Validate the implementation with Google's Rich Results Test and keep structured data in the prerendered HTML rather than injecting it with client-side JavaScript.
Schema validator, schema checker, and Rich Results Test
Vendors use “checker” and “validator” inconsistently. A JSON parser checks syntax. Schema Markup Validator checks the description against Schema.org. Rich Results Test checks requirements for supported Google features; none proves the content is true or guarantees display.
- JSON parser: whether the document can be parsed.
- Schema Markup Validator: Schema.org types and properties.
- Rich Results Test: requirements for features currently supported by Google.
- Editorial review and URL Inspection: content alignment, access and indexing.
Example
An article description scenario. Replace the author, date and headline with actual visible page data; the example does not assert that this article was published.
{
"@context": "https://schema.org",
"@type": "Article",
"headline": "How to reserve space for images",
"author": {
"@type": "Person",
"name": "Author name"
},
"datePublished": "2026-09-01"
}How to validate the implementation
- Check JSON-LD syntax (the parser should report no errors).
- Confirm values match content visible on the page.
- Confirm the type and properties fit that page template.
- Re-check after template changes or deploys, preferably with Google’s Rich Results Test.
Does structured data improve Google rankings?
Markup can help a search engine interpret a page and qualify it for supported presentations. It does not guarantee rankings, display or CTR gains. Assess effects using your own site data.
Visible FAQs and Google’s feature
Google retired FAQ rich results from May 7, 2026, and removed its documentation on June 15, 2026 (Search Central updates). Useful questions and answers remain valuable content, but FAQPage does not restore the retired feature.
A schema validator checks the syntax and structure of JSON-LD or Schema.org data. It can detect invalid JSON, incorrect types, and incompatible values, but it does not guarantee eligibility for a Google rich result.
Vendors use “checker” and “validator” inconsistently. A JSON parser checks syntax. Schema Markup Validator checks the description against Schema.org. Rich Results Test checks requirements for supported Google features; none proves the content is true or guarantees display.
No. Rich Results Test checks Google-supported types and requirements for selected rich-result features. General Schema.org validation needs a separate validator, while indexing and rendering require Google Search Console.
No. Valid structured data is a technical requirement for selected features, but Google may not show a rich result. Visible content, page quality, data type, and current Google policies also matter.
Validate JSON-LD syntax first, run Google Rich Results Test second, and then verify the URL in Search Console URL Inspection and the Pages report. These tools answer different questions and do not replace one another.
Inspect the rendered HTML and confirm that JSON-LD describes visible content. Then use a syntax validator, Google Rich Results Test and Search Console URL Inspection; each step checks a different kind of correctness.
Structured data are not a direct guarantee of higher rankings. They can help search engines interpret content and enable selected result presentations, but they do not replace quality, accessibility, linking, or correct indexing.
Google retired FAQ rich results from May 7, 2026, and removed its documentation on June 15, 2026 (Search Central updates). Useful questions and answers remain valuable content, but FAQPage does not restore the retired feature.