AI Summary: Entity optimization is identity hygiene, not a ranking shortcut. Publish an accurate Organization description on the home or organization page, use a stable identifier, and add sameAs only for external pages that unambiguously identify the same organization; Google says this can aid understanding and disambiguation, not guarantee a knowledge panel or AI citation.
Start with one canonical identity
Choose the page that explains the organization best, usually the home page or an About page. Make the visible name, legal or public description, logo, URL, contact details, and relevant locations agree with the business. Use an Organization object, or the most specific subtype that actually fits, and give it a stable @id such as https://example.com/#organization. Google recommends organization markup on a home or organization page rather than requiring it on every URL. [1]
The graph should reduce ambiguity, not create a second story. If JSON-LD invents an address or names an unrelated product, omit it. Validate the graph against the visible page.
Use sameAs narrowly
Schema.org defines sameAs as a URL of a reference page that unambiguously indicates the item's identity, such as an official profile, Wikipedia page, Wikidata entry, or official website. [2] Google supports multiple sameAs URLs where applicable. [1] That does not mean every social link belongs there. Include only profiles controlled by, or clearly representing, the same organization. A directory listing, partner page, campaign URL, or loosely related brand may be a useful citation link but is not automatically an identity equivalence.
| Field | Quality test |
|---|---|
name | Matches the visible organization name |
url | Resolves to the canonical identity page |
logo | Is crawlable, representative, and current |
sameAs | Each external URL unambiguously identifies the same entity |
@id | Remains stable across templates and releases |
Verification checklist
Parse the rendered JSON-LD as JSON and check that the @id, url, and sameAs values are absolute HTTPS URLs. Open each external reference and record why it identifies the same organization. Compare the graph with the visible name, logo, description, and contact facts. Remove stale or ambiguous references, then validate the final markup with the relevant structured-data tool.
A good entity graph makes one identity easier to verify; it cannot make unrelated pages equivalent or compel display.