Are your schema entities linked into one graph?
Structured data entities are linked (@id). Entities without @id links are disconnected fragments — three statements that happen to sit on one page.
What the check looks at
The check reads every JSON-LD entity on a page and looks for @id references between them: the WebPage that is part of the WebSite, the article whose publisher is the Organization, the Organization with one stable @id reused everywhere.
Why it matters
Entities without @id links are disconnected fragments — three statements that happen to sit on one page. Linked, they are one coherent organization with pages, articles and products that an engine can merge across the site.
How to see it on your own site
In the JSON-LD, check that the Organization has an @id (https://yourdomain/#org) and that other entities refer to it with "publisher": {"@id": "…#org"} rather than repeating a name.
Schema & entity check → — free, no signup.
How to fix it
- Give the Organization and the WebSite stable @ids and use them on every page.
- Reference, do not repeat:
author,publisher,isPartOf,aboutpoint at the @id. - Use @graph to put the entities of a page in one block.
What the agent does: the agent's Organization block carries a stable @id that every page shares; your templates can point at it.
Related checks
Part of the 23 checks · group: Brand identity — JSON-LD on the page, entity links (@id, sameAs), Wikidata record, consistent external profiles.
Questions people ask
What is @id, exactly?
A URL-shaped identifier for an entity, so two mentions of it can be recognised as the same thing. https://yourdomain/#org on every page means one organization, not one per page.
Start with the free check. Then tell the agent what you need.
The free check runs the 23 checks on your public pages. Nothing is installed, nothing changes until you press it.
Free check from outside in minutes · the report by email · nothing installed yet