Structured Data That Says Who You Are

Most sites with structured data have the page type and nothing else. The publisher node is the piece that actually matters, and it belongs in the template.

By Krisada. Updated September 7, 2026.

If you add one thing to your structured data this week, make it a publisher node. Anything deciding whether to trust a claim on your page needs to know whose claim it is, and on most sites that information exists nowhere a machine can read it.

What is usually there, and what is usually missing

A typical site with any structured data at all has an Article or WebPage type declared, added by a plugin. That tells a retriever what shape the content is. It says nothing about who published it, whether that publisher exists anywhere else, or whether the four hundred other pages on the site come from the same source.

QuickRankAI checks five things in this group for a reason. Presence alone is the low bar.

The minimum useful set

{
  "@context": "https://schema.org",
  "@graph": [
    {
      "@type": "Organization",
      "@id": "https://example.com/#organization",
      "name": "Example Company",
      "url": "https://example.com/",
      "logo": "https://example.com/logo.png",
      "sameAs": [
        "https://www.linkedin.com/company/example",
        "https://www.wikidata.org/wiki/Q00000"
      ]
    },
    {
      "@type": "WebPage",
      "@id": "https://example.com/your-page/#webpage",
      "url": "https://example.com/your-page/",
      "name": "The page title",
      "isPartOf": { "@id": "https://example.com/#website" },
      "publisher": { "@id": "https://example.com/#organization" }
    }
  ]
}

Three things are doing real work there. The Organization node names the publisher. The sameAs array corroborates it against references that already exist. And the identifiers let the WebPage node point at the Organization instead of repeating it, so the two describe one connected thing rather than two unrelated ones.

Why sameAs matters more than it looks

A name in a JSON block is a string. Anyone can write any string. What makes it an entity is that it resolves to something already established elsewhere, and sameAs is how you say which something.

Use references you actually control or that unambiguously refer to you. Wikidata, Wikipedia, LinkedIn, Crunchbase, an official business register, verified social accounts. Padding the list with profiles that do not clearly refer to the same entity weakens the claim instead of strengthening it.

Put it in the template, not the page

This is the part that gets skipped. A site where the blog posts carry a publisher node and nothing else does has told machines that most of its content was published by nobody in particular.

The Organization node is identical on every page. It belongs in the shared layout. The page-specific nodes reference it by identifier. One edit, whole site.

One warning about plugins

If two things are both emitting structured data, you do not get twice as much. You get two Organization nodes with different identifiers, or two Article nodes disagreeing about the publication date, and anything reading it has to decide which one is lying.

Pick one source of structured data and turn the other off. QuickRankAI reports how many nodes it found, which is a quick way to notice that a page has considerably more than it should.

How to confirm the repair landed

Run the page through Schema.org's validator or Google's Rich Results Test, then re-run the inspection. Entity Clarity is the category that moves, and it should move a long way, because five separate checks are sitting in it.