Auditors · 100% free

Schema Markup & Rich Results Checker

Paste a page URL or HTML and validate every JSON-LD schema block against Google's Rich Results requirements.

Google Schema.org Any

Paste page HTML or raw JSON-LD

About this tool

Finds every JSON-LD block on a page (Product, Review, FAQPage, HowTo, Article, Recipe, Event, LocalBusiness, BreadcrumbList, VideoObject, JobPosting and more), parses each one, and flags missing required properties, recommended fields and common mistakes that suppress Rich Results in Google search.

What it checks

Validates JSON-LD against the property requirements Google uses for Rich Results — not a full schema.org conformance test. Covers Product, Review, AggregateRating, FAQPage, HowTo, Article / BlogPosting / NewsArticle, Recipe, Event, LocalBusiness, Organization, BreadcrumbList, VideoObject, JobPosting, Course, SoftwareApplication and WebSite. Errors mean Google will likely suppress the rich result; warnings are recommended fields that improve SERP appearance; info are minor nits.

Two ways to use it

Paste mode (most reliable) — open the page you want to check, View Source, copy and paste here. Works for any site, including authenticated pages and staging environments.
Fetch URL mode — paste a public URL and the tool tries three public CORS proxies (AllOrigins, corsproxy.io, Codetabs) to fetch the HTML. Many sites block proxies or rate-limit; fall back to paste mode if it fails.

When to cross-check with Google

For production deploys, always run a second pass through Google's official Rich Results Test — it renders JavaScript, evaluates the live page exactly as Googlebot sees it, and previews the actual SERP card. This tool catches misconfigured properties quickly during build/edit, Google's test confirms the production result.

Frequently asked questions

What is JSON-LD schema markup? +

JSON-LD (JSON for Linking Data) is the format Google recommends for adding schema.org structured data to a page. It lives inside a <script type="application/ld+json"> tag in your HTML head and describes what the page is about (Product, Article, Review, Event, etc.) in a machine-readable way. Google uses it to decide whether your page is eligible for Rich Results in the SERP.

How is this different from Google's Rich Results Test? +

Google's Rich Results Test renders the page with a headless Chromium, evaluates JavaScript-injected schema, and previews the actual SERP card, it's the source of truth for production sites. This tool is faster for build/edit cycles: paste the JSON-LD you just wrote, see exactly which required and recommended properties are missing, fix, repeat. Always cross-check production deploys with Google's tool.

Which schema types does this check? +

Product, Review, AggregateRating, FAQPage, HowTo, Article / BlogPosting / NewsArticle, Recipe, Event, LocalBusiness / Restaurant / Store, Organization, BreadcrumbList, VideoObject, JobPosting, Course, SoftwareApplication and WebSite, the 20+ types that actually drive Google Rich Results. Other types parse and are surfaced but don't get type-specific rules (basic schema.org will validate but no SERP enhancement).

Why does URL fetching fail on some sites? +

Browser security (CORS) blocks JavaScript from fetching arbitrary cross-origin pages. This tool routes URL requests through public CORS proxies (AllOrigins, corsproxy.io, Codetabs) as a best-effort workaround. Many sites, especially WAF-protected ones, ones using Cloudflare bot-fight mode, or proxies that are rate-limited, will return errors. In that case open the page yourself, View Source, and paste the HTML into the other tab.

Does it check Microdata or RDFa? +

No, JSON-LD only. Google has consistently said JSON-LD is the preferred format and the vast majority of modern sites use it. If your page only has Microdata or RDFa, this tool will report "No JSON-LD found". Migrate to JSON-LD for both better tooling support and easier maintenance.

What's the difference between errors, warnings and info? +

Errors mean a required property is missing, Google will likely suppress the Rich Result entirely. Warnings flag recommended properties that improve SERP appearance (e.g. brand, sku, aggregateRating on Product), the result will still show but won't be as rich. Info notes are minor nits (missing @context, type with no Google rules). Fix all errors first.

Is the data I paste sent to a server? +

Only in URL-fetch mode, where the URL gets sent to a third-party CORS proxy to fetch the page. In paste mode, everything is processed entirely client-side in your browser, the HTML or JSON never leaves your device. We don't operate a server-side fetch endpoint or log any requests.