Citare Tools · Free
JSON-LD Inspector
Paste any URL — we fetch the page, extract every <script type="application/ld+json"> block, validate each entity against schema.org expectations, and highlight the schemas that matter most for AI citations.
Free. No signup. Cached 24h.
Frequently asked
What is JSON-LD and why does it matter for AI search?
JSON-LD (JavaScript Object Notation for Linked Data) is the schema.org format for embedding structured data in your HTML. AI search engines (ChatGPT, Claude, Perplexity, Gemini) and traditional search engines (Google, Bing) use JSON-LD to understand exactly what a page is about — product price, article author, FAQ Q&A pairs, business hours, recipe ingredients, etc. — without inferring from prose. Pages with valid JSON-LD get richer citation snippets, more accurate AI grounding, and eligible for Google's rich-result UI (review stars, breadcrumbs, FAQ accordions in SERPs). The Citare Inspector extracts every JSON-LD block on a page, validates each entity against schema.org's required-field expectations, and tells you exactly what's missing.
What schema types do AI search platforms prefer for citations?
For most sites, the highest-leverage schemas are Article (for blog posts, news), Product (with offers, ratings, brand), Organization + LocalBusiness (for brand identity), FAQPage (for direct Q&A grounding), HowTo (for procedural content), and BreadcrumbList (for nav understanding). The Citare Inspector flags entities that match these "high-value for AI" types so you know which ones to fix first. Avoid one anti-pattern: stuffing schemas you don't actually display on-page — Google and the AI platforms penalize spammy structured data, and FAQPage in particular gets ignored if the answers don't appear in the visible HTML.
Why is my JSON-LD valid but not generating rich results?
Valid JSON-LD is necessary but not sufficient for rich results. Google's rich-result UI has additional opinionated requirements beyond schema.org's baseline: image dimensions for Article, offer.price for Product, aggregateRating with reviewCount for ratings, etc. The Citare Inspector validates against schema.org's required fields (the baseline AI grounding needs), not Google's stricter rich-result rules — for the latter, run Google's own Rich Results Test. The two tools are complementary: pass Citare for AI-citation eligibility, pass Google's tool for rich-result eligibility.
Does the inspector send my URL anywhere?
We fetch the URL server-side (one HTTPS GET) to read the HTML, extract the JSON-LD blocks, validate, and return the report. We don't store the URL or the page content; we don't share with any third party. The result is cached for 24 hours in our edge cache keyed by URL to keep the tool fast for repeated checks — that cache is publicly readable in the sense that anyone hitting the same URL gets the same cached result, but no PII is stored.