sameAs schema: point entity markup at profiles that are really you

List only confirmed profiles

Official social profiles, a parent company page, and a Wikidata or directory entry you have checked can belong in sameAs. A search result that mentions your name does not.

The URLs should resolve and clearly show the same name and site. A dead profile keeps an old description in the graph.

Put sameAs on the organisation, not on every article

Organisation markup on the about page or the homepage is the right home. Repeating a long sameAs array on every guide adds nothing and drifts when a template copies stale links.

The visible page should mention the parent or the profile if you are asking machines to treat it as identity. Hidden-only relationships are weaker.

• Profiles you control or have verified.
• Organisation markup on the entity page.
• Remove URLs that no longer represent you.

Revalidate when branding changes

A rename, a merger, or a domain move should update sameAs in the same release as the about page. Old profiles should redirect or state the new name.

Test the JSON-LD. A sameAs list full of homepage variants (http, https, www) is not a set of external identities. Those belong in redirects.

Does sameAs create a knowledge panel?

No. It is one clue that URLs refer to the same entity. Panels still depend on broader consistency and notability.

Can sameAs include competitor or partner sites?

Only if that URL is genuinely the same entity, which a partner almost never is. Link partners in the prose instead.