sameAs links and entity reconciliation: a schema implementation guide

Use sameAs only when two URLs unambiguously identify the same real-world entity. Link an Organization or Person node to official profiles and authoritative records that represent that entity, not to every page that mentions it. Combine those links with a stable @id, consistent names and clear relationships among brands and subsidiaries. sameAs schema must match visible page facts and is not a guaranteed AI ranking factor or a shortcut to a knowledge panel.

Separate identity from association

An official company profile can be sameAs the company. A founder's personal profile, a reseller listing, a news article and a product page are related resources, but they are not identical to the organization. Use founder, employee, brand, parentOrganization, subOrganization or subjectOf when those relationships apply. This distinction matters when companies share a name, operate multiple brands or have acquired older entities. Write a short entity map before editing markup so each node has one scope, canonical page and accountable owner.

Choose references that genuinely disambiguate

• Prefer verified official social and platform profiles maintained by the entity.
• Include authoritative public registry or knowledge-base identifiers only when the record is correct.
• Use current canonical URLs and remove handles transferred to another owner.
• Do not add search-result pages, generic directory categories or articles as sameAs.
• Keep separate regional legal entities distinct even when they share branding.
• Document why each reference is equivalent and when it was last reviewed.

Build the Organization or Person graph with the schema generator, then inspect its deployed relationships using the schema validator. If a legitimate public Wikidata record already exists, the Wikidata guide can help assess and improve it under that community's sourcing rules. Do not create promotional records merely to obtain an identifier, and do not claim an external profile is official when the account lacks organizational control. Visible company pages should explain important brand and ownership relationships in normal language.

Run a reconciliation audit before publishing

1. Inventory names, former names, legal entities, brands, founders and official accounts.
2. Assign a canonical URL and stable @id to every entity that requires a distinct node.
3. Verify ownership and identity at each proposed sameAs destination.
4. Replace merely related links with the appropriate explicit schema relationship or a normal citation.
5. Check reciprocal names, domains, logos and locations for contradictions or namesake collisions.
6. Validate the rendered graph and retest after rebrands, acquisitions or account migrations.

Use an AI visibility scan to capture how assistants currently explain the business, its brands and key people. ModelSaid can preserve recurring identity questions across ChatGPT, Claude, Gemini and Perplexity, making conflation visible over time. Classify whether an error originates in owned markup, visible site copy or an external source before acting. A correction followed by a better answer is useful evidence, not proof of causal ranking impact; proprietary systems may reconcile entities with many signals and update on different schedules.

When two public records conflict, prefer reconciliation over link accumulation. Confirm the entity's legal name, official domain, location and control of the referenced account, then correct the source you own. For community-maintained records, follow their evidence and conflict-of-interest rules instead of rewriting them as marketing copy. Keep screenshots or dated notes for identity-sensitive changes such as a renamed company or transferred handle. If equivalence cannot be established confidently, omit sameAs and use a normal link that describes the relationship. Absence is safer than asserting a false identity connection that may spread the wrong address, executive or ownership information. Recheck downstream pages that reuse the affected @id so the correction is consistent across the site. Include customer support in this audit because identity collisions often surface first as misdirected inquiries, account questions or confusion about which company provides a product.

Maintain a controlled identity graph

Review sameAs destinations quarterly and after executive departures, domain changes, acquisitions or social-handle transfers. Automated checks can flag redirects, failed URLs and duplicate identifiers, while a human must decide whether equivalence still holds. Keep old names as alternateName only when they remain accurate and helpful, and describe succession visibly when one entity replaced another. A small verified set of links is stronger than a large indiscriminate list. Its value is clearer reconciliation for machines and people, not guaranteed AI visibility, citation or control over third-party knowledge.