What schema markup is your page missing?
Most schema tools tell you whether the markup you already have is well formed. This one starts from the gap: paste a URL or raw JSON-LD and see which schema types the page carries, which ones a page doing that job would normally carry as well, and what to add first. No account needed.
What this checks
There are two ways in. Give it a URL and the page is requested once, as ClimbrIQBot, with a ten-second timeout. It is one page per run, not a crawl. Give it raw JSON-LD instead and nothing is fetched at all, which is useful for markup you have written but not yet deployed.
- JSON-LD blocks — every
script type="application/ld+json"on the page is collected, not just the first one. Sites often carry several, added by different plugins over time. - Microdata — every element with an
itemtypeattribute is collected too, so older inline markup shows up alongside the JSON-LD. - Page context — the title tag and whether the page has an H1 go along with the markup, because what a page is determines which types it ought to have.
That collection is then read by a language model, which returns the types it found, the types it judges to be missing with a priority against each, the issues it can see, a score out of 100 and a short summary. Worth being plain about what that means: nothing here runs your markup through Google's parser. A model reads it and gives you a considered opinion.
How to read your results
The missing types list
This is the part to act on. Each entry names a type, gives a reason it belongs on a page like yours, and carries a priority of critical, high or medium. Critical usually means the type that matches the page's core purpose is absent entirely: a product page with no Product, an article with no Article, a contact page with no LocalBusiness.
The score out of 100
The score is the model's summary judgement, not a measurement of anything. It is most useful compared against itself: run the page, make the changes, run it again and see whether the number moved. Reading it as an absolute grade against other sites will tell you very little.
The ticks, crosses and top issues
Each found type is marked as looking sound or not, and the first three issues it raises are shown underneath. Treat a cross as a prompt to look, not a verdict. For anything that affects whether a rich result actually appears, Google's Rich Results Test is the one that counts, and it is free to run.
What to fix first
- A page with no structured data at all. Everything below assumes there is something to improve.
- The type that matches what the page actually is. One correct primary type beats five decorative ones.
- Required properties missing from a type you already have. An incomplete Product is often treated as no Product.
- Markup that claims something the page does not show. FAQPage with no visible questions is the common version, and it is the kind of mismatch that gets your structured data ignored.
- Duplicate blocks that contradict each other. Two plugins each writing an Organization block with different details leaves a machine to pick one.
Structured data is how an answer engine reads a page without inferring everything from prose, which is why it matters more now than it did when rich snippets were the only prize. The guide to answer engine optimisation covers what sits around it, and the heading structure analyser checks whether the visible page is organised as clearly as the markup claims.
Frequently asked questions
- Is this the same as Google's Rich Results Test?
- No, and it is not a replacement for it. Google's Rich Results Test is the authority on whether a page qualifies for a rich result, because it is Google deciding. This tool answers the question that comes before that one: which schema types is the page missing for the job it is doing? Use this to decide what to add, then run the Rich Results Test on the finished page to confirm Google accepts it.
- Does it check that my JSON-LD is syntactically valid?
- Not in the strict sense. The markup is read by a language model, which reports the problems it recognises and marks each type it found as looking sound or not. That is a judgement, not a parser verdict, and it can be wrong in both directions. If you need a definitive answer on syntax, use a JSON validator or the Rich Results Test.
- Does adding schema markup improve rankings?
- Not by itself. Structured data describes what a page is about in a form machines can read without guessing, which is what makes rich results and AI answer citations possible. The gain is in how your page is presented and understood, not in a position bump you can attribute to the markup alone.
- Does this check every page on my site?
- No. In URL mode it fetches the one page you give it. Structured data usually varies by page type rather than page by page, so checking one example of each type covers most of the ground. If you want the whole site checked, and the markup added rather than listed, that is what the paid ClimbrIQ plan does.
- Why did the check fail on my URL?
- The page is requested as ClimbrIQBot with a ten-second timeout. It fails if the page returns an error status, times out, or blocks non-browser user agents, and pages behind a login or a bot challenge cannot be read. If you see a rate limit message instead, the limit is 30 checks an hour per IP address.
- Do I need an account?
- No. The on-page result is free and needs no signup. Entering your email gets you a longer written report covering the same analysis, with JSON-LD code examples for the types you are missing and an order to implement them in.