Guides

Validate JSON-LD Structured Data for Google Rich Snippets

Google Rich Snippets enhance search results with star ratings, product prices, FAQ accordions, and article badges. Earning them requires strict Schema.org syntax, accurate property structures, and absolute parity with visible page copy.

Reviewed by WebAudit Lab · Updated 2026-10-02

Embed structured data using standard JSON-LD

Google strongly recommends JSON-LD (JavaScript Object Notation for Linked Data) embedded within <script type='application/ld+json'> tags over Microdata or RDFa. JSON-LD decouples structured metadata from visual HTML markup, preventing accidental breakage during UI redesigns. Ensure each script tag parses as strict, unescaped JSON without trailing commas, invalid string quotes, or syntax anomalies that cause Googlebot parsers to fail.

Target eligible Google Rich Result schema types

Not every Schema.org entity generates visual search features. Focus markup on schema types supported by Google Search: Article, Product, Organization, FAQPage, BreadcrumbList, HowTo, Recipe, and Event. Consult Google Search Central documentation for feature-specific mandatory properties. For example, Product schema requires name, image, and offers (with price, priceCurrency, and availability), while Article requires headline, image, datePublished, dateModified, and author entity objects.

Ensure strict parity between JSON-LD and visible text

One of the most common reasons Google ignores structured data or issues manual spam penalties is content divergence. Every price, user review rating, FAQ answer, publication timestamp, and author declared in JSON-LD must be clearly visible and legible to human visitors on the page. Concealing structured entities via display:none or declaring speculative reviews not present on the rendered page violates Google Search guidelines.

Connect entity graphs with @id and canonical URLs

Avoid emitting disconnected, isolated JSON-LD blocks on a single page. Use Schema.org @id URIs and nested properties to interconnect entities into a cohesive knowledge graph. Link the Article's publisher to the canonical Organization @id, associate BreadcrumbList with the canonical route, and verify that all internal URL properties match the page's preferred canonical HTTPS URL exactly, including subdomains and trailing slashes.

Test with Google Rich Results Tool and Schema Validator

Validate your markup using both the official Google Rich Results Test (which validates eligibility for Google-specific search enhancements) and the universal Schema.org Validator (which checks strict semantic compliance). Automate structured data validation in your build pipeline with automated unit tests to ensure content management updates or template revisions do not silently break structured data integrity.