Semantic Entity & Topical Map Audit

Audit whether a website states its entity identity unambiguously in machine-readable form and organizes its content into a coherent pillar-and-cluster topical structure, so that search engines and AI answer engines have a reconcilable identity to attach claims to instead of guessing between same-named entities.

Schema.org defines sameAs as the "URL of a reference Web page that unambiguously indicates the item's identity", naming an item's Wikipedia page, Wikidata entry, or official website as the examples [SCHEMA-SAMEAS-01]. Google's Organization structured-data guidance frames sameAs more broadly as "the URL of a page on another website with additional information about your organization" — for example a profile page on a social media or review site — and does not name Wikidata or Crunchbase specifically [GOOGLE-ORG-SCHEMA-01]. Treat Wikidata and Wikipedia as the identity-reconciliation targets Schema.org actually names, and treat Crunchbase, LinkedIn, GitHub and similar profiles as additional corroborating references.

No first-party documentation from OpenAI, Perplexity, Google, or Anthropic establishes sameAs as an input to their entity resolution. Do not assert that adding sameAs causes a named engine to disambiguate, cite, or recommend a brand. State the mechanism as what it verifiably is: an unambiguous machine-readable identity claim that removes a source of confusion.

Workflow

1. Audit entity disambiguation and sameAs knowledge graph grounding:
   • Inspect Schema.org Organization, Brand, and Person JSON-LD entities on the homepage and about/author pages [SCHEMA-ORGANIZATION-01].
   • Check for a sameAs array pointing at reference pages that unambiguously indicate identity [SCHEMA-SAMEAS-01]:
     • Wikidata item URI (https://www.wikidata.org/wiki/Q...) and/or Wikipedia article URI — the examples Schema.org names.
     • Corroborating profiles: Crunchbase organization page and official verified social profiles (LinkedIn, X/Twitter, GitHub, YouTube) [GOOGLE-ORG-SCHEMA-01].
   • Ensure the entity @id uses a stable global URI (e.g. https://example.com/#organization).
   • Where a sameAs target is present, resolve it and confirm it describes this organization before reporting it as reconciled — a presence grep proves the property is present, not that the target is correct [WIKIDATA-DATA-ACCESS-01].