The @graph JSON-LD explained
How the theme emits a single connected @graph of JSON-LD structured data, and why that helps search engines.
The @graph JSON-LD explained
Search engines understand pages better when you describe them in structured data, and this theme emits it as JSON-LD using a connected @graph. Rather than scattering separate, duplicative snippets, the theme outputs one JSON-LD block whose @graph array holds several linked entities that reference each other by @id — a cleaner, more accurate model of the page.
A single @graph lets entities share definitions instead of repeating them. The site's Organization and WebSite are defined once with stable @id values, and every page's WebPage, Article, or Course node points back to them via @id references. This avoids contradictions (one canonical publisher, one site definition) and is exactly how Google recommends modelling interlinked entities.
{
"@context": "https://schema.org",
"@graph": [
{ "@type": "Organization", "@id": "{site}/#owner", "name": "Namaste Salesforce" },
{ "@type": "WebSite", "@id": "{site}/#website", "publisher": { "@id": "{site}/#owner" } },
{ "@type": "Course", "@id": "{url}/#course",
"provider": { "@id": "{site}/#owner" },
"name": "Apex Masterclass" },
{ "@type": "WebPage", "@id": "{url}/#webpage",
"isPartOf": { "@id": "{site}/#website" } }
]
}
Notice the cross-references: the Course's provider and the WebSite's publisher both point at the same Organization @id, and the WebPage declares it isPartOf the WebSite. Search engines follow these links to build a coherent picture of who published what.
As an author you rarely touch this directly — the theme generates the graph from your Ghost content and settings. But understanding it explains why the site's fields matter: your Organization details (in Ghost general settings) feed the publisher node, and post-level fields feed the page node. Keeping those settings accurate makes the structured data accurate.
The next two docs drill into the most valuable page-level entities the graph emits — the Course and LearningResource schema that make course pages eligible for rich results, and the meta titles and canonical URLs that keep the graph's identity consistent.