Practical guide

JSON-LD validation checklist

Create useful structured data without spam.

What matters

Structured data should describe visible page content. Choose the closest supported type, supply required fields, keep URLs canonical and never invent ratings, prices or FAQs that users cannot see.

A safe workflow

Keep the source unchanged.
Test on a representative copy.
Review the output for meaning, not only file size or a green status.
Record the settings that worked.

Common mistake

Automation can make a wrong assumption repeat faster. Confirm encoding, units, schema meaning or visual quality before applying a result broadly.

Publish what visitors can verify

Structured data should describe the main visible content of the same canonical page. An Article headline should match the displayed headline; an Organization name and URL should identify the real organization; Product properties should not invent offers or reviews.

Deployment checklist

Choose the narrowest accurate schema type.
Use absolute HTTPS URLs.
Generate the initial JSON-LD and inspect it as JSON.
Place the script on the matching page.
Test the published URL, not only the pasted code.
Retest after visible content or templates change.

Common failure

Valid JSON is not automatically valid structured data. A document can parse correctly while using an unsupported property, missing a required field or contradicting the page.