Two different Organization @id values across the site

Why it matters

Different pages declare different `@id` values for the organisation. To AI engines this looks like two competing entities under one domain. The engine has to guess which one is canonical, and its guess is usually wrong because both @ids look equally weighty. Result: entity-level signals get split, citation weight is halved, and the knowledge graph for your brand fragments.

The fix

Pick one @id and use it on every Organization node site-wide:

```json
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "@id": "https://example.com/#organization",  // <-- the chosen @id
  "name": "Example",
  "url": "https://example.com",
  "sameAs": [ ... ]
}
```

Then refer to it from other schema nodes using `@id`:

```json
{
  "@type": "Article",
  "headline": "...",
  "author": { "@id": "https://example.com/#organization" },
  "publisher": { "@id": "https://example.com/#organization" }
}
```

This way every page references the same single Organization node and the engine sees one coherent entity.

The most common cause of this rule firing is two CMS templates each emitting their own Organization block with auto-generated @ids. Pick one template as the source of truth; have the other reference the @id instead of re-declaring.

References

• schema.org: using @id
• JSON-LD 1.1: @id keyword