sameAs and the Knowledge Graph: How to Tell Google Who You Are
Search and AI both resolve you to an entity before they trust you. Organization schema and sameAs are how you declare that identity. A setup guide.
What is an entity, and why does Google resolve me to one?
An entity is a thing search systems treat as a single, identifiable subject: your company, with a stable identity, distinct from every similarly named brand. Before Google or an answer engine repeats anything about you, it tries to decide which entity you are. That step is called entity resolution.
The Knowledge Graph is where Google stores what it has resolved. If it cannot confidently match your site to one entity, it hedges, and a hedged system does not put you in a knowledge panel or quote you in an AI answer. Declaring your identity removes the guesswork.
How does Organization schema declare my identity?
Organization schema is a block of structured data, usually JSON-LD in the page head, that states the facts about your business in a form machines read directly rather than infer. Name, logo, URL, and the profiles you own all go in one place.
The field that does the heavy lifting is sameAs. It is an array of URLs to other places that represent the same entity. Each link is you saying, in effect, that the brand here and the brand there are one and the same. The more verified corroboration you supply, the more confidently a system resolves you.
- name: your exact legal or trading name, spelled the same way every time.
- url: your canonical homepage, one version, not a mix of www and non-www.
- logo: a stable, full-resolution image URL.
- sameAs: an array of links to the profiles you actually control.
Which profiles belong in my sameAs array?
Only profiles that genuinely represent you and that you can keep accurate. A sameAs link to a dead or abandoned account weakens the declaration rather than strengthening it. Favour the platforms a system already weighs as credible in your market.
Review aggregators matter here for the same reason they matter for citation: an independent profile that discusses you is stronger corroboration than your own homepage describing itself.
- Your primary social accounts, the ones you keep current.
- Your Shopify App Store or marketplace listing, if you have one.
- Trustpilot for consumer retail, or G2 and Capterra if you sell software.
- A Crunchbase or Wikidata entry, where one legitimately exists.
Why does consistent naming matter so much?
Because resolution is a matching problem, and inconsistency reads as ambiguity. If your homepage says one trading name, your Trustpilot profile says another, and your social handle says a third, a system has three weak signals instead of one strong one. Consistent naming across profiles strengthens entity recognition; scattered naming dilutes it.
The same applies to your NAP, the name, address, and phone details. Keep them byte-for-byte identical wherever they appear. This is unglamorous housekeeping, and it is also the cheapest entity work you can do.
How does this feed both Google and AI citation?
One declaration serves two readers. The Knowledge Graph uses your Organization schema and sameAs links to build and confirm its record of you, which is what powers knowledge panels and confident search results. Answer engines lean on the same corroboration, because entity recognition feeds both the Google Knowledge Graph and AI citation.
When a model assembles an answer, it prefers entities it can resolve and sources it already trusts. A store with a clean Organization declaration and live aggregator profiles is easier to resolve, and easier to cite, than one a system cannot pin down.
What are the limits of declaring sameAs?
sameAs is a claim, not proof. You are asserting that these profiles are the same entity, and search systems treat that as a signal, not a fact they must accept. The links carry weight in proportion to how credible the destination is and whether the destination corroborates back. A sameAs to a thin or empty profile adds little.
It is also not a ranking lever you pull for an overnight result. Entity recognition accrues. Expect it to make you legible over time rather than to move a position this week. Declared honestly and kept current, it is foundation work, not a quick win.
What this adds up to
Tell both readers who you are, once, consistently, with corroboration. Organization schema states the facts in a machine-readable form. sameAs links you to the profiles that confirm them. Consistent naming keeps the signal clean. Together they help search and AI resolve you to one trustworthy entity.
Most review apps were built for the on-page shopper and stop at the widget, which is the gap BetterReviews is built to close: getting the reviews and reputation you already have readable, corroborated, and cited in search and AI.
- What is the difference between Organization schema and sameAs?
- Organization schema is the whole block of facts about your business; sameAs is one field inside it. The schema declares your name, logo, and URL. The sameAs array lists links to other profiles that represent the same entity, which is the part that corroborates your identity for search and AI.
- Will adding sameAs improve my rankings directly?
- Not directly or overnight. sameAs helps systems resolve you to one entity, which makes you easier to surface and cite over time. It is foundation work that compounds, not a ranking lever that moves a position this week. Treat it as legibility, not a quick win.
- Do I need a Wikipedia or Wikidata entry for this to work?
- No, though one helps if you legitimately qualify. The profiles you already control, social accounts, your marketplace listing, and review aggregators, do the core work. A Wikidata entry is strong corroboration when it exists honestly, but it is not a prerequisite for declaring your entity.
- Does inconsistent naming across my profiles actually hurt me?
- Yes. Inconsistent naming reads as ambiguity, and ambiguity weakens entity resolution. Three different spellings of your brand give a system three weak signals instead of one strong one. Keeping your name and NAP details identical everywhere is the cheapest way to strengthen recognition.