The identity’s details

Does the site’s structured identity carry the details its type needs?

Identity · 5 of 100 in Identity · yours to do · fields

What we look for

Naming yourself in structured data is a start; the details are what make it useful. We take your identity and check it has the fields your kind of site needs:

  • An organization (a business, a store, a nonprofit, a newsroom, a school, or a government): description and logo.
  • An organization with premises (one whose identity is a LocalBusiness or a subtype such as Store, Restaurant, or ProfessionalService, or that declares openingHours or openingHoursSpecification; and any government body): also address or areaServed. An Organization, a Corporation, a Person, or software with an address and none of those isn’t asked where it is: a mailing address isn’t a place people visit.
  • A place people come to (a LocalBusiness, a restaurant, a store): also telephone, openingHours or openingHoursSpecification, and geo or a full address with the street and the town.
  • A person: name, url, image, and jobTitle.
  • A podcast (a PodcastSeries): author, description, and image.
  • Software or a product: applicationCategory or category, and offers.
  • Anything else (a publication, a site whose kind nothing says, or a bare Organization that doesn’t say more): name, url, and description.

Your kind of site is told as the directory listings criterion tells it, strongest signal first. The score is the fraction of those fields present. If no identity is declared at all, the criterion is skipped; the structured identity criterion covers that. A meta author tag declares none: it carries a name and nothing more. When the fields your kind needs belong on a node your page doesn’t have (a SoftwareApplication for software, a Person for a person), the fix says to add that node, never to put an application’s properties on your WebSite or Organization.

When your identity is an h-card, every h-card on the home page with the same u-url is read as the same person, so a job title in a footer card counts beside a name in the header.

Why it matters

When an AI assistant describes you, it reaches for exactly these facts: what you’re called, where you are, what you make, who you are, what it costs. If they’re in your structured data, it can state them with confidence. If they’re missing, it has to infer them from your prose, or from someone else’s page about you — and get them wrong, or leave them out.

How to pass

Add the missing fields to the JSON-LD on your home page. The report names which ones. For an organization:

{
  "@context": "https://schema.org",
  "@type": "Organization",
  "@id": "https://example.com/#org",
  "name": "Example",
  "url": "https://example.com/",
  "logo": "https://example.com/logo.png",
  "description": "Project management for design studios.",
  "areaServed": "Worldwide"
}

For a software product:

{
  "@context": "https://schema.org",
  "@type": "SoftwareApplication",
  "name": "Example",
  "url": "https://example.com/",
  "applicationCategory": "BusinessApplication",
  "description": "Project management for design studios.",
  "offers": { "@type": "Offer", "price": "12", "priceCurrency": "USD" }
}

Last changed .

The whole rubric