↑↓ to move · Enter to open · Esc to close

Schema Markup Validator

Validate JSON-LD in your browser, or load a public page and check the JSON-LD blocks in its HTML. URL loading may use Utilza's server when the browser cannot retrieve the page directly.

Pasted JSON-LD is checked in your browser. Load From URL may use a server fetch.
Built by · Updated

JSON-LD

Samples

Accepts a single object, an array, or multiple JSON-LD blocks. Load From URL extracts JSON-LD from the page; microdata is noted but not validated here.

Checks run instantly in your browser.

How to use the Schema Markup Validator

  1. Paste JSON-LD code, or switch to URL mode to inspect a live page.
  2. Run the validation and review items marked as errors, warnings, or info.
  3. Fix the markup on the page or in your template, then test again.

How it works

Code mode parses your JSON-LD directly in the browser and checks the item tree for syntax errors, missing context, unknown types, unsupported properties, and basic value issues such as invalid URLs or date formats.

Load From URL first requests the public page from your browser. If browser restrictions block that request, Utilza's server may retrieve the HTML. JSON-LD blocks are then extracted and validated in your browser. Microdata markers can be detected, but microdata is not validated by this checker. Read the privacy policy before loading an address, and avoid URLs containing credentials or tokens.

The validator also compares common schema types against published rich result requirements so you can spot missing fields in Article, Product, FAQPage, BreadcrumbList, Organization, Event, Recipe, VideoObject, and similar markup.

Examples

  • A Product item without an Offer can trigger a warning if price-related rich result fields are missing.
  • Nested breadcrumb item URLs are not checked. Review them separately before publishing.
  • Load a public page to inspect its JSON-LD blocks without copying each script by hand.

Limitations

  • The built-in checks cover a compact set of schema.org types and properties. They do not validate all schema.org rules or Google's full rich result eligibility requirements, and cannot predict whether Google will show a rich result.
  • URL loading reads the fetched HTML without running the page's scripts. JSON-LD added later by JavaScript may be missed.
  • Some markup can be valid schema.org but still be a poor fit for the page content. That kind of editorial mismatch is outside the validator.

Frequently asked questions

Can this validator read microdata as well as JSON-LD?

It can detect microdata markers in a fetched page, but this checker validates JSON-LD only. Paste the JSON-LD code or load a public page that includes it in the fetched HTML.

Does valid schema guarantee rich results?

No. Valid markup is only one part of eligibility. Google also considers page quality, content, and policy compliance.

Why does my live page show no schema in URL mode?

The tool checks the raw HTML response. If your schema is injected later by JavaScript, it may not appear in the fetched version.

Often used together with Schema Markup Validator.

  • JSON ValidatorDeveloper Tools

    Checks JSON syntax and explains any error in plain English.

  • JSON ViewerDeveloper Tools

    Shows JSON as a collapsible tree with search and copyable paths.

  • Website SEO Analyzer

    Checks one page for SEO basics, response details, tags, headings, links, and structured data without running JavaScript.