Microdata Schema Analysis Test
The Schema Markup Test detects every block of structured data on any URL — JSON-LD, Microdata and RDFa — validates each against the Schema.org vocabulary, and reports which rich-result types the page is eligible for in…
- Results in seconds
- Pass / fail + fix guidance
- No account required
The Schema Markup Test detects every block of structured data on any URL — JSON-LD, Microdata and RDFa — validates each against the Schema.org vocabulary, and reports which rich-result types the page is eligible for in Google search. Structured data is how you tell Google exactly what your page is about (Article, Product, FAQ, HowTo, LocalBusiness, Event, Recipe, Review) and is the prerequisite for rich snippets, FAQ accordions, breadcrumbs, sitelinks and the most prominent SERP placements.
What This Tool Checks
- JSON-LD blocks in <head> or <body>
- Microdata via itemtype / itemprop attributes
- RDFa via vocab / typeof / property attributes
- Schema.org type detection (Article, Product, FAQ, HowTo, etc.)
- Required vs recommended properties per type
- Validation against Google's rich-results requirements
- Conflicting or duplicate schema blocks
Why It Matters for SEO
Structured data is the single biggest unlock for rich SERP appearance — FAQ accordions, How-To stepped results, Product price-and-rating cards, Recipe tiles, Event listings, breadcrumb trails. These rich results take up significantly more SERP real estate than plain blue links, can double or triple click-through rate, and are increasingly the only way to compete on commercial keywords. Even where rich results are not granted, structured data helps Google understand your content topology and is a strong topical-relevance signal.
How to Fix It
Add JSON-LD blocks in <head> for every page type: Article on blog posts, Product on product pages, FAQ on FAQ sections, HowTo on tutorials, BreadcrumbList sitewide, Organization on the homepage. Use Google's Rich Results Test to validate eligibility, and re-test this tool to confirm proper detection.
How It Works
We parse the page HTML, extract every JSON-LD block, every itemtype / itemprop attribute, and every RDFa annotation. Each detected entity is validated against the Schema.org vocabulary and Google's rich-results documentation, then reported with eligible rich-result types.
Common Mistakes to Avoid
- No structured data at all (missing every rich-result opportunity)
- JSON-LD with required properties missing (silently disqualified)
- Multiple competing schemas on the same page (Product + Article confuses Google)
- Schema declared for content not actually visible on the page (manual action risk)
- Using deprecated schema types or properties
Quick Checklist
- Every page has an appropriate JSON-LD type
- Sitewide BreadcrumbList and Organization schemas
- Required properties present per type
- Visible content matches schema content
- Google Rich Results Test passes
Put your whole site on autopilot — SEO and AI search
PositionMySite monitors every signal on this page across your entire website 24/7 — plus keyword rankings, competitor moves and AI-search readiness (llms.txt, schema, ChatGPT & Gemini visibility). When something breaks, you know before Google does.
Every feature unlocked · No commitment · Cancel anytimeFrequently Asked Questions
JSON-LD. Google explicitly recommends it because it lives in <head> as a separate <script> block, does not entangle with markup, and is easier to maintain. Microdata and RDFa are still valid but more error-prone.
No. Schema makes the page eligible — Google decides per query whether to display the rich result. Higher quality, more authoritative pages with valid schema are more likely to win the rich treatment.
Yes when they describe different aspects of the same content (Article + BreadcrumbList + Organization). Avoid putting unrelated competing types (Product on a blog post) on the same URL.
Indirectly but powerfully. It feeds Google's topical understanding of the page and is the gateway to rich results, which lift CTR — and CTR is increasingly weighted.
Use Google's Rich Results Test (search.google.com/test/rich-results) and the Schema.org validator (validator.schema.org). Both report errors plus eligibility for specific rich-result types.