Free Schema Markup Checker

Test & Validate Your Structured Data

Enter any page URL and instantly see every JSON-LD schema object it contains — the types, their properties, and any invalid or thin markup that could be costing you rich results. No signup required.

<script type="application/ld+json">
{
"@context": "schema.org",
"@type": "Product",
"name": "Blue Sneakers"
}
</script>
✓ 1 valid object · Product
We only read the page's public HTML — nothing is stored. Try a sample URL 3 checks left today
Fetching the page and scanning for structured data…
This usually takes a few seconds.

What Are Schema Objects (Structured Data)?

A schema object is a small block of machine-readable data you add to a web page that spells out exactly what the page is about — that this is a Product priced at $49, that this is an Article written by Jane Doe on the 3rd of March, or that this is a LocalBusiness open until 6pm. Search engines read these objects to understand your content far more precisely than they could from the visible text alone, and they use them to build rich results — the star ratings, FAQ drop-downs, breadcrumbs, and price snippets you see in Google.

These objects follow the shared vocabulary at Schema.org and are most commonly written in JSON-LD — a tidy block of JSON wrapped in a <script type="application/ld+json"> tag in your page's HTML. Two older formats, Microdata and RDFa, embed the same information directly into your HTML attributes. Google recommends JSON-LD, and this checker reads all three.

How the Schema Markup Checker Works — Step by Step

1. Paste a URL

Drop in any public page URL — a homepage, product page, blog post, or landing page you want to inspect.

2. We Fetch the HTML

Our server safely requests the page and reads only its public HTML source — the same thing a search crawler sees.

3. JSON-LD Extracted

Every <script type="application/ld+json"> block is pulled out and parsed, including nested @graph structures.

4. Objects Identified

Each schema object is listed with its @type, a plain-English explanation, and the properties it declares.

5. Problems Flagged

Broken JSON, missing @context or @type, empty values, and absent recommended properties are all highlighted.

6. Microdata & RDFa Too

We also detect Microdata (itemscope/itemtype) and RDFa so you get a complete picture of every markup format on the page.

Why Structured Data Matters for SEO

Unlocks Rich Results

Star ratings, FAQ accordions, recipe cards, event dates, and price snippets all come from valid schema. They make your listing bigger and far more clickable.

Higher Click-Through

A result with review stars or an FAQ drop-down takes up more space and earns more clicks than a plain blue link — often without any change in ranking position.

Clearer Meaning for AI

Structured data helps Google, Bing, and AI answer engines understand your entities and relationships, improving how your brand is represented and cited.

Catch Silent Breakage

One misplaced comma can invalidate an entire JSON-LD block and silently strip your rich results. Regular checks catch these errors before they cost you traffic.

Common Schema Types We Detect & Explain

When we find one of these types, the report tells you what it does and which recommended properties are missing. Here are the ones you'll run into most often:

Organization / LocalBusiness

Your brand or business location — powers the knowledge panel, logo, and local pack.

Article / BlogPosting

Editorial content — eligible for the Article rich result and Top Stories carousel.

Product & Offer

Items for sale — shows price, availability, and review stars right in search.

BreadcrumbList

The page navigation trail Google shows in place of the raw URL.

FAQPage & HowTo

Question lists and step-by-step guides that expand directly in the results.

Review & AggregateRating

Star ratings — one of the highest-impact rich results for click-through.

WebSite + SearchAction

Enables the Sitelinks Search Box for your brand queries.

Recipe, Event, VideoObject

Content-specific cards with times, dates, thumbnails, and ratings.

What Makes Schema Markup Invalid

  • Broken JSON syntax

    A trailing comma, an unclosed brace, or a stray quote makes the whole JSON-LD block unreadable. Search engines skip it entirely — no error, just no rich result. Our checker shows you exactly which block failed and why.

  • Missing @context or @type

    Without @context, a parser does not know you mean the Schema.org vocabulary. Without @type, it cannot tell whether the object is a Product, an Article, or something else. Both are essential.

  • Absent recommended properties

    A Product with no offers, or an Article with no headline, is technically valid JSON but will not qualify for the rich result. We flag the recommended properties Google expects for each type.

  • Empty or placeholder values

    Fields like "name": "" or leftover template values ("image": "{{IMAGE_URL}}") pass JSON parsing but fail validation. We surface empty values so they do not slip through.

  • Markup that contradicts the page

    Schema must reflect what a user actually sees. Marking up a rating that is not visible on the page, or a price that differs from the page, violates Google guidelines and risks a manual action.

Frequently Asked Questions

It is a free tool that reads a live web page and shows you the structured data it contains. You paste a URL, and it lists every JSON-LD schema object on the page along with its type, its properties, and any problems — so you can confirm your markup is present and valid without digging through source code.

It performs the core checks: it confirms your JSON-LD parses correctly, identifies each @type, checks for @context, and flags missing recommended properties and empty values. For final rich-result eligibility you should also run Google's Rich Results Test, but this tool is a much faster first pass to catch the common breakage.

All three: JSON-LD (the format Google recommends), Microdata (itemscope / itemtype attributes), and RDFa (typeof / vocab attributes). JSON-LD objects get the most detailed breakdown; Microdata and RDFa are detected and their types listed.

A few common reasons: the schema is injected by JavaScript after page load (we read the initial HTML, the same as a crawler on first pass), the markup is on a different URL than the one you entered, or the page genuinely has none. If you use a tag manager or a JS framework, check the server-rendered HTML.

Yes, it is completely free with no signup. To keep it fast and prevent abuse, checks are limited to 3 URLs per day per visitor. The counter next to the input shows how many you have left today, and it resets every day.

No. We fetch the page, analyze its HTML in memory, return the report, and keep only an anonymous count for the daily limit. The page content and your results are not saved.

A JSON validator checks whether text is syntactically valid JSON. This tool goes further — it fetches a live page, finds the JSON-LD, and validates it as Schema.org structured data: the right context, the right types, and the properties search engines expect.

Check your structured data now

Paste a URL above and see every schema object on the page in seconds — free, no signup.

Check Schema Markup