Skip to content
GigAI Tools

Rich Results Preview, Validate JSON-LD & Check Rich-Result Eligibility

Paste your structured data (or the whole page) and get an instant, honest read on it: every schema.org type detected, every required and recommended property checked, and a clear verdict on which Google rich results the markup is eligible for. Runs entirely in your browser, nothing uploaded.

100% browser processingFree · no sign-up

What is the rich results preview?

Rich Results Preview parses pasted JSON-LD or a full page's HTML, detecting every schema.org @type including nested nodes, then checking required and recommended properties and mapping them to eligible Google features like FAQ accordions, price snippets and breadcrumbs. A 0–100 score summarises it. Free and browser-based, so staging markup stays private.

The GigAI Rich Results Preview reads the structured data you paste, a raw JSON-LD object, an array of blocks, or an entire page's HTML with the `<script type="application/ld+json">` tags still in it, and turns it into a prioritised eligibility report. It first parses the input safely (with precise, line-aware errors when the JSON is malformed), then walks every node to detect each schema.org `@type` present, including nested types like the Offer inside a Product or the Question nodes inside an FAQPage. Each detected type is graded against schema.org's required and recommended properties: missing required fields are hard errors that disqualify the markup from a rich result, while missing recommended fields are warnings that quietly cost you eligibility or a richer display. On top of the raw validation, the tool maps what it found to the concrete Google rich-result features the page could earn: an FAQ accordion, product price and star ratings, a breadcrumb trail, event dates, a recipe card, a video thumbnail, sitelinks and more, so you understand the SEO payoff, not just the syntax. A 0–100 score and letter grade summarise the whole payload at a glance, and because it parses markup you paste using the browser's own JSON engine with zero network calls, it happily audits staging pages, competitor markup you copied, or a template you haven't shipped yet. To be clear about scope: this is a fast, pragmatic client-side linter and eligibility guide, not Google's live Rich Results Test: always confirm final eligibility on Google's own checker before you rely on it.

Difficulty:
Easy
Typical time:
~30s
Processing:
100% browser processing

Last updated

How to use the rich results preview

  1. 1

    Grab your structured data

    Copy the `<script type="application/ld+json">` block from your page's source, or the raw JSON-LD from your CMS or generator. You can also copy the entire page HTML: the tool will find the scripts inside it.

  2. 2

    Paste it in

    Paste (or drop a .json/.html file) into the analyzer. It parses safely and, if the JSON is malformed, tells you exactly what's wrong so you can fix it.

  3. 3

    Read the eligibility report

    See every detected type, its required/recommended check, and the Google rich-result features it qualifies for. Errors block a rich result. Warnings are improvements worth making.

  4. 4

    Fix, re-paste, and confirm

    Address the flagged errors, paste the updated markup back in to re-check, then confirm final eligibility with Google's official Rich Results Test before publishing.

What Rich Results Preview includes

  • Detects every schema type

    Paste one object, an array, or full HTML: the analyzer finds every schema.org @type present, including nested nodes like the Offer inside a Product or the Questions inside an FAQPage.

  • Required vs. recommended check

    Each type is graded against schema.org's required and recommended properties. Missing required fields are errors that block a rich result. Missing recommended ones are warnings that cost eligibility.

  • Rich-result eligibility mapping

    See the concrete Google features your markup could earn, FAQ accordion, price and star ratings, breadcrumbs, event dates, recipe cards, video thumbnails. Not just a raw pass/fail.

  • Precise JSON error reporting

    Malformed JSON-LD returns a clear, specific parse error instead of a silent blank, so you can fix a stray comma or unquoted key in seconds.

  • Works on HTML or raw JSON-LD

    Drop in a whole page's source and it pulls out every application/ld+json script for you, or paste a bare JSON object. Both are validated the same way.

  • 100% in your browser

    Parsing and validation use the browser's native JSON engine and DOMParser on your device. Your markup (including private prices or unpublished pages) is never uploaded, stored or logged.

Why use our rich results preview

Catch disqualifying errors before Google does

A single missing required property silently drops a page from a rich result. This tool surfaces those errors the moment you paste, so you fix them in the editor instead of discovering the loss weeks later in Search Console.

Understand the SEO payoff, not just the syntax

Instead of a bare 'valid' stamp, you see which rich-result features the markup unlocks (an FAQ accordion, star ratings, breadcrumbs) so you can prioritise the schema that actually moves click-through.

Audit anything, including private pages

Because it works on markup you paste with no network calls, you can validate staging environments, login-gated pages, competitor markup you copied, or a template you haven't shipped, none of which a live URL tester can reach.

Safe for confidential structured data

Everything runs locally, so structured data containing unpublished prices, internal event details or personal author information is checked without any of it leaving your machine.

Built for the way you work

From quick one-off fixes to daily workflows, see how people put this tool to use.

  • SEO specialist

    Validate structured data across templates

    Paste the JSON-LD your CMS emits for each page template to confirm required properties are present and no type has silently broken after a theme update.

  • Developer

    Debug a rich result that isn't showing

    When a page's FAQ or product snippet vanishes from Search, paste the live markup to see instantly whether a missing required property or malformed JSON is the cause.

  • E-commerce manager

    Check product markup before a launch

    Validate Product schema (price, currency, availability and aggregate rating) on a staging page so price and review rich results are eligible the day it goes live.

  • Content / competitive analyst

    Inspect a competitor's structured data

    Copy a rival page's ld+json scripts and paste them here to see exactly which rich-result features they've marked up for. No live URL access needed.

Supported formats

Accepts JSON-LD and HTML, and produces Report, all processed locally in your browser.

Input formats
  • JSON-LD
  • HTML
Output formats
  • Report

Frequently asked questions

Common problems, solved

Hit a snag? Here are quick fixes for the issues people run into most.

  • It says the JSON is invalid but the page works fine.

    You probably pasted a fragment with a trailing comma, an unquoted key, or the surrounding `<script>` tag without its content. Paste the full JSON object (or the whole HTML page and let the tool extract the script), and read the parse error. It points at the exact problem.

  • A required-property error appears for a field I did set.

    The property is likely on the wrong node: e.g. `price`/`priceCurrency` belong on the Offer, not directly on the Product, and `startDate` on the Event, not its location. Move it to the node the error path names and the error clears.

  • My markup passes here but Google's test flags it.

    This is a pragmatic required/recommended linter, not a full schema.org shape validator, and Google adds its own content-quality and eligibility rules on top of valid JSON-LD. Always confirm on Google's Rich Results Test before relying on a rich result.

  • Nothing is detected even though I pasted HTML.

    The page has no `<script type="application/ld+json">` blocks, or its structured data is in Microdata/RDFa rather than JSON-LD. This tool checks JSON-LD. Convert Microdata to JSON-LD (Google's recommended format) and paste that.

Get the most out of it

  • Paste the whole page HTML when in doubt, the tool extracts every ld+json script, so you don't have to hunt for them one at a time.

  • Fix required-property errors first: they're the only issues that outright disqualify a page from a rich result. Warnings are polish.

  • Multiple schema blocks on one page are normal and fine: an Article, a BreadcrumbList and an Organization can all coexist, and each is checked independently.

  • Only mark up content that's actually visible on the page. Valid markup for hidden or mismatched content can trigger a manual action even if it passes here.

  • After fixing everything, run the same markup through Google's Rich Results Test. Passing this check is necessary, but Google has the final say on eligibility.

What's new

Recent updates and improvements to the rich results preview.

  1. Initial release. Paste JSON-LD or full HTML, automatic type detection, required/recommended validation, rich-result eligibility mapping, 0–100 score and grade, precise JSON parse errors, sample and file drop.

  2. Added automatic extraction of every application/ld+json script from pasted HTML, plus per-type eligibility descriptions for FAQ, Product, Breadcrumb, Event, Recipe and Video results.

  3. Refined the report with grouped errors, recommended warnings and detected-types summary, and a link to Google's Rich Results Test for final confirmation.

Your privacy is built in

Every byte you paste is parsed and validated locally in your browser using its native JSON engine and DOMParser: nothing is uploaded to any server. Your structured data, including private prices, unpublished event details or personal author information, is never stored, logged or transmitted. Close the tab and every trace is gone.

  • Runs in your browser
  • No uploads
  • Nothing stored

Ready to try the rich results preview?

Free, private and instant. Rich Results Preview runs right in your browser.