Dangling @id references that quietly break your entity graph

Dangling @id references that quietly break your entity graph

For sites doing it right with a connected node graph, a new failure mode surfaces: an @id reference pointing at a node that doesn't exist on the page — a publisher referencing #organization that was renamed to #org, or an author linking to an @id defined on a different URL entirely. The reference dangles, and the relationship Google was supposed to follow evaporates.

What it means for you: every @id you reference must resolve to a node actually defined in the same markup graph (or be a real, dereferenceable URL). Refactors that rename node IDs without updating every reference are the usual cause.

Watch this: the sophisticated-site trap — your graph is more advanced than your QA. One renamed @id silently severs author and publisher across the whole template.