Use it for
Service pages, guides, tools, ecommerce product templates and articles where AI search visibility matters.
Paste any URL. The tool fetches the page, extracts every JSON-LD block, and scores it on what AI engines actually use to cite sources: entity graph, Wikidata, named author, freshness. Not just Google rich-result eligibility.
Schema.org and Google's Rich Results Test are still worth using. They tell you whether the markup is valid and whether Google can show a visible search enhancement.
This tool answers the next question: can an AI search engine connect the page to a real entity, named author, publisher, sameAs graph and extractable answer blocks? That is the gap generic validators miss.
Service pages, guides, tools, ecommerce product templates and articles where AI search visibility matters.
JSON-LD blocks, @id references, Person and Organization links, FAQ depth, dates and sameAs quality.
AI Overview or ChatGPT citation. Schema helps clarity. The page still needs crawl access, proof and useful visible copy.
Run a check to see the score.
Drop-in JSON-LD blocks for the schema types we recommended. Pre-filled from this page where we could detect facts (title, og:image, social profiles, dates, author byline). Open each, tweak the placeholders, paste into <head>.
Schema scored for citation in
Scoring weights reflect what each engine actually rewards - Wikidata, named-author E-E-A-T, @graph linkage, freshness. Not just Google rich-result eligibility.
Generic schema validators check syntax against schema.org and stop there. AI search engines (ChatGPT, Perplexity, Claude, Gemini, Google AI Mode) need a deeper set of signals before they will cite a source - the ones below.
Wikidata Q-numbers are the strongest entity-disambiguation signal AI engines use. Without one, two same-named businesses bleed into each other in AI answers. This tool flags Wikidata absence as a Tier-1 issue, not a nice-to-have.
Not all sameAs links are equal. Tier-1 (Wikidata, gov.uk, Companies House) > Tier-2 (LinkedIn, Crunchbase, G2) > Tier-3 (social only). The tool counts each tier and warns when sameAs is social-only - the most common entity-graph weakness.
AI engines traverse schema via @id references. This tool walks every @id reference, errors on broken refs, errors on duplicate @ids, and warns when 3+ blocks ship with zero cross-references (siloed nodes that look like unrelated entities).
Plain string authors ("author: Jane Smith") are invisible to AI engines - they cannot resolve the writer's identity. The tool flags this as an error on Article/BlogPosting/NewsArticle nodes, even though generic validators pass it.
FAQPage with one Q&A or single-line answers is gaming the schema for a rich-result hint without the substance. The tool counts substantive answers (>=80 chars) and requires >=4 for the citation credit.
Industry analysis (PromptAlpha, Ziptie) puts freshness around 30 to 40 percent of Perplexity ranking. The tool reads dateModified from your schema and credits content under 30 days, soft-credits under 90 days, and penalises year-old dates.
Free tools are good at diagnostics. They cannot get you a Wikidata Q-number, rebuild your entity graph across every template, or seed the citations that actually move AI rankings. That is the consultancy side.
Entity graph rebuild, Wikidata setup, @id-linked schema across every template, citation seeding on Reddit / LinkedIn / podcasts. The full programme this score is measuring.
See the GEO service AI ConsultingIf your schema is broken because the brand has no AI strategy at all, fixing the JSON-LD is treating the symptom. AI consulting covers the wider plan - AI search, internal AI workflows, AI-led content.
See AI Consulting SEO ManagementFor sites that need schema, technical SEO, content and authority work landed together rather than as separate projects. Monthly retainer with senior delivery, not account-manager triage.
See SEO Management Technical SEOIf schema is missing, duplicated or disconnected across templates, the fix belongs in technical SEO. I map the issue and turn it into developer-ready tickets.
See Technical SEOThe tool checks one URL at a time. A real AI schema audit covers every template, builds the entity graph with proper @id linkage, gets you a Wikidata Q-number and ships the fixes. 30-min call to scope it, no obligation.