What is JSON-LD @graph?

JSON-LD @graph

@graph is a JSON-LD container that lets a single <script type="application/ld+json"> block declare multiple, cross-referenced entities at once — for example, an Organization, a WebSite, a WebPage, and a BreadcrumbList that all reference each other via @id pointers. It is the recommended pattern for any site with more than one schema entity on a page. Why it matters: A consolidated @graph emits stronger entity signals than a stack of disconnected schema blocks, because the cross-references explicitly tell search and AI engines how the entities relate. It also reduces page weight and prevents the common bug where multiple Organization blocks contradict each other.

Why JSON-LD @graph matters

Aggregating data into a unified graph prevents data silos that confuse AI scrapers and search spiders. It transforms a collection of random attributes into a structured entity relationship that proves authorship, site ownership, and brand authority in one scan.

In practice

A technical SEO uses the Yoast plugin to output a single JSON-LD block where the WebPage is linked to an Organization and a specific Person via its @id, creating a readable map for Googlebot.

Common mistake

Treating nested schema entities as independent islands by omitting the @id attribute, which prevents search crawlers from resolving them into a single coherent knowledge graph.

How it connects

This architecture relies heavily on Schema.org Type @id pointers and establishes the foundational logic for the Knowledge Graph.

Frequently Asked Questions

In short: JSON-LD @graph is graph is a JSON-LD container that lets a single <script type="application/ld+json"> block declare multiple, cross-referenced entities at once — for example, an Organization, a WebSite, a WebPage, and a BreadcrumbList that all reference each other via @id pointers. See the full definition above for context.

How does this structure improve crawler interpretation speed?

Search engines process consolidated graphs more efficiently than scattered fragments because relationships are established through IDs rather than proximity. This structure prevents Google from seeing two separate mentions of a Person and an Author as distinct, unrelated individuals.

Will consolidating code blocks impact page performance?

Merging isolated scripts into a single block reduces redundant declarations like repeating the logo URL for both the Organization and the WebSite. Using a single script tag also minimizes the total DOM weight, which can marginally benefit Largest Contentful Paint metrics on heavy pages.

How can I verify the entities are correctly linked?

Tools like the Schema.org Validator or the Google Rich Results Test will display a single tree-like structure when @graph is used correctly. If the tool shows several high-level items that appear disconnected, you have likely failed to link them via @id pointers within the array.

If You're Invisible in AI, You're Losing Clients Right Now.

See exactly how your company appears across AI, search, and investor research — and uncover the hidden gaps costing you trust and deals.