Schema markup tells Google what something is. sameAs tells Google which well-known entity it already has in its database. That second step is where schema moves from description to identity — and it is the part most sites skip entirely.

Why Entity Identity Matters

Google’s Knowledge Graph is built on entities: people, organizations, places, concepts. When Google can match your markup to an existing entity in its graph, it can pull facts about that entity from its own database and display them with confidence. That is how Knowledge Panels appear, how author bylines gain credibility, and how local businesses get rich data in Maps results.

Without entity disambiguation, Google has to guess. Two different businesses named ‘Phoenix Digital Services’ look identical from the graph’s perspective. A sameAs link pointing to a Wikidata entry or a Google Business Profile resolves that ambiguity definitively. It is the difference between Google understanding your entity and Google tolerating it.

What sameAs Takes as a Value

sameAs accepts a URL or an array of URLs, each pointing to an authoritative reference for the same entity. The most useful targets, roughly in order of signal strength:

  • Wikidata — e.g. https://www.wikidata.org/wiki/Q12345 — the highest-signal external reference because it is the structured data backbone of Wikipedia and feeds directly into Google’s knowledge graph
  • Wikipedia — if a page exists for the entity; not all organizations or individuals have one, and that is fine
  • Google Business Profile — for local businesses, the Maps URL of the listing; this is the local entity anchor
  • LinkedIn company or profile page — for organizations and professionals; high-authority, frequently crawled
  • Crunchbase — for organizations with investment or company registry data
  • ISNI or VIAF — for public figures and creators, particularly in publishing and academic contexts
  • Official social profiles — Twitter/X, Facebook, YouTube; lower signal individually but useful collectively (for video-heavy brands, a YouTube channel URL in sameAs pairs well with full video schema markup on individual video pages)

Each additional trusted reference strengthens the signal. You do not need all of them. Wikidata plus two or three additional references is a solid foundation for most organizations.

How @id and sameAs Work Together

@id is the entity’s canonical identifier within your own markup — typically your domain URL plus a fragment identifier like #organization. sameAs points outward to other representations of the same entity on external authoritative sources.

Together they tell Google: this node in my graph (@id) represents the same real-world entity as these external records (sameAs). The @id is the local name; sameAs is the external proof. You need both — @id alone creates an island, sameAs alone without a stable @id anchor is hard to act on consistently.

Person Entities and E-E-A-T

Author entities are one of the highest-value uses of sameAs right now. Google’s quality rater guidelines treat author credibility as a direct E-E-A-T signal. A Person entity with sameAs links to a LinkedIn profile, a Wikipedia entry, or a Google Scholar page gives crawlers a way to verify that the author is a real, credentialed person rather than a pseudonym or a content farm byline.

At Salterra, every client site that publishes bylined content gets a Person entity for each named author, with at minimum a LinkedIn and a professional website as sameAs references. For clients in healthcare, legal, and financial verticals — where Google’s E-E-A-T scrutiny is heaviest — we add credentialing sources: state bar profiles for attorneys, medical license board listings for physicians, Google Scholar for academics.

Building a Wikidata Entry

If no Wikidata entry exists for your entity, you can create one. Wikidata is an openly editable structured knowledge base maintained by the Wikimedia Foundation. An entry for a real organization or public figure is entirely legitimate. The entry needs to cite verifiable third-party sources — news coverage, official filings, a Wikipedia article if one exists.

Once the Wikidata item has a stable Q-number, that URL becomes your most powerful sameAs target because it directly feeds Google’s knowledge graph. Do not create a Wikidata entry for a business that has no real third-party coverage. The notability bar exists for a reason, and a deleted entry is worse than no entry — it signals to Google that the entity tried to establish itself in the knowledge graph and was removed.

Local Business Entity Linking

For local service businesses — the majority of what I work with in the Phoenix metro — the most actionable sameAs targets are: the Google Business Profile URL, the Better Business Bureau listing, and any industry-specific directories that Google recognizes as authoritative (Avvo for attorneys, Healthgrades for healthcare, Houzz for home services). These carry weight because they have their own verification processes. A GBP listing requires phone or mail verification. An Avvo listing requires bar number verification. That verification process is exactly what makes them strong external anchors.

Keeping @id Values Consistent Across Pages

One frequently missed detail: if you reference the same entity from multiple pages — which you will, using the @graph pattern covered in nested schema and @graph — the @id value must be byte-for-byte identical across every occurrence. A trailing slash difference creates two separate nodes in the graph rather than one connected entity.

Pick a convention for each entity’s @id and enforce it via your template, not by hand. If you are on WordPress, that means the JSON-LD template generates the @id programmatically from a fixed pattern. Manual consistency at scale is not reliable.

How Long It Takes to See Results

After deploying sameAs markup, the changes work through Google’s index over weeks to months. Knowledge Panel updates are not instant. What you can monitor earlier is the entity recognition in Search Console’s search appearance data — searches for your brand name may start triggering entity-related features before the full Knowledge Panel solidifies.

The schema markup testing guide covers what to check and when in the validation workflow.

sameAs for Content Entities

Entity linking is not limited to organizations and people. Articles can use about pointing to a Thing with its own sameAs reference. A page about JSON-LD can reference the Wikidata entity for JSON-LD as the about target. This signals topical authority — the page is about a recognized concept, not just a keyword — which aligns directly with how Google’s topic model works.

For a structured review of your site’s entity markup — mapping what exists, what is missing, and what the highest-priority additions would be — my schema markup consulting process starts with exactly that audit before any implementation work begins.