Structured Data

Social Media Schema

Structured data linking an entity to its official social profiles, usually through sameAs.

Social media schema is the structured data that connects an organisation or person to their official social profiles, using the schema.org sameAs property. It gives search engines corroborating evidence that the accounts and the entity are the same thing, which is what lets a knowledge panel show the right profiles.

Definition

There is no separate "social media" type in schema.org. What people mean is the sameAs property on an Organization or Person node, holding the URLs of that entity's official profiles.

It is an entity-resolution signal rather than a ranking one: it helps a search engine be confident that this company and that X account are the same, which matters for knowledge panels and for disambiguating similarly named organisations.

Why It Matters

Without sameAs, a search engine has to infer which accounts belong to you from links and mentions. Stating it explicitly is cheap and removes the ambiguity.

Example

{
  "@type": "Organization",
  "name": "SlapMyWeb",
  "sameAs": [
    "https://x.com/slapmyweb",
    "https://github.com/slapmyweb"
  ]
}

There is no social media schema type

The name is a misnomer that has stuck. schema.org has no type for a social profile; what people mean is the sameAs property, which takes an array of URLs that identify the same entity elsewhere on the web.

It attaches to whatever the entity is — an Organization for a company, a Person for an author — and its job is disambiguation. It says: this company and that X account and that GitHub organisation are one thing, not three.

{
  "@context": "https://schema.org",
  "@type": "Organization",
  "@id": "https://example.com/#org",
  "name": "Example",
  "url": "https://example.com",
  "sameAs": [
    "https://x.com/example",
    "https://www.linkedin.com/company/example",
    "https://github.com/example"
  ]
}

What it does and does not do

It is an entity-resolution signal, not a ranking one. Adding sameAs will not move a page up the results. What it affects is whether a search engine can confidently connect your site to the accounts, mentions and coverage that exist elsewhere — which is what knowledge panels are built from, and what matters when several organisations share a name.

Include only profiles you actually control and that are actually about the entity. A list padded with directory listings and abandoned accounts weakens the signal rather than strengthening it, because each one is a claim the search engine may check.

The mistake to avoid: repeating it everywhere

Organization markup describes the organisation, and an organisation does not appear once per page. Emitting the same Organization node on all 300 pages of a site is a common template error and it is what audit tools flag as duplicate structured data.

The correct pattern is to define it once, on the homepage, with a stable @id — then reference that @id from other pages' nodes rather than restating the whole thing. @id exists precisely so a node can be named once and pointed at from anywhere.

Person markup for authors is the other half

The same sameAs property applies to a Person, and for anything E-E-A-T-sensitive it matters more than the organisation's.

An author byline that links to nothing is a name. An author with a Person node carrying sameAs links to their professional profiles, published work and speaking history is an identity a search engine can corroborate against sources it already trusts. That is the mechanism behind "who wrote this and why should we believe them" — not a claimed credential in the byline, but a resolvable identity.

Attach the node to the article via author, give it a stable @id, and reuse that id everywhere the same person appears rather than restating the whole node per post.

How SlapMyWeb checks this

The audit reads the Organization node on the homepage and reports whether sameAs is present and what it links to. It also checks that the node is emitted once, on the homepage, rather than repeated on every page — a duplicate Organization on 300 pages is a real finding that this site was itself caught by. Run a page through the schema markup validator to see the graph as a search engine parses it.

Related Tools

Schema Markup Validator

Know the term.
Check your own site.

A free audit tells you whether this is currently costing you score points — and exactly what to change.

Run a free audit

Free foreverNo signupResults in 30s