Rich Results Tester
Paste JSON-LD or a full HTML head and check eligibility for Google's 2026 rich-result types — with FAQPage limits and HowTo deprecation baked in.
Why a 2026-Aware Rich Results Tool Matters
Google's rich-result rules shift more often than most teams notice. Between 2023 and 2025 FAQPage rich results were narrowed to government and authoritative health sites for non-logged-in users, HowTo rich results were retired entirely, and several other types tightened their required-field checks. A schema generator from 2022 will happily emit JSON-LD that validates against Schema.org but no longer earns any rich result on the SERP — and you will only know after weeks of watching the impressions stay flat. This tester encodes the current eligibility rules, not just structural validity. Use it alongside the Schema Markup Generator for new schema or the Schema Validator for syntactic checks.
How the Eligibility Checks Work
Paste either a `<script type="application/ld+json">` block or a full page HTML — the tool extracts every JSON-LD island and runs them in turn. For each block it identifies the `@type`, looks up the current rich-result rules for that type, and runs three layers of checks. Layer one is parse validity — does the JSON parse, and is the type still in active use? Layer two is structural — are all required fields present, do they have plausible types, are arrays correctly nested? Layer three is eligibility — for types like FAQPage that have post-2023 restrictions, the tool warns even when the markup is structurally valid because the rich result no longer triggers for most sites. The output lists each block with a pass/warn/fail badge plus a short reason. Nothing is uploaded; all the rule data is bundled.
Frequently Asked Questions
Does this tool replace Google's own Rich Results Test?+
No — Google's test makes a live request and runs against their internal renderer, which can catch JavaScript-rendered issues this tool cannot. Use both: this tool for fast iteration during writing, Google's for final pre-deploy verification.
Why does FAQPage now warn even when the markup is correct?+
Since 2023 Google has restricted FAQ rich results to authoritative government and health domains for non-logged-in searchers. Your FAQPage markup may be perfectly valid yet earn no visible rich result. The warning surfaces that expectation gap so you do not assume the markup is failing for structural reasons.
What happens to my HowTo schema?+
HowTo rich results were retired in 2023. The markup itself is not harmful, but it earns no rich result and the tool flags it as deprecated so you can decide whether to keep, convert to a different type, or remove.
Can I test multiple JSON-LD blocks at once?+
Yes — paste full page HTML and the extractor finds every JSON-LD island. Each block is checked independently and reported separately, so you can see which page-level schemas pass and which warn.
Does the tester check Open Graph or Twitter Card tags?+
No — those are not JSON-LD and a different tool covers them. Use the Social Card Debugger for OG and Twitter validation.
How current is the rules data?+
Rules reflect Google Search Central guidance current to the page footer date. Rich-result rules change a few times a year; if Google announces a new restriction or eligibility change, the rules are updated and the tool re-deployed.
Is anything I paste sent to a server?+
Nothing. The entire validator runs in your browser — parsing, type lookup, eligibility checks — and the page never makes an outbound request with your content.
When a block shows 'eligible — but verify with Google', what is the caveat?+
Some types pass every encodable rule but still get rejected at indexing time for reasons not visible to a static checker, like spam signals or low domain trust. The wording acknowledges that passing eligibility is necessary, not sufficient.
Built by Derek Giordano · Part of Ultimate Design Tools
Privacy Policy · Terms of Service