Schema markup validator
Enter a page URL or paste JSON-LD to find syntax errors and see, for each item, which properties Google requires and recommends and which are missing.
What it checks
- Syntax. Each JSON-LD block is parsed. A trailing comma or an unescaped quote makes Google ignore the whole block, so the line and column of the error are shown.
- Required properties. For Product, Offer, AggregateOffer, Review, AggregateRating, Article, BreadcrumbList, Organization, LocalBusiness, Event, Recipe, VideoObject, SoftwareApplication and JobPosting, the properties Google lists as required for its rich result.
- Recommended properties. The ones Google lists as recommended, so you can see what would make the result fuller.
- Nested items. Offers, ratings and reviews inside a Product are checked with their own rules, items inside an
@graphare checked one by one, and common subtypes such as BlogPosting and Restaurant use their parent type's rules.
Errors worth fixing first
A Product with a name but no offers, review or aggregateRating, an Offer without a price, and a rating without ratingCount or reviewCount are the most common reasons a product page shows no rich result. Our product schema markup guide explains each property. Remember that the values must match what the page shows.
Build it, then check it
If a page has no markup yet, start with the schema markup generator, then paste its output here. For which types are still worth adding, see types of schema markup worth adding in 2026. Across a whole site, a XeoRank site crawl reads the structured data on each page it crawls.
Questions
- Is this the same as Google's Rich Results Test?
- No. This tool reads the JSON-LD and compares each item with the required and recommended properties in Google's structured data documentation. Google's Rich Results Test renders the page with JavaScript and decides eligibility, so use it to confirm a page before you rely on a rich result.
- What is the difference from validator.schema.org?
- The Schema.org validator checks that markup uses the Schema.org vocabulary correctly. It does not tell you which properties Google needs for a rich result, because Schema.org itself has no required properties. This tool checks Google's lists.
- Why does my FAQ or HowTo markup show as no longer a rich result?
- Google retired both. How-to rich results stopped in September 2023, and FAQ rich results stopped appearing in Google Search in May 2026. The markup does no harm, but it no longer earns a rich result.
- Does it check microdata or RDFa?
- It counts microdata items so you know they are there, but it only validates JSON-LD, the format Google recommends.
- Why does the URL check miss markup I can see in the browser?
- The URL check reads the HTML your server sends, without running JavaScript. If a plugin or tag manager adds the JSON-LD after the page loads, paste the rendered source from your browser's developer tools instead.
More free tools
Reads your sitemap and page titles and drafts an llms.txt file you can edit and download.
Robots.txt generatorBuild a robots.txt that allows AI search crawlers and blocks AI training crawlers, with a WordPress preset.
AI crawler checkerShows which AI crawlers your robots.txt lets in: GPTBot, OAI-SearchBot, ClaudeBot, PerplexityBot, Google-Extended and more.
Meta tag checkerTitle, meta description, canonical, robots, H1 and Open Graph tags for up to 10 pages, with length checks and duplicates.
Sitemap checkerFinds every sitemap a site declares, counts the URLs, checks lastmod dates and spot-checks that listed URLs return 200.
Redirect checkerTests http, https, www and non-www versions of a site and shows every redirect hop, so you can see if they all land on one URL.
Schema markup generatorBuild JSON-LD for Organization, LocalBusiness, FAQ, Product and Article pages, ready to paste into your site.
Keyword density checkerWord count and the most repeated words and phrases in your text, plus how often a target keyword appears. Runs in your browser.
SERP snippet previewSee how your title and meta description may look in Google on desktop and mobile, and where they get cut off.
Open Graph checkerog:title, og:description, og:image and twitter:card tags for up to 5 pages, with a preview of the shared link card.
H1 checkerThe H1 heading of up to 10 pages, flagging pages with none or more than one.
Canonical tag checkerWhether each page's canonical points to itself, is missing, or tells Google to index a different URL.
Hreflang checkerHreflang tags, language and region codes, x-default and return links between language versions.
Core Web Vitals checkerReal-user LCP, INP and CLS from the Chrome UX Report plus a Lighthouse lab test, on mobile or desktop.