Guides
How to Validate Structured Data and JSON-LD
Valid JSON is only the first gate. The markup must describe the visible page accurately and meet the current policy for the feature you expect.
Parse the JSON-LD, inspect every entity and property against visible content, then use the validator for the exact search feature. Correct markup never guarantees a rich result.
Parse and validate every JSON-LD block
Ensure every <script type='application/ld+json'> block parses as strict, valid JSON. Common syntax errors—such as missing closing braces, unescaped quotes in descriptions, trailing commas, or misplaced @context and @type declarations—render entire entity graphs unreadable by search crawlers.
Model authentic page entities
Choose Schema.org types that accurately reflect the primary subject of the page (such as Article, Product, Organization, or FAQPage). Connect entity nodes logically using @id and URL properties, rather than inflating the page with disconnected or irrelevant schema types.
Enforce strict parity with visible content
Every question, answer, price, aggregate rating, review, author, and timestamp declared in markup must be plainly visible to human visitors on the page. Declaring FAQ or rating schema for content that is hidden, cloaked, or absent violates search engine guidelines and risks algorithmic penalties or manual actions.
Maintain canonical identity and URL consistency
Keep @id, url, and mainEntityOfPage attributes aligned with the preferred canonical URL of the document. Ensure protocols (https), subdomains, and trailing slashes match exactly so search crawlers can resolve entity identity without ambiguity.
Understand search feature eligibility limits
Valid JSON-LD syntax and Schema.org compliance are prerequisites, but they do not guarantee rich-result inclusion in Google Search. Search features change over time, and display depends on Google's algorithmic quality thresholds and current documentation.