The identity’s details

fields · Identity · weight 20 of 145

What we check

Naming yourself in structured data is a start; the details are what make it useful. We take the identity the structured identity rule judges and check it has the fields its type needs:

• Organization, LocalBusiness, and their kin (Corporation, ProfessionalService, Store, Restaurant): name, url, logo, and one of address, areaServed, or description.
• Person: name, url, and one of jobTitle, worksFor, or description.
• SoftwareApplication or WebApplication: name, url, applicationCategory, description, and either offers or isAccessibleForFree.
• Product: name, description, brand, and offers.

The score is the fraction of those fields present. A WebSite, Blog, or Brand has no list, so for those the check is skipped.

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" }
}

Back to the rules