Entity Consistency Across iGaming Properties

Why consistency is the real work

Google's structured data guidelines require markup to be "a true representation of the page content." On a single page that is easy. Across a brand's whole footprint it is hard, because facts drift: a logo is updated on the home page but not in the help center, the legal name changes after a license transfer, an old social profile stays in sameAs for years.

Search systems compare what they find in many places. When the brand name, company and contacts agree, there is nothing to reconcile. When they disagree, systems have to choose, and they may choose wrong. Consistency does not make a brand more visible by itself. It removes reasons for confusion.

The facts to align

Keep this grid in a shared document and treat it as the source for templates. When a fact changes, change it in the grid first, then in every place listed.

Who owns which @id

An @id works best when the domain that describes an entity in full also owns its identifier. The brand's main site owns https://brand.example/#org. A market edition, a help center on a subdomain or a separate blog refers to that identifier instead of minting its own. The identifier guide covers formats and the cases where separate identifiers are right.

{
  "@context": "https://schema.org",
  "@graph": [
    {
      "@type": "Organization",
      "@id": "https://northwake.example/#org",
      "name": "Northwake Sportsbook",
      "legalName": "Northwake Betting Ltd (fictional)",
      "url": "https://northwake.example/",
      "logo": "https://northwake.example/media/logo.png",
      "sameAs": [
        "https://social.example/northwake"
      ]
    },
    {
      "@type": "WebSite",
      "@id": "https://northwake.example/#website",
      "name": "Northwake",
      "url": "https://northwake.example/",
      "publisher": {
        "@id": "https://northwake.example/#org"
      }
    },
    {
      "@type": "WebSite",
      "@id": "https://on.northwake.example/#website",
      "name": "Northwake Ontario",
      "url": "https://on.northwake.example/",
      "publisher": {
        "@id": "https://northwake.example/#org"
      },
      "inLanguage": "en-CA"
    }
  ]
}

sameAs, done carefully

Schema.org defines sameAs as the "URL of a reference Web page that unambiguously indicates the item's identity." In practice that means official profiles the brand controls. A good test: does the profile link back to the brand's site, and would the brand be able to edit it tomorrow? If not, leave it out. Directory listings, affiliate pages and fan accounts do not identify the brand; they describe it.

Market editions and separate companies

Gambling brands often operate through different companies in different markets, because licenses are issued to specific legal entities. Two patterns are honest:

• One company, several sites. Use one Organization node and give each site its own WebSite node with publisher pointing at that Organization.
• Several companies under one brand. Describe each licensed company as its own Organization with its own legalName, and use the same brand or parentOrganization where that relationship is public.

Language and region handling for these editions is in entity identity across localized properties.

Fixing drift

1. Crawl each property and extract its JSON-LD.
2. Compare each fact with the grid. Our entity map helps you see which @id each page points at.
3. Fix templates, not single pages, so the fix holds.
4. Retire old identifiers with care: keep the old domain's markup pointing at the new canonical entity while redirects are in place.
5. Log the change with a date, so the next audit knows what moved.

Sources

How SchemaReel chooses, reads and dates its sources is set out on the data sources page.

1. Google Search Central, General structured data guidelines, last updated July 10, 2026.
2. Google Search Central, Organization structured data, last updated September 8, 2026.
3. Schema.org, sameAs, V30.1 (2026-09-16).
4. Schema.org, Organization (legalName, parentOrganization, brand), V30.1 (2026-09-16).