Take it step by step
- Choose a schema type that fits the visible page.
- Fill fields from real content rather than invented reviews or ratings.
- Generate and inspect the JSON-LD.
- Use the relevant search-engine validation tool and check the published page.
A situation to try.
A real article can describe its title and actual author. Do not add five-star reviews to a tool page when no such reviews exist.
Use the tool’s synthetic example first where available. The example here explains a decision; it is not a reported benchmark result.
Before you call it done.
- Validate JSON syntax.
- Match names and URLs with visible content.
- Confirm eligibility rules for the desired search feature.
Know the limits.
Syntax validation does not guarantee rich results or higher rankings.
This tool’s current boundary: Review the output before using it. Your input remains on this device.
Evidence and scope
Technical source guidance and task-specific output checks. These do not establish that every file, browser or device passes.
Use the checks above on your own exported result. A source explains the format or mechanism; it is not proof that this export preserved every feature.
Technical reference: Google: structured data introduction ↗
Choose the right tool for this step.
Structured data
Draft JSON-LD matching your page’s visible information.
On your deviceWhy use it: Draft JSON-LD from visible facts.
Before you start: Valid JSON is not rich-result eligibility.
Imported HTML audit
Inspect imported HTML for common markup and SEO issues.
On your deviceWhy use it: Inspect a saved page’s markup.
Before you start: Imported HTML is not a live deployment audit.
Preparation tools process locally. Official service links take you to the authority’s website. Inspect any exported copy before sharing it.