Structured Data Validator

Paste JSON-LD or enter a URL to check syntax, @context and @type, Google rich result required fields, URLs and ISO 8601 dates.

The interactive tool loads here when JavaScript runs.

About this tool

What is the Structured Data Validator?

The Structured Data Validator checks JSON-LD in two ways. Paste a block into JSON-LD Code, or switch to URL Analysis and enter a page address to pull every script type="application/ld+json" block from that page. It reports errors, warnings, the schema types found and how many properties they carry.

Errors are things that break or disqualify the markup: invalid JSON, a missing @context or @type, and properties Google lists as required for a rich result (for example name, startDate and location on an Event, or name plus offers, review or aggregateRating on a Product). Warnings cover recommended properties, empty values, URLs that are not absolute, dates that are not ISO 8601, and types whose rich results Google has restricted, such as FAQPage and HowTo. Single objects, top-level arrays and @graph documents are all understood.

Pasted JSON is checked in your browser. Browsers do not let one site read another site's HTML (the same-origin policy and CORS), so the page is fetched through the public allorigins.win proxy and parsed in your browser. The URL you enter is therefore sent to that third-party service.

  • JSON syntax, @context and @type checks
  • Google rich result required and recommended fields for common types
  • Arrays, @graph and multiple blocks per page
  • URL and ISO 8601 date checks, FAQPage and HowTo notices
  • Pasted JSON is checked locally; URL mode uses a public CORS proxy
Read the guide: JSON-LD Structured Data: What Still Earns Rich Results

Updated

How to use the Structured Data Validator

  1. Choose JSON-LD Code and paste your JSON (the content of the script tag, not the tag itself), or choose URL Analysis and enter a page address.
  2. Click Validate JSON-LD or Analyze URL.
  3. Read the status line: Valid or Invalid, the schema type badge and the property count.
  4. Fix each item in Errors first, then review Warnings. In URL mode the extracted JSON is copied into the code box so you can edit and re-validate it.

Worked examples

Product without an offer

Input

{ "@context": "https://schema.org", "@type": "Product", "name": "Ceramic Mug" }

Output

Invalid. Error: Product needs at least one of: offers, review, aggregateRating

Google's product snippets need a price, a review or a rating to show anything extra. Add an Offer with price and priceCurrency.

Logo as an ImageObject

Input

"logo": { "@type": "ImageObject", "url": "https://example.com/logo.png" }

Output

No URL error

Image properties may be a URL string or an ImageObject. The validator checks the object's url instead of rejecting it.

Event date in prose

Input

"startDate": "March 5, 2026"

Output

Warning: "startDate" is not an ISO 8601 date (e.g. 2026-10-24 or 2026-10-24T09:30:00+01:00)

JavaScript can parse "March 5, 2026", but Google expects ISO 8601. Include a time and UTC offset for events.

Background and insight

A JSON-LD block has two layers that can fail separately. The first is syntax: it must be valid JSON, and the browser's JSON.parse is unforgiving about trailing commas and smart quotes pasted from a word processor. The second is vocabulary: @context should point at schema.org and every node needs an @type. Schema.org itself has no required properties, so "valid" only becomes strict when you add a consumer's rules.

Google's rules are per feature and they change. Article has no required properties, only recommended ones; LocalBusiness needs name and address; Recipe needs name and image. In August 2023 Google limited FAQ rich results to well-known government and health sites, and in September 2023 it stopped showing HowTo rich results. The Structured Data Testing Tool was retired in favour of the Rich Results Test (Google features) and the Schema Markup Validator at validator.schema.org (general schema.org).

This validator covers the common types and the mistakes that cause most failures. It does not know every schema.org type or every Google feature, and it checks top-level properties rather than walking nested objects. Use it as a fast first pass, then confirm important pages with the Rich Results Test or URL Inspection in Search Console.

Common use cases

  • Before deploying a template change

    Paste the JSON-LD a template renders and catch a missing field before it hits every page.

  • Auditing a live page

    Pull every JSON-LD block from a URL, including ones added by plugins you forgot about.

  • Debugging lost rich results

    Check whether a page relies on FAQ or HowTo markup that Google no longer rewards.

  • Reviewing generated markup

    Check output from the Schema Markup Generator or a CMS plugin.

Tips and limitations

  • Paste only the JSON, without the surrounding script tag, into the code box.
  • Smart quotes from a word processor break JSON. Use straight double quotes.
  • Prefer absolute https URLs for url, image, logo and sameAs.
  • Give event startDate a time and UTC offset, such as 2026-11-05T19:00:00-05:00, so it is not read in the wrong time zone.
  • A clean result here does not guarantee a rich result. Google also weighs content quality, policy compliance and whether the feature is offered for your site type.

Sources and further reading

  1. RFC 8259: The JavaScript Object Notation (JSON) Data Interchange Format, IETF. The JSON syntax a JSON-LD block must follow
  2. JSON-LD 1.1, W3C. Defines @context, @type and the rest of the format
  3. Structured data markup that Google Search supports, Google Search Central. Each feature's required and recommended properties
  4. Changes to HowTo and FAQ rich results, Google Search Central Blog
  5. An update on the Structured Data Testing Tool, Google Search Central Blog. The move to the Rich Results Test and validator.schema.org

Frequently asked questions

How do I test structured data without Google's tools?

Paste the JSON-LD into this validator to check syntax, @context, @type and the fields Google requires for common rich results. For a final check use Google's Rich Results Test, which reports exactly which Google features a page is eligible for, or the Schema Markup Validator at validator.schema.org for general schema.org.

What happened to Google's Structured Data Testing Tool?

Google retired it. Google-specific checks moved to the Rich Results Test, and the general schema.org checker moved to the Schema Markup Validator at validator.schema.org, run by schema.org. Search Console's URL Inspection and rich result reports show what Google found on live pages.

Why does my FAQPage markup show a warning?

Since August 2023 Google shows FAQ rich results only for well-known, authoritative government and health websites. The markup is still valid schema.org and does no harm, but on most sites it will not produce the expandable questions in search results any more.

Is JSON-LD with @graph valid?

Yes. @graph lets one script block hold several linked nodes, such as WebSite, Organization and BreadcrumbList, sharing one @context. Google reads it, and so does this validator: each node in the graph is checked for @type and its type's required fields.

Which properties are required for Article structured data?

None. Google's Article documentation lists only recommended properties: headline, author, datePublished, dateModified and image. Missing ones appear here as warnings rather than errors. Adding author as a Person with a name and url, and a 1200-pixel-wide image, gives Google the most to work with.

Why does the validator complain about a relative image URL?

Search engines resolve relative URLs against the page, but the result depends on where the markup ends up, and other consumers may not resolve them at all. Absolute https URLs remove that ambiguity, so the validator warns about any url, image, logo or sameAs value that is not one.

Is there an in-depth guide to the Structured Data Validator?

Yes. “JSON-LD Structured Data: What Still Earns Rich Results” covers the background, how it works, common pitfalls and worked examples. Read the full guide.