Schema markup checker

What is schema markup

Schema markup is structured data written in the schema.org vocabulary. It tells search engines what a page is about in a form they can read without guessing: the company behind the site, the article and its author, the questions a page answers.

Google reads three formats: JSON-LD, Microdata and RDFa. It recommends JSON-LD, a script tag holding a block of JSON that sits apart from your HTML, so it’s easy to add and keep up to date. Google says structured data can make a page eligible for rich results, like breadcrumbs under your link, but it doesn’t promise them.

The markup has to describe what’s on the page. Marking up answers, reviews or prices a visitor can’t see breaks Google’s structured data guidelines.

Which schema a SaaS site needs

Most SaaS sites need four page types covered. The checker flags a missing type when you pick the page type, or when Auto can tell what kind of page it is.

On the homepage, Organization carries your name, URL, logo and sameAs links to your profiles, and WebSite carries the site name Google can show in results. Give each one an @id, like https://example.com/#org, and point other blocks at it instead of repeating the company in every block.

On blog posts, add the author as a Person with a name and a URL, and keep datePublished and dateModified in ISO 8601, like 2026-10-28. BreadcrumbList shows the path back to your blog. Google’s software app rich result also needs a rating or reviews, so only add those when they’re real.

FAQ markup and AI answers

Since August 2023, Google only shows FAQ rich results for well-known, authoritative government and health sites, and its update log says the feature stopped appearing from 7 May 2026. You don't need to remove FAQ markup, but don't expect the dropdowns.

For AI Overviews and AI Mode, Google says there’s no special schema.org structured data you need to add. What it does ask is that your structured data matches the visible text on the page. That’s why the checker warns when an FAQ answer in the markup isn’t on the page.

If a page has questions and answers, write them for the reader first: the question as a heading and a direct answer under it, in plain text on the page.

FAQ

What does a schema markup checker do?

It reads the structured data on a page, lists each schema type and checks it for the fields Google’s docs list. This one reads JSON-LD, the format Google recommends, and flags what a SaaS homepage, blog post, FAQ page or product page usually carries but yours doesn’t.

Is this the same as Google’s Rich Results Test?

No. The Rich Results Test shows which Google rich results a page can get, and it runs the page’s JavaScript. This checker reads the HTML your server sends, also checks types with no rich result, like Organization, and gives you a starter for each missing type. Every result links to the Rich Results Test, so you can use both.

Why doesn’t my schema show up here?

We read the HTML your server sends. If a script adds your JSON-LD after the page loads, it isn’t in that HTML. Paste the rendered HTML from your browser’s dev tools instead. Microdata and RDFa are counted, but not checked yet.

Does schema markup improve rankings?

Google says structured data helps it understand a page and can make the page eligible for rich results, but it doesn’t guarantee them. Treat it as a way to describe your pages accurately, not a shortcut.

Do you store the URL or the HTML?

No. Our server fetches a URL once and sends the HTML straight back to your browser, where the checks run. Pasted HTML never leaves your browser.

Read next

• Technical SEO: indexing, rendering and AI crawlers
• Schema markup for SaaS sites: what Google supports
• How to show up in Google AI Overviews
• AI crawler checker, for checking which AI crawlers your robots.txt lets in
• llms.txt generator and checker, for building or checking an llms.txt
• SERP preview tool, for checking titles and meta descriptions