Updated 2026-07-13 · 13 min read
JSON-LD gives machines an explicit graph of entities and relationships already visible on a page. It can reduce ambiguity and qualify pages for supported search features. It cannot make weak content authoritative, force an LLM citation or replace crawlable HTML. The best implementation is accurate, connected and boring.
Define one Organization and one WebSite with persistent @id values, then reference those IDs from every page. Do not create a new slightly different organization entity on each route. Use canonical absolute URLs.
{"@context":"https://schema.org","@type":"Organization","@id":"https://example.com/#org","name":"Example","url":"https://example.com/","logo":"https://example.com/logo.png"}
An article’s publisher should reference https://example.com/#org; its isPartOf references #website; mainEntityOfPage points to the canonical page entity. Breadcrumb items use canonical page URLs. These links tell parsers that repeated nodes are the same entity.
Think beyond isolated snippets. The homepage defines Organization and WebSite. An article references those nodes instead of redefining them. A category is a CollectionPage whose ItemList links to canonical article or product pages. The AboutPage is about the same Organization ID. This connected graph is easier to maintain and less ambiguous than twenty independent blocks with slightly different names and logos.
Generate schema server-side from the same records used for titles, visible headings and canonical links. If a price, date or item count changes, one data update should change both HTML and JSON-LD. Parallel hand-maintained facts inevitably drift.
Never add reviews, prices, FAQs or authors that a visitor cannot verify. During a free launch, do not leave paid offer schema active while hiding the price from the page. Keep dates real: dateModified changes only when content meaningfully changes, not on every server start.
A strong Article node includes headline, description, canonical URL, image, datePublished, dateModified, inLanguage, author, publisher, articleSection, keywords and wordCount. Add citations when the article relies on external primary sources. The structured fields should be generated from the same content object that renders the page to prevent drift.
Use CollectionPage as the page and ItemList as its main entity. List position, name and canonical URL for items. Do not dump thousands of entities into every category page; include the visible items or a sensible representative list and let their own pages carry detail.
No mechanism guarantees recommendation. LLM-oriented discovery benefits from the same foundations: accessible pages, clear entities, consistent facts, original evidence, internal links and external references. JSON-LD improves machine readability and disambiguation; citations are earned by useful, trustworthy information.
Inventory every indexable route and map it to the most specific truthful Schema.org type. Create stable Organization and WebSite @id nodes shared across routes. Generate page JSON-LD from the same server-side data as visible HTML. Add Article fields, BreadcrumbList and CollectionPage/ItemList where appropriate. Do not add invisible claims. Write tests that parse every block and assert canonical URLs, required fields and unique stable IDs.
It helps machines understand entities and relationships, but does not guarantee citations or recommendations. Original content, crawlability and authority remain essential.
Organization and WebSite are useful foundations for most organizations. Page-specific schema should then match the actual page type.
Only when the questions and complete answers are visible and genuinely useful. Search engines may limit FAQ rich results regardless of valid markup.