- A team is learning structured data syntax.
- Several nodes need to be connected in one graph.
- A CMS or template publishes script based markup.
- A code example needs validation before deployment.
Foundation and page identity
Start with valid JSON, visible content, stable IDs, and one coherent graph
JSON LD is a script based structured data format that describes a page and its entities without adding vocabulary attributes throughout the visible HTML.
Beginner reference
5 decisions
6 checks
Reviewed 2026-07-27
Current platform reality
Separate Schema.org meaning from Google feature eligibility.
Reviewed 2026-07-27
Google recommends JSON LD when the site setup allows it. The format is easier to maintain, but it still requires valid JSON, accurate fields, visible content alignment, and the correct feature rules.
Use and avoid
Apply the type only when the visible role and evidence support it.
- Using smart quotes or trailing commas.
- Copying placeholders into production.
- Publishing hidden or irrelevant data.
- Assuming valid JSON equals Google rich result eligibility.
Implementation model
Make the page role, identity, fields, and validation decisions in order.
Start with context and type
Name the vocabulary and real item.
Add visible fields
Use values readers can confirm.
Use stable IDs
Connect repeated entities through @id.
Use @graph when helpful
Keep several connected nodes in one readable block.
Validate twice
Check generic syntax and any Google feature requirements separately.
Acceptance checks
Do not approve the markup because the JSON parses.
The content, entity ownership, canonical URLs, policy state, and maintenance source must also pass.
Valid JSON
Quotes, commas, arrays, and objects parse correctly.
Accurate type
The selected type matches the visible item.
Visible values
Marked fields appear on the page.
Stable identity
@id values remain consistent.
No placeholders
Example values are fully replaced.
Correct validator
The test matches the intended consumer.
Implementation examples
Use the examples as a starting structure, not production data.
Replace every placeholder with approved visible values. The examples do not create eligibility or guarantee a search appearance.
Minimal JSON LD WebPage
Copy exampleConnected four node graph
Copy examplePrimary sources
Use current Google and Schema.org documentation as the source of truth.
Google structured data introduction
Open the official sourceGoogle general structured data guidelines
Open the official sourceGoogle structured data testing tools
Open the official sourceGoogle structured data introduction
Open the official sourceGoogle general structured data guidelines
Open the official sourceSchema.org JSON LD context
Open the official sourceQuestions
JSON LD Basics questions.
Where does JSON LD go?
It is normally placed in a script element in the head or body of the document.
What does @id do?
It gives a node a stable identifier so other nodes can reference the same entity.
What does @graph do?
It holds several connected nodes inside one JSON LD block.
Does valid JSON guarantee eligibility?
No. The page must also satisfy relevance, quality, visibility, and feature specific requirements.
Next route
Prepare schema cues after visible copy, entity ownership, and URLs are approved.
MIRENA can audit the page role, identity, fields, current feature support, and validation route. Production markup still needs human review and live testing.
Founder access is €20 every 30 days excluding VAT for one seat and one active MIRENA instance. OpenAI account rules and usage limits remain separate.