Rich Results Preview

Article, FAQPage, HowTo, Product, Recipe, Review, Event, LocalBusiness, Organization, BreadcrumbList, VideoObject. Sub-types like NewsArticle also detected.

Yes — paste a @graph array and each type gets its own preview card and validation report.

Required fields per type (FAQPage needs mainEntity, Product needs name+offers) and warns about missing recommended fields for rich result eligibility.

Yes, the Rich Results Preview is 100% free with no registration, no hidden fees, and no usage limits. All processing happens locally in your browser, ensuring complete privacy.

Absolutely. The Rich Results Preview processes everything client-side in your browser. No data is uploaded to or stored on any server. Your content remains private on your device at all times.

Yes, the Rich Results Preview is fully responsive and works on smartphones and tablets. You can use it on any device with a modern web browser -- no app download required.

No account or registration is needed. Simply open the Rich Results Preview in your browser and start using it immediately. There are no sign-up walls or usage restrictions.

Yes, the Rich Results Preview is built following current Google Search guidelines and best practices. We regularly update the tool to reflect changes in search engine requirements.

Simply enter your input in the provided field, adjust any settings to your preference, and the tool will process it instantly. You can then copy the result to your clipboard or download it.

The Rich Results Preview works in all modern browsers including Chrome, Firefox, Safari, Edge, and Opera. For the best experience, use the latest version of your preferred browser.

All three are syntaxes for adding the same schema.org vocabulary to a page, but they differ in where the markup lives. JSON-LD keeps structured data in a single self-contained block inside a <script type="application/ld+json"> tag, separate from your visible HTML. Microdata and RDFa instead weave attributes like itemprop and property directly into existing HTML elements, which is harder to maintain and easy to break during redesigns. Google explicitly recommends JSON-LD because it is the cleanest to add, edit, and inject dynamically without touching page layout. This previewer reads JSON-LD specifically, so paste the contents of your script block rather than the surrounding HTML. If your markup is currently in Microdata, convert it to a JSON-LD block first, then drop it here to confirm the fields parse correctly.

Valid markup only makes a page eligible for rich results; it never guarantees them. Google decides whether to display an enhancement based on page quality, content relevance, whether the markup matches visible on-page content, and its own algorithms, so a perfectly valid FAQPage or Product snippet can still appear as a plain blue link. Manual actions for spammy or hidden markup, very new or low-authority pages, and duplicate content can all suppress rich results too. This tool checks that your required and recommended fields are present and correct, which removes the technical blockers you can actually fix. Treat a clean validation report here as clearing the eligibility bar, then give Google time to recrawl and assess the page before expecting the enhanced listing to appear in search.

Required fields are the properties Google treats as mandatory for a type to qualify for rich results at all. Leave one out and the page is ineligible, which is why this tool flags a missing required field as a hard fail. For example, FAQPage requires mainEntity, Product requires name and offers, and Event requires name, startDate, and location. Recommended fields are optional properties that make the result richer and more competitive, such as image, aggregateRating, and brand on a Product, or image, publisher, and dateModified on an Article. Missing recommended fields show as warnings rather than errors because the markup still works without them, just less impressively. Paste your snippet and the validation panel labels every field pass, fail, or warn so you know exactly what to add before publishing.

A single page often needs several schema blocks at once, for example an Article plus a BreadcrumbList plus an Organization. Rather than stacking multiple script tags, you can combine them in one JSON-LD block using a @graph array: set @context once at the top, then list each typed node as an object inside a @graph property. This keeps related entities together and lets them reference one another by @id. You can also paste a plain top-level array of objects if you prefer. This previewer handles both structures, detecting every node, giving each its own preview card, and running a separate validation report per type, with a combined pass, fail, and warn tally at the top. Paste your @graph block to confirm every type is recognised and that none of them are missing a required field.

This tool mirrors the core logic of Google's Rich Results Test: it detects the schema type, checks the same required and recommended fields, and renders a Google-style card so you can spot problems instantly as you edit. The key difference is that it validates your JSON-LD snippet in isolation, entirely in your browser, without needing a live published URL, which makes it ideal for drafting and unpublished pages. Because it works from a fixed field set rather than fetching the real page, it cannot confirm that markup matches visible content or catch issues only Google sees during a live crawl. Use it as a fast, private first pass to fix obvious missing fields and syntax errors, then run the final published URL through Google's official test before relying on the rich result going live.