Tools
Schema Markup Checker | Free Website Test
Paste a URL to check schema markup on any website. The checker finds LocalBusiness, Organization, FAQPage, and Service JSON-LD, then provides a ready-to-paste snippet for anything missing.
What this checks and why
Paste any public URL and the checker fetches the page the way a search crawler sees it — the raw HTML, without running JavaScript — and lists every JSON-LD block it finds, grouped by schema type. Each finding names the type (Organization, LocalBusiness, FAQPage, and the rest), the properties present, and what looks missing for that kind of page.
Why this matters: crawlers and answer engines use schema to resolve which business a page belongs to. Pages with clear identity markup are easier to attribute, and attribution is a precondition for being cited. The checker tells you the starting position; the fix list tells you the next edit.
Worked example: this page
Running the checker on this page's own URL reports five JSON-LD blocks: Organization (who publishes the site), SoftwareApplication (what the checker tool is, with its description and URL), WebPage (this page's title and canonical URL), FAQPage (the questions and answers below, mirrored word-for-word from the visible text), and BreadcrumbList (Home → Tools → this page). Nothing is missing for a tool page of this kind, so the result is a clean pass with no fix list.
A typical local-business homepage, by contrast, comes back with Organization but no LocalBusiness block — no address, opening hours, or geo coordinates — and the checker returns a ready-to-paste LocalBusiness snippet with placeholders for exactly those fields. That is the whole loop: check, paste the missing block, redeploy, and recheck until the pass is clean.
What schema markup can establish
JSON-LD can identify an organization, local business, service, or visible FAQ in a structured form. It helps crawlers resolve page meaning, but it does not replace useful content or guarantee a rich result, AI citation, Knowledge Panel, or recommendation.
How to fix missing schema safely
Add only accurate properties that match the rendered page. Use the most specific appropriate type, stable canonical URLs, and official profile links that resolve to the same entity. FAQPage markup must mirror questions and answers users can actually see.
Schema checker vs schema validator
A schema markup checker identifies the JSON-LD types and entity fields present on a public page. A validator focuses on syntax and vocabulary rules, while Google's Rich Results Test checks eligibility for supported search features. Use the checker first to find the page's structure, then validate corrected markup with the Rich Results Test.
Recheck the deployed page, then validate it with the Schema.org validator. Fix syntax and entity mismatches before adding more schema types.
Schema markup and your AI visibility
VisiScan's signal auditor checks for Organization, LocalBusiness, FAQPage, Service, and Product schema on your pages. Missing or incorrect schema lowers your Readiness score and makes it harder for AI engines to resolve your business identity. The checker above tells you which schema types are present — fix the gaps, then run a full scan to measure whether AI engines name you more often. For how structured data fits into being retrieved and cited, see how to get your business cited by ChatGPT.
Schema markup checker FAQ
What does a schema markup checker test?
It checks the public page for JSON-LD schema such as LocalBusiness, Organization, FAQPage, and Service, then reports which types are present and which may be missing.
Is a schema checker the same as a Rich Results Test?
No. A schema checker identifies the JSON-LD types and entity signals on a page. Google's Rich Results Test checks eligibility for supported Google rich-result features. Use both when validating structured data.
Can schema markup guarantee an AI citation?
No. Accurate schema can clarify page type and business identity, but AI citations also depend on crawl access, relevance, content quality, authority, and the answer engine's retrieval process.
Does the checker see schema added by JavaScript?
No. The checker reads the server-rendered HTML — the same view a crawler gets without executing scripts. If your JSON-LD is injected by client-side JavaScript after load, move it into the server-rendered document so crawlers can see it.
How often should a page's schema be rechecked?
Recheck after every deploy that touches page templates, structured-data components, or the content management setup, and on a quarterly baseline even when nothing changed. Schema drifts silently when templates are edited for other reasons.