EntitySEO.wikiThe Entity SEO Reference

@id and entity graphs

From EntitySEO.wiki, the entity SEO reference · Published · Updated · By · Published by Local Blitz · How we research

In JSON-LD, @id gives a node a stable identifier (a URI) so that other nodes, on the same page or across your site, can refer to it instead of redefining it. Using one consistent @id for your organization, each person and your website lets you build a connected entity graph: articles point to their author, the author works for the organization, and the organization publishes the site.

What is @id?

The JSON-LD 1.1 specification uses @id to identify a node with an IRI; other objects can then reference that node by the same IRI.[1] Officially documented The IRI does not have to resolve to a separate page, but a URL on your own domain, such as your homepage plus a fragment, is the usual pattern.

What is a good @id pattern?

EntityExample @id
Organizationhttps://www.example.com/#organization
WebSitehttps://www.example.com/#website
Personhttps://www.example.com/about/jane-doe#person
WebPagehttps://www.example.com/guide/#webpage

The fragment names are a convention, not a standard. Practitioner practice What matters is that each entity keeps the same @id everywhere.

How do nodes connect?

{
"@context": "https://schema.org",
"@graph": [
{"@type": "Organization", "@id": "https://www.example.com/#organization",
"name": "Example Co", "url": "https://www.example.com/"},
{"@type": "Person", "@id": "https://www.example.com/about/jane-doe#person",
"name": "Jane Doe", "worksFor": {"@id": "https://www.example.com/#organization"}},
{"@type": "Article", "headline": "Guide title",
"author": {"@id": "https://www.example.com/about/jane-doe#person"},
"publisher": {"@id": "https://www.example.com/#organization"}}
]
}

Can @id work across sites?

Yes. Every article on this wiki uses the same Person and Organization @id values for Simon White and Local Blitz (https://entityseo.wiki/simon-white#person and https://entityseo.wiki/#publisher, IRIs on this site’s own domain), so every article points to one author entity and one publisher entity. Practitioner practice View the page source of any article here to see the pattern.

What mistakes break the graph?

How JSON-LD defines @id, node references and graphs

The W3C JSON-LD 1.1 specification describes node identifiers this way: “to be able to externally reference nodes in an RDF graph, it is important that nodes have an identifier”, and in JSON-LD a node is identified with @id.[1] Four details from the spec shape good practice:

This site’s own pattern

Every page on EntitySEO.wiki carries one @graph in which the website, publisher, author, page and breadcrumb are separate nodes joined by node references. The publisher is https://entityseo.wiki/#publisher, the author is https://entityseo.wiki/simon-white#person, and each page is …/slug#page. All identifiers live on this domain, so nothing in the markup depends on another site. View the source of any article to see it. Practitioner practice

Frequently asked questions

Does Google require @id?

No. Google's docs do not require it, but it is valid JSON-LD and is widely used to connect entities without repeating them.

Does the @id URL need to load?

Not necessarily. It is an identifier. Using a URL on your own domain keeps it unique and under your control.

References

Pages accessed September 29, 2026 unless a date is given. See all sources and our editorial policy.

  1. ^ "JSON-LD 1.1: A JSON-based Serialization for Linked Data". W3C Recommendation. Published July 16, 2020.
  2. ^ "ProfilePage structured data". Google Search Central. Last updated September 8, 2026. Accessed October 29, 2026.