Free Structured Data Tool

Schema Markup Checker

See which structured data types your page exposes — and which AI-friendly ones it's missing

We parse every JSON-LD block on the page and tell you what's there, what's broken, and what's 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 extract every JSON-LD block

    Then parse each one and surface invalid blocks separately so you can fix them in isolation.

  3. 3

    We classify @type values

    Organization, FAQPage, Article, Product, BreadcrumbList, WebSite — everything that helps Google rich results and AI citation.

  4. 4

    We flag missing high-value schemas

    Coverage of the schemas 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, FAQ snippets, 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 — stars, FAQ accordions, breadcrumbs, sitelinks — all unlock through specific schema types.
  • 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 pushes meta-tag fixes straight to your CMS.

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. FAQPage anywhere there's a real FAQ section. 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.
Will adding FAQPage schema actually help with AI engines?
Yes — AI engines preferentially extract from FAQ-formatted content because the question/answer structure mirrors how users prompt them. We see this consistently in the full CrawlTide product: pages with FAQPage schema get cited more often than otherwise-equivalent pages without it.
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.