Technical SEO

Schema.org @id Hub Technique: Entity Consolidation Results Across 8 Sites

May 11, 2026·13 min min read·Emre Çelik

Why Entity Consolidation Matters

Google's 2025-2026 algorithm ranks entities, not pages. When the same person, brand, or concept appears with different @ids across pages, Google treats them as separate entities and signals scatter. The @id hub technique ties every reference to one canonical URI, producing a single strong node in the Knowledge Graph.

Test Setup

Sample: 8 client sites, each with 3-5 primary entities (founder, brand, product line)
Window: Feb 1 – May 1, 2026 (3 months)
Metrics: Knowledge Panel trigger, sitelinks search box, brand SERP CTR
Control: 4 sites (no hub, legacy scattered schema) vs 4 sites (hub applied)

Implementation Pattern

Pick one canonical URI per entity (e.g., https://site.com/#founder-ahmet). Every JSON-LD reference on the site uses that @id:

{
  "@context": "https://schema.org",
  "@graph": [
    {
      "@type": "Person",
      "@id": "https://site.com/#founder-ahmet",
      "name": "Ahmet Yilmaz",
      "sameAs": [
        "https://www.linkedin.com/in/ahmet",
        "https://twitter.com/ahmet",
        "https://en.wikipedia.org/wiki/Ahmet_Yilmaz"
      ]
    },
    {
      "@type": "Organization",
      "@id": "https://site.com/#org",
      "founder": { "@id": "https://site.com/#founder-ahmet" }
    },
    {
      "@type": "Article",
      "author": { "@id": "https://site.com/#founder-ahmet" }
    }
  ]
}

Every Article, AboutPage, ProfilePage schema references the same #founder-ahmet. Google merges them into one entity.

3-Month Results

Metric	No hub (4 sites)	Hub (4 sites)	Delta
Brand SERP Knowledge Panel	18% (1 site)	80% (3 + 1 partial)	+4.4x
Sitelinks search box	0/4	3/4	+3 sites
"founder of X" position 1	1/4	4/4	+3 sites
Brand CTR average	34.1%	55.3%	+62.1%
People Also Ask entity	2 sites, 7 PAAs	4 sites, 31 PAAs	+4.4x

Common Mistakes

Different @id per page: Most common error. /about#ahmet and /authors/ahmet#person are two people to Google.
Missing sameAs: sameAs is the bridge into the Knowledge Graph. Without Wikipedia, Wikidata, LinkedIn links, the hub is half-built.
Separate JSON-LD blocks instead of @graph: Works, but linkage visibility drops. Merge into one @graph.
Hub URL has no real page: The #founder-ahmet fragment must resolve to a real ProfilePage. Phantom @ids don't consolidate in Google.

Knowledge Graph Verification

Six weeks after rollout, the kgsearch.googleapis.com/v1/entities:search?query=... API showed that hub entities had picked up a stable kg:/g/ Knowledge Graph ID. No such ID appeared for non-hub sites — strong evidence that consolidation registered on Google's side.

Editorial Note

Setting up @id hubs is 1-2 days of technical work, but its impact lasts as long as your content. For Knowledge Panel and brand SERP dominance, the answer isn't "write more articles" — it's "build a cleaner entity graph." In 2026 this is the highest cost-to-impact ratio technical SEO move available.