Structured identity

Does the home page say, in a form a machine can read, who or what the site is?

Identity · 25 of 100 in Identity · yours to do · structured

What we look for

We look on your home page for a statement of who or what the site is, in any honest form a machine can read, and give each the same full credit:

WhatJSON-LDh-card (microformats2)Microdata / RDFa
A namenamep-nameitemprop="name"
A stable address@id / urlu-url (or u-uid)itemid / url
Your profilessameAsrel="me"sameAs

A named identity earns 0.4; a stable address and your profiles add 0.3 each. An identity with no name, or JSON-LD that says nothing about who you are, scores 0.3, never more than a named one; nothing at all scores 0. Only the home page counts here: whether every other page points back to you is the graph criterion’s question.

If the home page declares several identities, we judge a named one that isn’t just a WebSite or Blog (the organization, person, or product behind the site), the first such when several are. In microdata, only a top-level item, or one marked publisher or copyrightHolder, is yours, never an author’s byline inside an article or an excerpt.

Why it matters

An AI assistant reading your home page has to guess what you are from the words on it. Structured data removes the guess: it says this is a company, this is its name, this is its address on the web, and these are its profiles elsewhere. That’s the difference between “a page that mentions Example” and “Example, the company, at example.com.”

The sameAs links matter most. They’re how a machine connects your site to your LinkedIn page, your GitHub, or your Wikidata item, and treats them as one thing. Without them, each is a separate stranger.

How to pass

  1. Say who you are on the home page, in JSON-LD, an h-card, or microdata, with a name, a stable address, and your profiles. In JSON-LD, for one, a block in the head:
    <script type="application/ld+json">
    {
      "@context": "https://schema.org",
      "@type": "Organization",
      "@id": "https://example.com/#org",
      "name": "Example",
      "url": "https://example.com/",
      "logo": "https://example.com/logo.png",
      "sameAs": [
        "https://www.linkedin.com/company/example/",
        "https://github.com/example"
      ]
    }
    </script>
  2. Use the type that fits: Person for a personal site, SoftwareApplication or Product for a product, LocalBusiness for a shop or studio.
  3. Already have an h-card with a u-url and rel="me" links, or microdata with an itemid? That counts in full; you needn’t add JSON-LD too.
  4. On every other page, point back to that identity, so each page says whose it is. The graph criterion shows how.

Evidence

  • Google, “AI features and your website” · December 2025 · strong

    AI features need no special schema; structured data helps as it does for Search, by describing the page.

    Vendor documentation.

  • AirOps · 2026 · moderate

    Pages with JSON-LD were cited 38.5% of the time, against 32.0% without. A correlation, not a cause.

    353,799 pages retrieved for 16,851 ChatGPT queries. AirOps sells AI-visibility tools.

  • Ahrefs · May 2026 · contrary

    Adding JSON-LD brought no meaningful lift on ChatGPT or AI Mode, and a small drop on AI Overviews.

    Before and after: 1,885 pages that added JSON-LD against 4,000 that didn’t, all already cited. Ahrefs sells AI-visibility tracking.

Last changed .

The whole rubric