Schema Markup Validator

Last updated:

Inventory JSON-LD and Microdata on any public page, catch parse errors, and review common property gaps. This is a fast diagnostic; confirm final Schema.org validity and Google eligibility with the official validators.

Check a live URL or paste JSON-LD directly:

How the Schema Markup Validator Works

This tool fetches a webpage and extracts all structured data embedded in it. Here's the process:

  1. Choose an input, fetch a public URL or paste JSON-LD for browser-only parsing without a server request.
  2. JSON-LD extraction, it finds all <script type="application/ld+json"> blocks, parses the JSON, and handles @graph arrays.
  3. Type detection, the tool lists the @type values it can parse, including types inside @graph.
  4. Common property checks, built-in rules flag selected gaps on frequently used types. These checks are not a complete implementation of the Schema.org vocabulary or every Google search feature.
  5. Microdata scan, the tool also detects schema.org Microdata markup embedded in HTML attributes.

Why Schema Markup Matters for SEO and GEO

Structured data can make visible facts easier to interpret consistently. It is one layer of a broader search and entity strategy:

  • Search-feature eligibility, supported types with valid properties can make a page eligible for breadcrumbs, products, events, articles, and other enhanced results. Display is never guaranteed.
  • Entity clarity, stable identifiers and consistent Organization, Person, Product, or LocalBusiness facts can reduce ambiguity when they match the page and external profiles.
  • Maintenance, structured fields make stale prices, ratings, authors, and dates easier to audit systematically.
  • AI-search foundation, machine-readable facts may help systems interpret a source, but markup alone does not establish expertise or earn citations. Measure real prompts and cited URLs separately.

Schema works alongside your SEO and Open Graph tags ; together, they provide explicit metadata for different consumers. Need to generate a starting point? Use the Schema Markup Generator, then adapt it to the visible page and validate it. For a broader technical audit, the AI Search Readiness Checker reviews schema alongside crawler controls, headings, and standard discovery signals.

Want to go deeper? Our blog covers the full structured data topic: what schema markup is and why it matters for SEO explains the fundamentals and which types your site needs. How schema helps your business earn AI citations covers the growing role of structured data in ChatGPT, Perplexity, and Google AI Overviews. And our guide to testing and validating schema markup walks through the complete validation workflow from pre-publish checks to quarterly audits.

Google Retired the Structured Data Testing Tool. Here's What to Use Now.

For years, the Structured Data Testing Tool was the way to check schema markup: paste a URL, see every type on the page, fix what's flagged. Google announced its deprecation in 2020, and in 2021 handed it over to Schema.org, where it survives as validator.schema.org without the Google-specific checks site owners relied on.

The replacements each cover only part of what the original did:

Validator What it checks The catch
Google Rich Results Test Schema types eligible for Google rich results Covers only ~30 types. Valid Organization, Service, or WebSite schema shows as "no items detected".
validator.schema.org Syntax and vocabulary of all Schema.org types General vocabulary validation; use Google documentation for Google-specific search-feature requirements.
Search Console Rich result reports for your own verified site Only works on sites you own, and only after Google has crawled them.
This tool Live-page JSON-LD inventory, parse errors, Microdata types, and selected common-property checks Fast diagnostic only; not authoritative for the full Schema.org vocabulary or Google eligibility.

In short: use the Rich Results Test to confirm a specific rich result, and use a general schema checker like this one for a quick live-page inventory. No validator can predict an AI citation. For the complete validation workflow, read our guide to testing schema markup.

Common Schema Types, Chosen by Page

There is no universal checklist. Choose the narrowest types that accurately describe the visible page:

  • Organization, your business name, logo, URL, social profiles. The foundation of your online identity in search.
  • WebSite, site name, URL, and publisher identity.
  • BreadcrumbList, a real navigation path (Home → Category → Page) that can support breadcrumb display.
  • Article / BlogPosting, for editorial content with visible author and accurate publication dates.
  • FAQPage, only for visible FAQ content that complies with current search policies. Google limits FAQ rich results mainly to authoritative government and health sites.
  • WebApplication, for tool pages (like this one). Describes the app, its category, pricing, and provider.
  • Product, for product pages. Requires name, image, and offers for rich results with pricing.
  • Service, for service pages. Describes what you offer, the provider, and the service area.

Schema Type Reference: Properties to Review

Different consumers and search features have different requirements. Use this as a starting reference, then confirm the current requirements for the specific feature in Google's documentation and validate the general vocabulary at Schema.org.

Schema type Use it on Common properties to review
Organization Site identity, commonly anchored from the home page @id, name, url, logo, and accurate sameAs profiles.
LocalBusiness Local business or store pages name, real address, telephone, openingHours, and geo when those facts are visible and accurate.
Article / BlogPosting Blog posts and news articles headline, image, datePublished, author. Add dateModified and publisher for full eligibility.
Product + Offer Product and e-commerce pages name, image, plus offers with price and priceCurrency. Add aggregateRating or review for star ratings.
FAQPage Pages with a real FAQ section mainEntity as a list of Question items, each with a name and an acceptedAnswer (Answer with text).
BreadcrumbList Any page with a navigation path itemListElement as ordered ListItem entries, each with position, name, and item (the URL).
WebSite Home page (site-wide identity) @id, name, url, and a consistent publisher reference.

Requirements can change. Valid markup can make eligible content understandable; it does not guarantee a rich result, ranking, Knowledge Graph panel, voice answer, or AI citation.

Next steps

Schema Markup Validator related tools and articles

Continue with the closest follow-up checks and guides based on this tool's topic, crawl intent, and optimization workflow.

Schema Markup Validator: FAQ

What do JSON-LD blocks, schema items, and total types mean?
JSON-LD blocks counts script elements that parsed successfully. Schema items counts top-level typed nodes found directly, in a top-level array, or inside @graph. Total types adds those items to detected Microdata type declarations, so it is an inventory count rather than a quality score.
What do the issue messages validate?
The tool applies a small set of built-in checks to Organization, LocalBusiness, WebSite, article types, FAQPage, BreadcrumbList, software applications, and Product. It checks selected common properties only. No issue means those checks passed, not that the full Schema.org vocabulary or a rich-result policy passed.
How should I fix a JSON-LD parse error?
The report identifies the script block number and the browser JSON parser message. Look for trailing commas, comments, unescaped quotes, invalid control characters, or markup mixed into the JSON. Fix the source block, publish it, and scan the live page again.
How are @graph, nested objects, and Microdata handled?
Top-level @graph nodes are listed separately, while nested authors, offers, and other objects remain properties of their owning item. Microdata detection lists itemtype names only and does not validate itemprop values. RDFa is not inspected.
Why can the result say no schema when I can see markup elsewhere?
The checker reads the fetched HTML response, up to 2 MB. Schema inserted only after client-side JavaScript runs may be absent from that response. Consent gates, authentication, bot protection, timeouts, or more than five redirects can also prevent the expected markup from being read.
Which validation tool should I use next?
Use this report to locate blocks and obvious gaps. Then use Schema.org Validator for general vocabulary conformance and Google's Rich Results Test for a Google-supported feature. Also compare every value with the visible page and check Search Console reports for your verified property.
What are the fetch and display limitations?
The request has a 12-second timeout, follows at most five redirects, and reads at most 2,000,000 bytes. Long property values are shortened for display. The checker does not execute JavaScript or determine whether Google will show a rich result.
Are the checked URL and page markup stored?
The public URL is sent to the Web Aloha server so it can fetch and parse the HTML. This endpoint has no result cache or database write and does not persist the URL, HTML, or extracted schema after returning the report.

Free 48-Hour Website Audit

Not sure what to fix first on your own website? We'll review it and tell you, in plain English. Free & non-obligatory.

Need Help With Your Structured Data?

We implement accurate structured data that matches visible content and test it through the appropriate official validation workflow.