ai

Identify your site with Organization schema

MetricSpot looks for an Organization (or Person) JSON-LD block. It tells search engines and AI who's behind the site — required for the Google Knowledge Graph card.

What this check does

Scans the page for <script type="application/ld+json"> containing an Organization (for companies) or Person (for solo-creator sites) entity at the top level. The check fails when:

  • No Organization / Person block exists anywhere on the site.
  • The block exists but is missing required fields: name, url, and logo.

Usually MetricSpot only needs to find this on the homepage — Google reads it from the canonical site root and applies it to every page.

Why it matters

Organization schema is how you stake your claim to your own brand on the open web.

  • Google Knowledge Graph card. The branded panel that appears on the right of search results when someone searches for your company name comes from Organization schema (cross-referenced with Wikipedia / Wikidata / your social profiles).
  • AI brand recognition. ChatGPT, Perplexity, and Google AI Overviews use the schema to identify which company a page belongs to when citing answers. Without it, the AI might cite “according to a blog post” instead of “according to MetricSpot.”
  • Authorship signal. Modern Google search increasingly favors content from named entities. An anonymous-feeling site (no Org schema, no author bylines, no contact page) ranks behind a site that signals who it is.
  • Logo in the SERP. Google can show your logo next to your search result when Organization schema declares it.

How to fix it

Put a JSON-LD block in the <head> (or anywhere in <body>) of your homepage. One block covers the whole site:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "MetricSpot",
  "url": "https://metricspot.com",
  "logo": "https://metricspot.com/logo.png",
  "description": "Free SEO and AI-readiness audits. 91 checks, no signup.",
  "foundingDate": "2014",
  "sameAs": [
    "https://x.com/metricspot",
    "https://www.linkedin.com/company/metricspot",
    "https://github.com/metricspot"
  ],
  "contactPoint": {
    "@type": "ContactPoint",
    "email": "hello@metricspot.com",
    "contactType": "customer support"
  }
}
</script>

Person for solo sites:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Person",
  "name": "Angel Diaz",
  "url": "https://example.com",
  "image": "https://example.com/me.jpg",
  "jobTitle": "Founder, MetricSpot",
  "sameAs": [
    "https://x.com/angeldiaz",
    "https://www.linkedin.com/in/angeldiaz"
  ]
}
</script>

sameAs is the network signal. List every public profile you own — X, LinkedIn, GitHub, YouTube, Crunchbase, Wikipedia. Google uses sameAs to verify identity across the web and merges the entities into one Knowledge Graph node. The more you list (consistently — same name, same logo), the stronger the signal. See the Organization sameAs page for the detailed rules.

Logo rules.

  • PNG or JPG, ≥112×112, but ≥600×60 is recommended.
  • Hosted on your own domain (not a CDN under a different brand).
  • logo should be the canonical brand mark — not a favicon, not a wordmark on a hero image.

Astro / Next.js — generate at build time:

---
const org = {
  "@context": "https://schema.org",
  "@type": "Organization",
  name: "MetricSpot",
  url: Astro.site,
  logo: new URL("/logo.png", Astro.site).href,
  // ...
};
---
<script type="application/ld+json" set:html={JSON.stringify(org)} />

WordPress — Yoast SEO (Settings → Site basics → Organization) and Rank Math (Titles & Meta → Local SEO) both emit Organization schema automatically once you’ve set the name, logo, and social URLs.

Test it — paste the URL into Google’s Rich Results Test. Confirm the Organization entity parses with name, url, and logo all present.

Frequently asked questions

Should I put Organization schema on every page or just the homepage?

Just the homepage is enough — Google attributes the entity to the whole site. Per-page schemas (Article, Product, FAQPage, etc.) reference the Organization implicitly via the canonical URL.

What’s the difference from JSON-LD structured data generally?

Organization is one of dozens of JSON-LD structured data types. JSON-LD is the format; Organization is one entity inside it. You can (and should) emit several — Organization on the homepage, Article on blog posts, FAQPage on FAQ sections.

Do I need Wikipedia / Wikidata to get a Knowledge Graph card?

It helps. The most reliable path is: Organization schema + Wikidata entry + consistent sameAs to public profiles. Wikidata entries are free and easy to create — the Item creation guide walks through it.

Sources

Last updated 2026-05-11