Free Structured Data Tool

Schema Markup Checker

See every schema type a page has, and which high-value ones it is missing entirely

We read every JSON-LD block on the page and tell you what's there, what fails to parse, and which high-value types are missing.

How it works

No black box. Here's exactly what Schema Markup Checker checks.

  1. 1

    We fetch the page

    Server-side, with a sane timeout. We don't store the URL.

  2. 2

    We parse every JSON-LD block

    Each block is parsed on its own, and any that fail are surfaced separately so you can fix them in isolation.

  3. 3

    We classify @type values

    Organization, Article, Product, BreadcrumbList, WebSite, FAQPage and more: every type on the page, named so you can see what Google and AI engines can read.

  4. 4

    We flag missing high-value schemas

    This is the part a syntax check leaves out. Coverage of the types that matter most for AI Visibility and rich SERP results, with concrete add-this recommendations.

Why this matters

Schema is the most reliable signal you can send about what your site actually is. Every other signal is heuristic. Schema is explicit. AI engines use it to attach a verifiable entity to citations, and Google uses it for rich results, breadcrumbs, and knowledge panels. The work is genuinely 10 minutes per page; the leverage is months of compounding visibility.

  • AI engines (ChatGPT, Perplexity, AI Overviews) reference structured data to confirm "this is a real organization" before citing.
  • Google rich results (review stars, breadcrumbs, product details) unlock through specific schema types. FAQ is no longer one of them: Google stopped showing FAQ rich results in Search on May 7, 2026.
  • Schema that's present but invalid is silently ignored. Validation is half the win.
  • Schema also forces clarity: writing it forces you to articulate the page's entity in unambiguous terms.

Want the full story across every page?

The Schema Markup Checker checks one URL. CrawlTide audits your whole site, tracks issues over time, watches your AI Visibility weekly, and publishes articles to WordPress, Webflow, and Shopify.

Run a full audit freeSee all features

No credit card. Free tier covers a small site end-to-end.

Frequently asked questions

Does this validate against schema.org's full spec?
Not in v1. We check parseability, presence of @type, and required fields for the most common types (Organization, Article, Product, FAQPage). For deep validation use Google's Rich Results Test alongside this. They're complementary.
Should every page have schema?
Most pages benefit. The minimum is Organization + WebSite on the homepage. Article/BlogPosting on blog posts. Product on product pages. Don't schema-stuff pages with content that doesn't exist. Google penalizes that.
What's the highest-ROI schema to add first?
Organization on the homepage with name, logo, sameAs (social profile URLs), and contact. That single block is the foundation every other schema reference attaches to. Five minutes of work, lifetime of compounding entity confidence.
Is FAQPage schema still worth adding?
Not for Google rich results. Google stopped showing FAQ rich results in Search on May 7, 2026, so FAQPage markup no longer earns an FAQ snippet, and this checker neither scores it nor recommends adding it. It is still valid schema.org markup, so existing FAQPage that matches a visible Q&A section does no harm. For AI search, Google says no special markup is needed to appear in AI Overviews or AI Mode; clear, question-shaped headings with direct answers in the visible text do more than the markup.
Can you have too much schema?
You can have wrong schema: overlapping types, schema describing content that isn't on the page, FAQ schema for fake FAQs. Google penalizes deceptive structured data. The fix is to only mark up content that actually exists on the page.
How is this different from Google's Rich Results Test?
Rich Results Test tells you whether your schema qualifies for specific rich results. This tool tells you what schema you have, what's missing, and prioritizes the additions. Use Rich Results Test to validate, use this to plan.
Is a schema markup validator the same thing as a checker or a tester?
People use the words interchangeably, but there is a real difference worth knowing. A checker or tester tells you what is on the page and whether it parses, which is what this tool does, plus the part a syntax check cannot tell you: which high-value types the page is missing entirely. A true validator checks your markup against the full Schema.org specification, property by property. This tool does not do that, and it would be misleading to say otherwise. For spec-level validation use the Schema.org validator or Google's Rich Results Test. Use this to see the whole picture and decide what to add next.

More free tools

See all →
AI Visibility

AI Visibility Check

Score how ready a page is to be understood and cited by AI search, with prioritized fixes

AI Visibility

AI Answer Readiness Checker

See if a single page is structured to win direct answers in ChatGPT, Perplexity, and AI Overviews

Technical SEO

SEO Score Checker

A quick health score for any URL: title, meta, headings, links, and basic technical SEO