Schema markup checker

Enter a page and this tool extracts its JSON-LD structured data, lists the schema.org types it found, shows the code, and flags blocks with syntax errors. It also notes whether the page uses microdata or RDFa.

It’s for developers and marketers who added schema and want to confirm it’s really in the page. It checks that the markup is there and readable. To check eligibility for a rich result in Google, follow up with Google’s Rich Results Test.

Free with a ShipScroll account.

How to use the Schema Markup Checker

  1. Enter the page address and press Check schema.
  2. Confirm the types match what the page is, such as Product, Article or FAQPage.
  3. Open each item and check the values against what’s visible on the page.
  4. Run important pages through Google’s Rich Results Test.

Which format should you use?

Google recommends JSON-LD where your setup allows it. It sits in a script tag apart from your visible HTML, which makes it easier to add and maintain than microdata or RDFa. This tool shows full JSON-LD and counts the other two formats.

Valid markup doesn’t guarantee a rich result

Structured data can make a page eligible for enhanced results. It doesn’t guarantee them. A type needs all its required properties, and content that breaks Google’s guidelines can be left out. Some types have also been limited over time, so check Google’s current list for the feature you’re after.

Common mistakes

  • A trailing comma or an unescaped quote, which makes the whole block unreadable.
  • Marking up things that aren’t visible on the page, such as reviews nobody can see.
  • A template adding the same schema to every page, whether it fits or not.
  • Schema added only by client-side JavaScript, which not every crawler will run.

Example: one comma, no schema

A developer pastes a price into a Product block and leaves a trailing comma. The page looks fine and nothing errors in the browser, but the JSON can’t be parsed, so the whole block is lost. This tool reports a syntax error, which is your cue to fix that block.

Questions

How is this different from Google’s Rich Results Test?

Google’s test tells you whether a page qualifies for specific Google features. This tool is a quick way to see what’s there across any schema type and read the code. Use this to confirm it’s deployed, and Google’s test to check eligibility.

Does it check required properties?

No. It checks that JSON-LD parses and has a type, and it doesn’t validate each type’s required fields, since those differ by type and by search feature. Google’s Rich Results Test does that for the types it supports.

Why does it find no schema when I know I added it?

The tool reads the HTML before JavaScript runs. If schema is added by a script or a tag manager, it won’t show here. Other things to check are caching, and whether the plugin is active on this page type.

Does schema markup improve rankings?

Google describes it as helping it understand your content and enabling enhanced displays. Treat it as a way to be understood and presented better, and don’t count on it as a ranking boost.

Related tools

  • On-Page SEO AuditOne report on a page’s title, headings, images, links, schema and robots.txt.
  • Meta Tags CheckerSee the title, description, canonical and share tags a page actually serves.
  • AI Visibility CheckerSee which AI crawlers your robots.txt allows, plus llms.txt and schema readiness.

Sources