Skip to main content

Schema Validator

Validate JSON-LD from code or a live URL.

How to use the Schema Validator, step by step

Real screenshots of the current tool, using sample inputs. Long results are shown as a preview.

  1. 1

    Add your input

    Paste or type into the field Schema Validator works from.

    Schema Validator in its default state before the walkthrough
  2. 2

    Sample text in place

    With sample text entered, Schema Validator is ready to run.

    Schema Validator with sample input or settings in place
  3. 3

    Review the result

    Select Validate schema to run the tool. This screenshot shows the result returned for the sample input.

    Schema Validator showing its actual result with sample inputs
10,000+
Schemas validated
30+
Schema types
~10s
Average validation
4.8★
Trustpilot

How it works

Validate any schema in under 10 seconds.

STEP 1

Paste code or URL

Paste JSON-LD directly, or drop a URL to auto-extract every script tag from a live page.

STEP 2

Deep validation

Grigora detects every @type (including @graph), runs required + recommended field checks, and grades AI search readiness.

STEP 3

Fix with one click

Every error card shows why it matters and the exact line to change. Copy-paste and re-validate.

30+ schema types

Every schema type, with copy-paste examples

Click any type to see required fields, recommended fields, and a ready-to-paste JSON-LD example.

Most common errors

Common schema errors & how to fix them

Based on thousands of validations run through Grigora.

Missing @context

Cause: The JSON-LD block has no "@context" or uses "http://" instead of "https://".

Fix: Add "@context": "https://schema.org" as the first property.

Missing @type

Cause: "@type" is omitted or mis-capitalized (e.g. "type" or "@Type").

Fix: Use the exact case: "@type": "Article".

headline too long

Cause: Article headlines over 110 characters are rejected for Top Stories.

Fix: Trim to under 110 characters or move the long summary to description.

Missing offers (Product)

Cause: Product schema without a price won't show rich results.

Fix: Add offers with price, priceCurrency, and availability.

Invalid date format

Cause: datePublished uses "20 April 2026" or "4/20/2026".

Fix: Use ISO 8601. "2026-04-20" or "2026-04-20T09:00:00+05:30".

image is not a URL

Cause: You passed a relative path like "/hero.jpg".

Fix: Use the full absolute URL: "https://example.com/hero.jpg".

Duplicate @id

Cause: Two nested entities in a @graph share the same @id.

Fix: Give each @graph node a unique @id fragment (e.g. #org, #website).

aggregateRating without reviewCount

Cause: Ratings with no review count are ignored by Google.

Fix: Include reviewCount (or ratingCount) with a positive integer.

FAQPage with one question

Cause: Single-question FAQPage entities look spammy and get dropped.

Fix: Add at least three real, non-duplicate questions inside mainEntity.

Event in the past

Cause: Events with startDate in the past are ignored.

Fix: Update startDate to a future date or remove the Event schema.

Invalid JSON syntax

Cause: A stray comma, unclosed bracket, or smart quote breaks the entire block.

Fix: Run the full JSON through the validator, it points to the exact line.

LocalBusiness missing address

Cause: LocalBusiness needs a full PostalAddress, not just a city string.

Fix: Use a nested PostalAddress with streetAddress + addressLocality + addressCountry.

Grigora vs. other schema validators

Honest side-by-side against Google Rich Results Test and Schema.org Validator.

FeatureGrigoraGoogle Rich ResultsSchema.org Validator
Free forever
Validate from URL
Visual field tree
Required + recommended field checkPartial
"Why it matters" + "How to fix"
AI Search / GEO readiness
No rate limits
30+ schema typesPartial
GEO · AEO · AI Overviews

Schema is how you get quoted by ChatGPT

After the March 2026 Google Core Update, structured data became a direct signal for AI Overviews, ChatGPT, and Perplexity citations. Pages with complete schema saw a +22% visibility gain. Grigora scores the exact fields AI engines look for.

ChatGPT
Article + HowTo + FAQPage
AI Overviews
Organization + Author
Perplexity
Structured data + freshness
Claude Search
Publisher + author trust
From the team behind this tool

Build your whole website with Grigora

Grigora is an AI website builder that generates SEO-ready sites with clean schema markup baked in, no plugins, no broken JSON-LD. Start on Starter at $15/mo, or pick Pro at $25/mo.

Starter
$15/mo
  • 1 website, unlimited pages
  • 30k AI credits
  • Clean schema markup
  • 20% off annual

Frequently asked questions

Everything you need to know about the tool.

Yes. Unlimited validations, no signup, no rate limits. Everything on this page is free forever.

Google's tool returns pass/fail for a handful of schema types and tells you nothing about why an error matters.

30+ types including Article, Product, FAQPage, Recipe, Event, LocalBusiness, VideoObject, HowTo, BreadcrumbList, JobPosting, Course, Review, Organization, WebSite, SoftwareApplication, Service, and more.

More than ever. After the March 2026 Google Core Update, structured data became a direct signal for AI Overviews, ChatGPT, and Perplexity citations.

Yes. Switch to the "From URL" tab, paste any public URL, and the tool extracts and validates every JSON-LD script tag it finds on the page.

Yes. @graph arrays with multiple @types are parsed and each node is validated individually with its own field tree and error cards.

Proper schema is one of the strongest signals AI Overviews uses to decide what to quote. Grigora flags the exact fields AI engines look for, author, datePublished, publisher, and explicit offers.

No. The validator runs stateless, nothing is logged, stored, or shared. You can use it on staging and pre-release URLs safely.

Usually one of three reasons: (1) Google only supports a subset of schema types for rich results; (2) your page blocks Googlebot from rendering client-side JS that injects the schema; (3) the schema references an image URL Google cannot reach.

Yes, the validator runs on the final rendered HTML, so it works with every platform. For React and Next.js, make sure you render JSON-LD server-side (with next-seo or next/head) so crawlers can see it.

Yes. Grigora detects every schema block and validates them in a single run, each gets its own detected-types panel, tree view, and error cards.

All three are Schema.org formats. JSON-LD is Google's recommended format, it lives in a single script tag, is easy to maintain, and has no effect on your HTML.

G
Maintained by the Grigora team
Last updated November 2026 · Aligned with Google Search Central guidelines

Pre-order Grigora Pro, lifetime 50% off. Auto-monitor, bulk validate, AI fix suggestions.