Rich Snippet Validator Calculator

Example data table

Formula used

This validator uses a weighted completeness score to summarize your structured data health.

• Coverage% = (Total required fields found ÷ Total required fields expected) × 100
• Score = clamp( Coverage% + bonuses − penalties, 0, 100 )
• Bonuses reward detected JSON-LD and additional markup formats.
• Penalties increase with parse errors, missing required fields, and strict scoring.

How to use this calculator

1. Paste your page HTML or JSON-LD into the input box.
2. Optionally provide a URL and enable “Fetch URL”.
3. Select an expected schema type if you want a mismatch warning.
4. Click Validate rich snippets to see score, items, and issues.
5. Use CSV/PDF exports to share reports with your team.

Structured data signals and detection

This validator scans pasted markup or fetched HTML for JSON-LD scripts, plus optional microdata and RDFa indicators. In routine audits, teams often find JSON-LD on 60–90% of key templates, while microdata appears on legacy product and breadcrumb components. The tool summarizes these signals so you can prioritize where markup is missing, duplicated, or split across formats.

Coverage scoring for common rich results

For each detected item, required fields are checked against practical rule sets. Example: Article expects headline, image, datePublished, and author; Product expects name, image, and offers. Coverage% is calculated as found ÷ expected. If a page has 12 expected fields across items and 9 are present, coverage is 75%.

Penalty model and strict mode behavior

The final score adds small bonuses for JSON-LD presence and subtracts penalties for parse errors and missing fields. Each JSON-LD parse error increases risk because crawlers may ignore the block entirely. Strict mode amplifies warning penalties to reflect high-stakes templates, such as ecommerce, where priceCurrency or availability mistakes can break eligibility.

Interpreting item-level results

Use the item table to isolate which schema objects need work. A warning status usually means fields are incomplete, not invalid. An error status typically indicates missing @type, missing mainEntity on FAQPage, or absent itemListElement on BreadcrumbList. Fixing one root object often improves multiple URLs in a template-based site.

Exporting reports for workflow alignment

CSV export is useful for merging with QA tickets and sprint backlogs. Include score, verdict, detected types, and top issues in a single row per URL during large crawls. PDF export works well for client handoffs, showing a concise summary plus the first 20 issues for fast stakeholder review.

Practical optimization targets

Start with pages that already rank on page one but lack enhancements. Improve Product offers by ensuring numeric price, ISO 4217 currency, and consistent URLs. For Articles, ensure a representative image and accurate publication dates. Revalidate after changes, and track score trends weekly to measure structured data hygiene across releases. Benchmark scores by template, then improve the weakest.

FAQs

1) Is this an official rich result test?

No. It is a heuristic pre-check that validates structure, required fields, and common mistakes. Use it to catch issues early before running official tools and requesting recrawls.

2) Why do I see warnings when my JSON-LD is valid?

Warnings usually mean completeness gaps for rich results, not invalid JSON. A page can be valid but still miss fields that improve eligibility and display quality.

3) What should I paste for best results?

Paste the full HTML source of the page or the exact JSON-LD block you deploy. Full HTML helps detect canonical links and other markup signals.

4) How is the score calculated?

Coverage is found required fields divided by expected fields, multiplied by 100. The score then applies small bonuses for detected markup and penalties for errors and strict warnings.

5) Can I validate microdata and RDFa?

Yes. Enable the detection options to flag whether those patterns exist in the input. The detailed checks focus on JSON-LD items, but mixed formats are still summarized.

6) Why is URL fetching failing on my server?

It may be blocked by firewalls, robots rules, SSL issues, or missing cURL support. Turn off fetching and paste HTML directly to validate without network requests.