What it checks
The Cyberbard Schema Checker for AI is a free tool that reads a page's JSON-LD and Microdata and scores how clearly it identifies the brand behind the site, then generates Organization and WebSite JSON-LD to fill the gaps.
"How AI sees you" entity card
The name, URL, logo, description and identity links your markup declares, in one card, exactly as a machine reads them.
sameAs identity links
Which profiles you link (Wikidata, Wikipedia, LinkedIn, Crunchbase, social) to confirm the brand is the same entity across the web.
Key fields per type
Required and recommended fields for 16 common types: Organization, LocalBusiness, Product, Article, FAQPage, BreadcrumbList, WebSite, WebPage, SoftwareApplication, Service, Person, Event and more.
Syntax errors
JSON-LD blocks that don't parse, which machines silently ignore.
Language consistency
Whether inLanguage matches the page's lang attribute, and whether page schema on a multilingual site points at the right URL.
JSON-LD generator
Organization and WebSite JSON-LD pre-filled from your page, including social profiles linked on it. Edit the fields and copy.
How to use the Schema Checker for AI
Enter a page
Start with your homepage, where the Organization markup usually lives. Then try key product or article pages.Read the entity card
If the card is empty or wrong, that is what AI systems can read about your brand from your own markup.Work through the checks
Fix failures first (missing entity, broken JSON, missing required fields), then the warnings.Paste the generated JSON-LD
Copy the generated block into your page's <head> (or your CMS's schema setting), publish, and check again.What this tool does, and what it doesn't (yet)
So you know exactly what the result covers, and where to look for the rest.
What it does
- Extract every JSON-LD block (including @graph) and Microdata item with its properties
- Report JSON-LD blocks with syntax errors
- Build an entity card from Organization, LocalBusiness and their subtypes
- Classify sameAs links by platform and flag when none point to Wikidata, Wikipedia, LinkedIn or Crunchbase
- Check required and recommended fields for 16 common schema types
- Spot an entity url on another domain, a relative logo URL, and a brand name that appears nowhere in the title
- Compare inLanguage with the page's lang attribute and check page URLs on hreflang sites
- Generate editable Organization and WebSite JSON-LD from your existing markup and page meta
Not covered (yet), and what to do instead
RDFa markup isn't read.
Instead: Most sites use JSON-LD; if you use RDFa, Google's Rich Results Test reads it.
Schema added by JavaScript (for example through Google Tag Manager) may not be visible, because we read the HTML your server sends. We tell you when that's likely.
Instead: Put important markup in the server-rendered HTML; many AI crawlers don't run JavaScript either.
One URL per run, not a site-wide crawl.
Instead: Check your homepage plus one page of each template (product, article, location).
It doesn't tell you whether Google will show a rich result.
Instead: Use Google's Rich Results Test for that; eligibility depends on Google's own policies.
It doesn't verify that the facts in your markup match what the page shows.
Instead: Review the entity card yourself; markup must describe visible content.
Why structured data matters for AI search
Structured data is machine-readable markup, usually JSON-LD using the schema.org vocabulary, that states facts about a page explicitly: this is an Organization called X, its logo is here, its official profiles are these. Search engines use it to understand pages, and Google says it uses structured data to understand content and to show rich results; it does not promise a ranking boost.
Why it matters more for AI than for blue links
An AI answer that names businesses has to decide which entity your website belongs to. Text alone is ambiguous: there are many "Apex Plumbing"s. Structured data removes the guesswork:
- Organization / LocalBusiness states your official name, URL, logo and contact details.
- sameAs links connect your site to profiles that describe the same entity (Wikidata, Wikipedia, LinkedIn, Crunchbase, official social accounts). That cross-referencing is how knowledge graphs merge mentions into one entity.
- Type-specific markup (Product, Article, FAQPage, Event…) states the facts an answer may quote: price, author, date, question and answer.
Structured data doesn't guarantee citations. It makes the facts about you unambiguous, which is the part you control.
The checks that matter most
- An Organization (or LocalBusiness) entity on the homepage with name, url, logo and description.
- sameAs links to authoritative profiles, at least one of Wikidata, Wikipedia, LinkedIn or Crunchbase, plus your official social accounts.
- No broken JSON. One trailing comma makes the whole block invisible.
- Required fields on each item: a Product without a name or an Article without a headline is ignored.
- Consistency: the same brand name as your title and og:site_name, an entity url on your own domain, inLanguage matching the page.
About rich results
Google has narrowed some rich results over time: since 2023, FAQ rich results are shown only for well-known government and health sites, and HowTo rich results are no longer shown. The markup is still valid and still readable by machines, but don't add it expecting a visual change in Google.
How this checker differs from a schema validator
An honest comparison, including what we don't do.
Finds JSON-LD and reports syntax errors
Explains how clearly the brand entity is defined
Rates sameAs links by authority (Wikidata, LinkedIn …)
Checks inLanguage and hreflang consistency
Generates JSON-LD pre-filled from your page
Full schema.org validation of every property
Google rich result eligibility
Frequently asked questions
Does schema markup help with AI search?
It helps AI systems and search engines identify who you are and read facts about your pages without guessing. Google says structured data helps it understand content; it doesn't guarantee rankings or citations. Think of it as removing ambiguity rather than as a ranking switch.
Which schema types matter most for GEO?
Start with Organization (or LocalBusiness) on the homepage with name, url, logo, description and sameAs. Then add the type that matches each template: Product for product pages, Article or BlogPosting for posts, FAQPage where you have real Q&A, BreadcrumbList for structure.
What is sameAs, and why link Wikidata?
sameAs lists URLs of other pages about the same entity, such as your LinkedIn company page or Wikidata item. Knowledge graphs use these links to connect mentions of your brand across the web into one entity. Wikidata and Wikipedia are widely used reference sources, but only link them if an entry about you exists.
Why can't the tool see the schema I added with Google Tag Manager?
We read the HTML your server returns, without running JavaScript. Markup injected by Tag Manager or a front-end framework after the page loads isn't in that HTML. Google can render JavaScript, but many AI crawlers don't, so server-rendered JSON-LD is the safer place for important markup.
JSON-LD or Microdata?
Both are valid. JSON-LD is what Google recommends because it sits in one block, separate from your HTML, and is easier to maintain. This tool reads both, and suggests moving to JSON-LD if Microdata is all you have.
Will fixing these issues get me rich results?
Not necessarily. Rich results are Google's decision and depend on its policies (for example FAQ rich results are limited to government and health sites). Use Google's Rich Results Test to check eligibility.
How do I add the generated JSON-LD?
Paste it inside a <script type="application/ld+json"> tag in your page's <head> (the copy button includes the tag). On WordPress, Shopify and most site builders, an SEO plugin or a custom-code setting can hold it. Check the values first; they're pre-filled from your page, not invented.
Does this replace Google's Rich Results Test or the Schema Markup Validator?
No. Those check strict validity and Google feature eligibility. This tool focuses on whether your markup identifies your brand clearly to AI. Use both.
Is it really free? Are there limits?
Yes, it's free and needs no account. To keep it fast for everyone, each visitor can run 20 checks per hour. If you hit the limit, the page tells you when you can try again.
Do you store the URL I check or the results?
No. The address and the results are only shown in your browser and are gone when you leave the page. To enforce the hourly limit we store a one-way hash of your IP address with a counter, nothing else.
What does the full Cyberbard report add?
This tool checks one thing. The full report asks AI the questions your customers ask, shows which competitors it recommends instead of you, scores 50+ factors across your site and the wider web, and writes a Fix plan for your developer plus a Growth plan for the marketing side. You get 3 free reports when you sign up, with no card and no subscription.
More free GEO tools
AI Crawler Checker
Check whether GPTBot, ClaudeBot, PerplexityBot and 14 other AI and search crawlers can reach a page: robots.txt rules plus a live request with each bot's real user agent.
Open the toolllms.txt Generator
Validate an existing llms.txt or generate a draft from your sitemap and navigation, with every link checked and an editor to copy or download the file.
Open the toolAI Citability Checker
Score any page paragraph by paragraph for how easily AI can quote it, with the reasons behind each score and what to change.
Open the toolLast updated