Organization JSON-LD and sameAs: telling models which entity you are

The entity problem

Models reason about entities, not URLs. When a user asks about 'Brand', the model has a cluster of things it has read: reviews, a Wikipedia line, LinkedIn, a news piece, your own pages. If that cluster is well connected, everything reinforces one entity and the model speaks about it confidently. If it is loosely connected, you are several weak entities, and the answer either hedges or picks a better-connected rival. Your homepage is the one place you control that can state, in machine terms, 'this domain is this organisation, and these profiles are also us'.

The block

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "@id": "https://www.brand.ch/#organization",
  "name": "Brand AG",
  "alternateName": "Brand",
  "url": "https://www.brand.ch/",
  "logo": "https://www.brand.ch/logo.png",
  "description": "Swiss outdoor equipment retailer, founded 1998, stores in Zürich and Bern.",
  "foundingDate": "1998",
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "Musterstrasse 1",
    "postalCode": "8001",
    "addressLocality": "Zürich",
    "addressCountry": "CH"
  },
  "contactPoint": {
    "@type": "ContactPoint",
    "contactType": "customer service",
    "email": "[email protected]",
    "availableLanguage": ["de", "fr", "en"]
  },
  "sameAs": [
    "https://www.wikidata.org/wiki/Q00000000",
    "https://www.linkedin.com/company/brand-ag",
    "https://www.instagram.com/brand.ch",
    "https://www.zefix.ch/…"
  ]
}
</script>

• `sameAs` does the joining. List the profiles that unambiguously refer to you: Wikidata if you have an item, the commercial register entry, LinkedIn, the social accounts you actually run. Skip profiles you do not control.
• `@id` gives the entity a stable name you can reference from other pages: an Article's publisher or a Product's brand can point at https://www.brand.ch/#organization instead of repeating the block.
• `description` is read. One or two factual sentences: what you do, where, since when. It is the sentence a model is most likely to paraphrase when it names you.
• Use the specific subtype when it fits: LocalBusiness, OnlineStore, NewsMediaOrganization. They inherit everything from Organization and add fields such as opening hours or masthead.
• Google documents this in its Organization structured data guidance, including which fields feed its knowledge panel; the same fields are what other engines read.

WebSite markup and the site name

A companion WebSite block names the site itself and can carry a SearchAction for your internal search. Its name is what Google uses for the site name shown in results, which is also the label answer engines often print beside a citation. Keep it identical to the Organization.name or alternateName so the two do not compete.

{
  "@context": "https://schema.org",
  "@type": "WebSite",
  "name": "Brand",
  "url": "https://www.brand.ch/",
  "publisher": { "@id": "https://www.brand.ch/#organization" },
  "inLanguage": "de-CH"
}

What Qomvia checks

Organisation structured data under Identity is worth 5 points. It looks for an Organization or WebSite node in the homepage JSON-LD. Both name and url present with a non-empty sameAs array: full marks. name and url without sameAs: 3 points, 'no sameAs profiles'. Markup present but missing one of those: 2. Nothing: 0, with the finding 'The site does not say who it is'. It is one of the fastest checks to fix, and it is the one that most directly affects whether you are named rather than merely cited.

Questions

We have no Wikidata item. Is sameAs still worth it?

Yes. The commercial register, LinkedIn and your real social accounts are enough to join the entity. Creating a Wikidata item is possible if you meet its notability rules, but it is not required.

Should the block be on every page or only the homepage?

The full block on the homepage. Other pages reference it by @id from their own markup (Article publisher, Product brand) rather than repeating it.

Does the logo field matter for AI answers?

Less than name, url, description and sameAs. It feeds knowledge panels and some citation cards. Use a square or wide PNG/SVG on a plain background.