Practical structured data guide
Organization Schema: use sameAs and @id without creating a fake entity
Organization markup can connect a visible brand with its official website and profiles. It should clarify identity, not manufacture authority, reviews, awards or relationships that do not exist.
Quick answer
Use a stable `@id`, the canonical organization URL and only official profiles that represent the same entity. Reuse the identifier when another visible node, such as WebSite, names that organization as publisher.
What sameAs is for
`sameAs` can point to external profiles that unambiguously represent the same organization. It is not a list of every mention of the brand and not a shortcut to borrow another company’s reputation.
Why @id helps
A stable `@id` lets multiple JSON-LD nodes refer to one entity. For example, a WebSite can use the Organization identifier as its publisher. The linked entity still needs to be represented accurately on the page.
Avoiding entity pollution
Do not add unrelated social profiles, fabricated awards, fake reviews or names that are not visible and supportable. Fewer accurate properties are better than a large inaccurate graph.
Copy-ready JSON-LD example
Replace every placeholder with facts that are true and visible on your own page. Do not publish the sample identity, URL or values unchanged.
{
"@context": "https://schema.org",
"@type": "Organization",
"@id": "https://example.com/#organization",
"name": "Example Studio",
"url": "https://example.com/",
"logo": "https://example.com/logo.png",
"sameAs": [
"https://www.linkedin.com/company/example-studio"
]
}What fails
The markup attaches unrelated social profiles or uses `sameAs` to imply a relationship that the organization does not control.
What works better
Link only matching official profiles, keep the stable identifier and reuse it consistently in connected entities.
Publishing checklist
- Organization name, URL and logo are accurate.
- Every sameAs URL represents the same organization.
- The logo is relevant, crawlable and accessible.
- Connected nodes reuse the same stable @id.
- No authority, review or affiliation claims are invented.
A reliable workflow
Generate or edit the markup, validate the exact code, compare important properties with the visible page, publish it, then inspect the live URL. For critical pages, save a baseline and monitor for field changes after releases. A valid object can still be inaccurate if its data becomes stale.