Free
No signup
Fast
Privacy-friendly

Back to Category

Schema Markup Validator

Q: What problem does schema validation solve?

It finds missing, incomplete, or conflicting JSON-LD — especially broken FAQPage and HowTo — so structured data matches visible content.

Q: Who uses this tool?

Technical SEO, developers, and content teams use it after CMS schema plugins, FAQ blocks, and recipe/howto templates change.

Q: Does a green score guarantee rich results?

No. This is a heuristic completeness audit . Google Rich Results eligibility also depends on guidelines and indexing.

Q: What FAQPage fields are required here?

Each FAQ mainEntity question needs a name and an acceptedAnswer.text that matches visible Q&A.

Q: What HowTo fields are checked?

HowTo needs a name and a step list with name or text on each step.

Q: How does this differ from a full SEO audit?

This page is a structured-data specialist report . A full SEO audit covers headings, links, and broader technical categories.

Q: What evidence appears in findings?

Reports include type counts, FAQ/HowTo issue lists, missing recommended properties, and sample node keys .

Inventory JSON-LD types, validate FAQPage and HowTo completeness, and flag missing recommended properties.

Free · API · MCPToolYour platform

Use Schema Markup Validator three ways

The free Schema Markup Validator on this page works in your browser. The same workflow is available via REST API for apps and via MCP for Cursor, Claude, and other agents — one API key, one plan, one quota. This tool is part of the seo-apis module under Digital Tools.

Free in browserUse Schema Markup Validator here — no account required.
REST APICall from your server with X-Api-Key.
MCP for agentsConnect Cursor or Claude to ToolYour MCP with the same key.

1. Get an API keySign in and open Dashboard → API Keys (works for REST and MCP).
2. Call or connectUse the REST API from your server, or paste the MCP URL into your agent config.
3. Same qualityOutput matches the free web tool across all three surfaces.

Manage API keys MCP setup API reference Create free account

What is Schema Markup Validator?

Broken or empty structured data wastes rich-result opportunity and confuses entity understanding. FAQPage blocks without acceptedAnswer.text, HowTo nodes without steps, and duplicate Organization graphs are common after theme or plugin updates.

This Schema Markup Validator fetches a public URL, inventories JSON-LD types (including @graph), checks FAQPage question/answer completeness, HowTo step completeness, and flags missing recommended properties for common types. You get a type graph, severity findings, evidence samples, and fix steps — not a promise of Google Rich Results approval.

Use it before launching FAQ or HowTo templates, after SEO-plugin upgrades, and when Search Console rich-result reports show invalid items.

What are common questions about Schema Markup Validator?

What problem does schema validation solve?

It finds missing, incomplete, or conflicting JSON-LD — especially broken FAQPage and HowTo — so structured data matches visible content.

Who uses this tool?

Technical SEO, developers, and content teams use it after CMS schema plugins, FAQ blocks, and recipe/howto templates change.

Does a green score guarantee rich results?

No. This is a heuristic completeness audit. Google Rich Results eligibility also depends on guidelines and indexing.

What FAQPage fields are required here?

Each FAQ mainEntity question needs a name and an acceptedAnswer.text that matches visible Q&A.

What HowTo fields are checked?

HowTo needs a name and a step list with name or text on each step.

Is Microdata supported?

Microdata presence is counted. Deep FAQ/HowTo property checks focus on JSON-LD, the format most CMS tools emit.

How does this differ from a full SEO audit?

This page is a structured-data specialist report. A full SEO audit covers headings, links, and broader technical categories.

What evidence appears in findings?

Reports include type counts, FAQ/HowTo issue lists, missing recommended properties, and sample node keys.

What are the key features of Schema Markup Validator?

JSON-LD type inventory

Lists @type values with counts, including @graph expansion.

FAQPage completeness

Checks mainEntity questions for name and acceptedAnswer.text.

HowTo step validation

Flags missing HowTo name or empty step arrays.

Recommended properties

Highlights missing common fields for Article, Product, Organization, and more.

Severity findings

Ranks incomplete markup with evidence and how-to-fix steps.

Honest limitations

States heuristic scope — not Google’s Rich Results Test.

How do you use Schema Markup Validator?

Enter a public HTTPS URL

Paste the page that embeds JSON-LD (article, FAQ, product, or howto).

Run schema validation

Parse JSON-LD, score type coverage, and evaluate FAQ/HowTo completeness.

Fix incomplete nodes

Update CMS schema fields or script tags using each finding’s evidence.

Why incomplete FAQ and HowTo markup fails in practice

Publishers often enable “FAQ schema” toggles that emit empty or partial nodes. Search systems that consume FAQPage expect question name and answer text aligned with visible content. HowTo without steps is likewise incomplete.

This tool surfaces those gaps with concrete issue strings and counts. schema.org type names such as Organization, Article, Product, and BreadcrumbList also get recommended-property checks so entity pages are not hollow shells.

Use cases: plugins, migrations, and rich-result cleanup

After plugin updates — Re-run cornerstone URLs when Yoast/RankMath/theme JSON-LD changes.

FAQ and HowTo launches — Validate the first three templates before scaling.

Search Console invalid items — Reproduce the URL here and match missing properties to evidence.

Pair with SERP Snippet Preview for title/description CTR, and SEO Audit for whole-page scoring.

Scope and limitations

Static HTML JSON-LD and counted microdata only. Client-injected schema after hydration is invisible. Passing this audit does not guarantee rich results. Keep markup synchronized with visible page content.