<b>Stop repeating yourself: @id referencing is the pro move in JSON-LD</b>

<b>Stop repeating yourself: @id referencing is the pro move in JSON-LD</b>

The single biggest tell of amateur markup is the same <code>Organization</code> block copy-pasted into every entity. Pros use a <code>@graph</code> array with stable <code>@id</code> values (<code>#org</code>, <code>#website</code>, <code>#logo</code>) and then reference by ID everywhere else. Define the publisher once, point to it forever.

Why it matters beyond elegance — a connected graph with resolved IDs is what lets Google and AI crawlers build a clean entity model of your site instead of reconciling a hundred duplicate org nodes.

What it means for you — refactor your template to a single <code>@graph</code> with a node for Organization, WebSite, WebPage, and the page's primary entity, all wired by <code>@id</code>. Smaller payload, zero contradictions, stronger entity signals.

Watch this: contradictory duplicate nodes are a quiet cause of 'eligible but not shown.'