Organization markup on the homepage

What this check looks for

This check only runs against the homepage. If the homepage carries an Organization-family type (Organization, LocalBusiness, Restaurant, and similar business subtypes), it passes, citing the declared name. If it carries other structured data but none from that family, it warns, reporting what was found instead. Non-homepage pages, and homepages where structured data wasn't extracted, report "na".

Why it matters

Organization markup on the homepage is the anchor search engines use to build (or confirm) a knowledge panel for your brand — name, logo, social profiles via sameAs, and contact details all flow from this one block. Without it, a search engine has to infer your brand identity from scattered signals across the site, which is slower and less reliable than a single authoritative declaration. This same block is exactly the kind of entity-grounding data AI answer engines use to confirm who is actually behind a domain before treating claims from it as coming from a real, identifiable organization rather than an anonymous source.

How to fix it

Add Organization (or the appropriate business subtype) JSON-LD to the homepage with as complete a property set as you can:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Acme Audio",
  "url": "https://www.acme.com",
  "logo": "https://www.acme.com/logo.png",
  "sameAs": [
    "https://www.linkedin.com/company/acme-audio",
    "https://twitter.com/acmeaudio"
  ]
}
</script>

If you're a physical or local business, use LocalBusiness (or a more specific subtype) instead of plain Organization so address and hours can be included.