Skip to content

Schema markup validator: see which rich results your page can get

This schema markup validator finds every structured data block on your page, shows which rich results it qualifies for, and names the required property missing on each type.

  • Free, no account
  • Results in under a minute
  • JSON-LD and microdata

Example result:example-shop.hr

WordPress 6.8

Sample shop · homepage · mobile Chrome · the same check you get for your own site

Run it on your site
Schema markup validator
4 passed · 0 failed · 4 warnings · 1 to note. Biggest issue: Add offers.price to Product structured data.

Structured data blocks

2 blocks · 0 with errors · 0 eligible for rich results
Each structured data block with its type, format, whether it parses, rich result status and missing required properties
BlockTypeParsesRich resultMissing required
JSON-LD 1ProductTenisice Runner Xyesnot yet: properties missing
  • offers.price
JSON-LD 2OrganizationExample Shopyesnone for this typenone

What we found

0 failed4 warnings1 to note4 passed
Show 4 passed checks

Fix these first

From the example above. Check your own site to get the fixes that apply to it.

  1. Warning: Add offers.price to Product structured data

    Google shows a rich result (price, stars, FAQ, breadcrumb) only when the entity carries the properties it requires.

    How to fix it: Open the technical detail for the full list, one line per entity type and property.

  2. Warning: Not eligible for rich results: Product

    Rich results (price, stars, FAQ or breadcrumbs under your listing) make it bigger and earn more clicks than a plain blue link.

    How to fix it: Fix the properties listed under "required properties missing" first; eligibility follows automatically.

  3. Warning: WooCommerce Product schema is missing 2 rich-result fields (Tenisice Runner X: offers.price (or offers.lowPrice), Tenisice Runner X: aggregateRating or review (only if the product has reviews))

    Google shows the price, stock state and stars in results only when the Product block carries offers.price, offers.availability and a rating.

    How to fix it: Fill in the product's regular price and stock status; enable reviews if you have them. If an SEO plugin or builder outputs its own Product block, let WooCommerce's (or the plugin's, not both) be the single source.

What the schema markup validator checks

Every structured data item, grouped by rich result like Google's Rich Results Test, with its critical and non-critical issues and all its properties.

  • Structured data

    Checks for JSON-LD that lets Google show prices, ratings and breadcrumbs under your listing.

  • JSON-LD syntax

    Checks every JSON-LD block parses, because one syntax error makes Google ignore the whole block.

  • Microdata usage

    Notes microdata attributes in the HTML, which still work but are read by fewer tools than JSON-LD.

  • Structured data types

    Lists the entity types the page declares, so you know which rich results it can earn.

  • Required schema properties

    Checks each entity has the properties Google requires before it shows a rich result.

  • Rich result eligibility

    Shows which entities qualify for rich results like price, stars or breadcrumbs in search.

  • Organization logo and profiles

    Checks your Organization data has a logo and social profile links for Google's brand box.

  • WooCommerce Product schema fields

    Checks WooCommerce products carry price, availability and rating so Google can show them in results.

  • Schema from multiple plugins

    Checks only one plugin outputs structured data, since conflicting blocks make Google withhold rich results.

  • Duplicate schema entities

    Checks the same Organization, WebSite or Product is not described twice with possibly different details.

  • Organization schema

    Looks for Organization or LocalBusiness JSON-LD on your home, about and contact pages.

  • Organisation name

    Compares the name on your pages, in your schema and on Wikidata, ignoring legal forms like Ltd.

Show 22 more checks

  • Required schema properties

    Checks each entity has the properties Google requires before it shows a rich result.

  • Rich result eligibility

    Shows which entities qualify for rich results like price, stars or breadcrumbs in search.

  • Organization logo and profiles

    Checks your Organization data has a logo and social profile links for Google's brand box.

  • WooCommerce Product schema fields

    Checks WooCommerce products carry price, availability and rating so Google can show them in results.

  • Schema from multiple plugins

    Checks only one plugin outputs structured data, since conflicting blocks make Google withhold rich results.

  • Duplicate schema entities

    Checks the same Organization, WebSite or Product is not described twice with possibly different details.

  • Organization schema

    Looks for Organization or LocalBusiness JSON-LD on your home, about and contact pages.

  • Organisation name

    Compares the name on your pages, in your schema and on Wikidata, ignoring legal forms like Ltd.

  • Founding year

    Compares the year on your about page with schema foundingDate and Wikidata's inception.

  • Address

    Compares your footer or contact address with your schema address and Wikidata's headquarters.

  • Phone number

    Compares tel links, schema telephone and Wikidata's phone, digit by digit with the country code.

  • Logo

    Checks your Organization schema names a logo image for search and assistants to show.

  • Profiles and sameAs

    Checks your schema's sameAs links your official profiles and, when one exists, your Wikidata item.

  • Wikidata item

    Looks your organisation up on Wikidata by official website first, then by name.

  • Wikidata item

    Finds the item by official website (P856) first, then by name, and shows what it says.

  • Official website (P856)

    Checks the item names your site as its official website, the link that ties the item to you.

  • Description

    Checks the item has a short English description, the line shown under its name.

  • Inception (P571)

    Checks the item says when the organisation was founded.

  • Headquarters (P159)

    Checks the item says where the organisation is based.

  • External identifiers

    Counts the identifiers that link the item to other databases and your profiles.

  • Wikipedia articles

    Counts the Wikipedia articles, by language, that the item links.

  • Logo (P154)

    Checks the item has a logo image from Wikimedia Commons.

Show 14 more checks

  • Founding year

    Compares the year on your about page with schema foundingDate and Wikidata's inception.

  • Address

    Compares your footer or contact address with your schema address and Wikidata's headquarters.

  • Phone number

    Compares tel links, schema telephone and Wikidata's phone, digit by digit with the country code.

  • Logo

    Checks your Organization schema names a logo image for search and assistants to show.

  • Profiles and sameAs

    Checks your schema's sameAs links your official profiles and, when one exists, your Wikidata item.

  • Wikidata item

    Looks your organisation up on Wikidata by official website first, then by name.

  • Wikidata item

    Finds the item by official website (P856) first, then by name, and shows what it says.

  • Official website (P856)

    Checks the item names your site as its official website, the link that ties the item to you.

  • Description

    Checks the item has a short English description, the line shown under its name.

  • Inception (P571)

    Checks the item says when the organisation was founded.

  • Headquarters (P159)

    Checks the item says where the organisation is based.

  • External identifiers

    Counts the identifiers that link the item to other databases and your profiles.

  • Wikipedia articles

    Counts the Wikipedia articles, by language, that the item links.

  • Logo (P154)

    Checks the item has a logo image from Wikimedia Commons.

How the schema markup validator works

  1. Find the markup

    Every JSON-LD block and microdata item on the page is found, parsed and its types listed.

  2. Check required properties

    Each item is checked per rich result, such as Product snippets, Merchant listings or Breadcrumbs. A missing required property or a bad value is critical, a missing recommended one non-critical. Retired types like FAQ show their end date.

  3. Flag conflicts

    Duplicate or conflicting entities are flagged, and each problem comes with a plain-language fix.

Rich results are checked for JSON-LD and microdata; the findings and the duplicate checks read JSON-LD only. RDFa is not parsed, and Google can still choose not to show a valid item.

Structured data and rich results questions

How do I test schema markup on my website?

Enter the page address above. The validator finds every JSON-LD block on the page, lists its types and checks them against the properties Google requires for rich results, naming the missing ones. Google's Rich Results Test checks the same eligibility, and the Schema Markup Validator at validator.schema.org checks against the full schema.org vocabulary.

Which rich results can my page get?

It depends on the types on the page: Product can show price, stock and review stars; Breadcrumb replaces the URL line with the page's path; Event and Recipe have their own layouts; Article helps Google show the right headline, image and date. The validator shows which rich results each block qualifies for. Qualifying makes a page eligible, not guaranteed; Google decides per search.

Why does the validator find duplicate entities?

Because two sources describe the same thing, typically a theme and an SEO plugin both adding Organization or Product markup, or JSON-LD plus microdata for the same product. Google may merge them or pick one, and conflicting values, such as two different prices, can cost the rich result. Keep one source per entity, usually the SEO or shop plugin, and switch the other off.

Can I validate JSON-LD before it is live?

Not here: this validator checks published pages by URL. For code that is not live yet, paste it into Google's Rich Results Test, which accepts a code snippet, or build it with our schema generator, which checks the required properties as you fill in the form. Once the page is published, run it through this validator to confirm Google can read it.

Why are my review stars not showing in Google?

Google shows review stars only for certain types, such as Product, Recipe, Book or Course, and not for reviews about a business on its own site: for Organization and LocalBusiness those count as self-serving and have been ignored since 2019. The markup also needs ratingValue plus reviewCount or ratingCount, and the reviews must be visible on the page.

Is this a replacement for Google's Structured Data Testing Tool?

Partly. Google retired its Structured Data Testing Tool in 2021: general schema.org checks moved to the Schema Markup Validator on schema.org, and rich-result checks to Google's Rich Results Test. This free validator does a bit of both: like the Rich Results Test it groups your items by rich result and separates critical from non-critical issues, shows every property of each item, and explains each gap in plain language.

Do you support microdata and RDFa?

Both JSON-LD and microdata are checked in the rich results panel, item by item, the way Google reads them. The findings and the duplicate checks read JSON-LD only, and RDFa is not parsed. Google recommends JSON-LD, and most CMSs and SEO plugins output it, so moving old microdata to JSON-LD is usually the simplest way to keep it maintained.

Is this schema markup validator free?

Yes, with no sign-up. getReport is funded by donations, not plans, and the complete report with all seven modules is one click away, also free. It stays at its shareable link for 12 months, is not listed publicly and carries a noindex tag, and nothing about your visitors is collected.

Related free tools

All 59 tools →

Free, funded by the people who use it

No account, no paid plan. Donations keep it running.

Chip in