RevealTheme logo

Schema Markup Validator

Extract and validate JSON-LD structured data from any URL. See what schema types are present and whether they parse correctly.

What is schema markup and why does it matter for rankings?

Schema.org structured data is a shared vocabulary — maintained by Google, Microsoft, Yahoo, and Yandex — that lets you tell search engines what a page is, beyond just its prose. Without schema, Google reads your page like a human: parsing the words and guessing what's important. With schema, you explicitly tag 'this is a product, priced $29, with 4.5 stars from 1,250 reviews' or 'this is a how-to guide with these 7 steps'. That structured information powers rich results — the visually-enhanced SERP entries that include star ratings, prices, recipe cards, FAQ accordions, event dates, and breadcrumbs. Rich results don't just look better; they get 30-50% higher click-through rates on average. The three formats Google accepts are JSON-LD (recommended — separate from your HTML, easiest to maintain), Microdata (inline HTML attributes — legacy), and RDFa (XML-based — also legacy). All modern advice is JSON-LD, which is what this validator extracts and parses. Beyond rich results, schema also helps Google understand entity relationships (which builds your knowledge graph presence), feeds AI overviews and answer boxes, and signals topical expertise. The most common schema types worth implementing on a content site: Organization (sitewide identity), WebSite (with SiteSearchAction for the search box rich result), BreadcrumbList (every page), Article (blog posts), FAQPage (FAQs), HowTo (tutorials), Product (ecommerce), Review (reviews and comparisons), VideoObject (any embedded video). This tool fetches a URL, parses every <script type="application/ld+json"> block, and reports parse errors plus the detected @type for each. For Google-specific eligibility checks, also run your URL through Google's Rich Results Test (search.google.com/test/rich-results) — that tool checks Google's additional requirements beyond schema.org spec.

Common use cases

  • Verify a new schema implementation actually parses correctly after deploying changes.

  • Audit a competitor's structured data to identify what rich results they're targeting.

  • Debug missing rich results — confirm the schema is present and syntactically valid before suspecting Google.

  • Confirm Yoast/Rank Math is emitting the schema types you expect.

  • Validate JSON-LD on staging before deploying to production.

  • Check for accidentally-duplicate schema blocks (a common source of 'multiple Article' warnings in Search Console).

Frequently asked questions

Does valid schema guarantee rich results?▼
No. Schema validity is a prerequisite, not a sufficient condition. Google's rich result eligibility depends on additional factors: content quality, the specific schema type's requirements, and Google's discretion. A page can have perfectly valid schema and still not display rich results because Google decided not to — usually because the page's overall quality signals aren't strong enough.
What schema types should every site have?▼
Sitewide: Organization (or Person for individual brands) — establishes identity for the knowledge graph. WebSite — with SiteSearchAction for the sitelinks search box. BreadcrumbList — on every page beyond the homepage. Per-template: Article on blog posts, Product on product pages, FAQPage where applicable, HowTo for tutorials. These cover 90% of rich-result opportunities for most sites.
JSON-LD or Microdata — which should I use?▼
JSON-LD. Google explicitly recommends it. JSON-LD is easier to maintain (a separate block, not interleaved with your HTML), easier to debug (paste into a validator), and less likely to break when you redesign the page layout. Microdata is legacy — supported but discouraged for new implementations.
Why does my schema show in this validator but not in Google's Rich Results Test?▼
Schema.org spec and Google's rich-result requirements aren't identical. Google requires specific fields for rich-result eligibility that the broader schema.org spec marks optional. Example: a Recipe schema needs name, image, and recipeIngredient to be Google-eligible, even though schema.org technically only requires name. Always run through both validators.
Can I have multiple JSON-LD blocks on one page?▼
Yes — Google parses all of them. Common pattern: one block for Article schema, another for BreadcrumbList, another for the FAQ section. Don't duplicate the same @type though (e.g., two Article blocks describing the same content). When in doubt, combine them into a single @graph array.
Does schema affect rankings directly?▼
Indirectly. Google has repeatedly said schema is not a direct ranking signal. But rich results have higher click-through rates (a behavioral signal), schema helps Google understand your content more confidently, and entities in the knowledge graph rank for branded queries. Net: schema improves rankings via downstream effects, not by raw schema-presence.
What's @graph and when should I use it?▼
@graph is a JSON-LD feature that lets you describe multiple entities (an Article AND its Person author AND the publishing Organization) in a single JSON-LD block, with @id references between them. Useful for complex pages with interrelated entities. Not required — flat blocks work fine for simpler cases.

Related tools

Meta Tags Analyzer

Extract and analyze every meta tag from any URL.

Heading Hierarchy Analyzer

Audit H1-H6 structure for SEO and accessibility issues.

Open Graph Inspector

Preview how a URL appears on Facebook, Twitter, and LinkedIn.

Sitemap Inspector

Analyze any XML sitemap — URL count, lastmod, structure.

robots.txt Inspector

Parse robots.txt and flag common mistakes.

Page Word Count

Count visible words on any URL.

Subscribe for updates

We do not sell your email. We do not spam.

© 2026 RevealTheme. All rights reserved.