BLOG · ONE CHECK EXPLAINED

One Check Explained: Organization Schema, and the Gap Our Own Check Couldn't See

Published 15 October 2026 · 4 min read

Our free scanner runs 18 deterministic checks. This series takes them one at a time: what the check tests, why it is there, and how to pass it. This one is worth 4 of the 100 points, and it taught us something about our own site.

What the check tests

The scanner reads the JSON-LD blocks on your home page. If any block declares a type of Organization, LocalBusiness, Corporation or WebSite, the check passes and scores 4 points. If none does, it fails with a fix: add Organization schema with a name, URL, logo and sameAs links to your profiles.

That is all it tests: presence. It does not check whether the name in your schema matches the name in your title tag, your Open Graph tags or your LinkedIn page.

Why it is in the score

Schema is one of the few places a site states who it is in a form that needs no reading between the lines: a name, a URL, a logo, an address, and links to the other places the same entity appears. A language model reading prose has to infer those things. We don’t claim that schema causes citations. The score measures readiness, and readiness is not the same as being cited.

How to pass it

A minimal block on the home page:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "@id": "https://www.example.com/#organization",
  "name": "Example",
  "url": "https://www.example.com",
  "logo": "https://www.example.com/logo.png",
  "sameAs": ["https://www.linkedin.com/company/example"]
}
</script>

If the brand belongs to a company with a different legal name, say so with parentOrganization rather than putting the company’s legal name on the brand.

The gap: we passed, and we were still split

In October 2026 we scanned our own site. It scored 100 of 100, with all 18 checks passing, this one included.

Then we read our own JSON-LD by hand. Our Organization block was named “Aura AI”. Our title tag said “Aura AI”. Our product, our LinkedIn page and our app name all said “Aura AI Visibility”. The company’s legal name, which belongs to the parent company, sat on the product. Every one of those is valid schema, and the check passed, because the check only asks whether the schema is there.

What we changed: the Organization is now named “Aura AI Visibility”, with “Aura AI” as an alternateName. The legal name moved to a parentOrganization node for Aura AI Agents L.L.C-FZ, with its own LinkedIn page in sameAs. Every article’s author and publisher now point at the same @id.

Readiness is not visibility

A perfect readiness score is a precondition, not an outcome. It says AI engines can reach, read and quote your site. It doesn’t say they name you when someone asks about your category. That is a separate measurement: sampling real answers over time and reporting each rate with its sample size and confidence interval, mentions and citations counted separately. The free scan does the first; the Monitor does the second.

Check yours by hand

Find your Organization block (view source, search for application/ld+json).
Compare its name with your <title>, og:site_name and your LinkedIn page name. One name, or an alternateName for the short form.
Open every sameAs link and confirm the page names you the same way.
If a parent company owns the brand, put the legal name on the parent, not on the brand.

Run all 18 checks on your domain — free, no signup