Schema Markup Checker and Analyzer
See every structured data entity on up to five pages, how complete each one is, and which types your competitors use that you do not.
What the analyzer inspects on each page
Pages are fetched live and every JSON-LD script is parsed, including nested @graph structures, so markup added by several plugins is all counted.
- Every JSON-LD block
- Up to 24 blocks per page, each up to 100 KB. Blocks that will not parse, or are too large, are counted as unreadable.
- Flattened entities
- Objects inside @graph and nested items are pulled out and checked one by one, up to 60 per page, with exact repeats removed.
- Core properties
- The properties the checklist expects for a complete entity of that type, such as headline, image, datePublished and author for an Article.
- Recommended properties
- Extra properties that make the entity richer, such as dateModified, publisher and inLanguage on an Article.
- Child items
- Lists are checked inside too, for example each breadcrumb step needs a position, a name and an item address.
- Google feature status
- Each type is labelled active, limited, retired or none, so you know whether Google still shows a search feature for it.
- Coverage across pages
- A grid of which types appear on which page, with the score of each, sorted so the most useful types come first.
- Gaps against the first page
- Types that the other pages use and the first one does not, listed with how many of the others have them.
How to analyze schema markup
List your page first
Put the page you want to improve on the first line. Comparisons and templates are built around it.
Add pages to compare
Up to four more: the pages that rank above you, or other templates on your own site such as a product and a category.
Run the scan
Pages are read three at a time. A page that cannot be reached gets its own error, the rest still finish.
Work through the findings
Fix unreadable blocks first, then missing core properties, then decide which gap types truly describe your page.
A page has roughly 15 seconds to answer, and the first 2 MB of HTML is read. Only JSON-LD is read: microdata and RDFa in the HTML are not scored.
How to read the scores and findings
Scores measure completeness against a checklist. They do not decide rich result eligibility, which only Google's own tests can confirm.
- Completeness score and grade
- Core properties count for 70 points, recommended ones for 25, and 5 more go to an entity with no warnings. Grades run A from 90, B from 80, C from 65, D from 50, and F below that.
- Average Completeness
- The mean score across all entities on the pages that were read.
- JSON-LD Entities and Unique Types
- How many typed objects were found in total, and how many different schema types they cover.
- Types not in the checklist
- Scored only on how many properties are filled, capped at 70, with a note saying so.
- Retired type finding
- The page uses a type such as HowTo whose Google feature has been withdrawn. Harmless, but it earns no rich result.
- Templates
- Up to 12 starter blocks for types with an active Google feature that the first page does not use yet, prefilled with its domain.
Structured data problems it uncovers
A JSON-LD block that cannot be read
Fix: Usually a stray comma, an unescaped quote or a template tag that printed nothing. Fix the syntax and recheck: search engines skip broken blocks entirely.
Article markup with no image or date
Fix: Add image, datePublished and author from the visible post. Many SEO plugins have a setting for a default image that fills the gap.
Breadcrumb steps missing position or item
Fix: Each ListItem needs a numbered position, a name and the URL of that level. The last step may point to the current page.
No structured data at all
Fix: Start with Organization and WebSite on the home page, Article on posts and Product on product pages.
Duplicate Organization blocks from two plugins
Fix: Keep one source of structured data per site. Two plugins writing the same type often disagree on names and logos.
Competitors use types you do not
Fix: Copy only what is true for your page. A Review or FAQ block added just because a rival has it can break Google's guidelines.
Who runs a schema audit
- SEOs comparing a client page with the pages that outrank it.
- Developers checking that a theme update did not break structured data.
- Site owners running two SEO plugins and wondering which markup wins.
- Content leads making sure every article template ships complete markup.
Types Google has stepped back from
Google limited FAQ rich results to well known government and health sites in 2023, retired HowTo results the same year, and removed the sitelinks search box in 2024. The analyzer marks these so you do not spend effort chasing a result that no longer exists.
Schema Intelligence Analyzer FAQ
Short answers about the Schema Intelligence Analyzer.
Up to 5 per run. Put your own page first so the gap list and templates are built around it.
No. It reads JSON-LD only, the format Google recommends. If your theme uses microdata, convert it or check it with a separate validator.
No. The score means the entity has every property on the checklist. Google decides eligibility from the page, the site and its policies.
They have different @id values or different content, often from two plugins or a theme and a plugin both adding markup.
Google no longer shows a search feature for it. The markup does no harm and other search engines may still use it, but it adds no rich result in Google.
No. The analyzer only sees the raw HTML your server returns, so JSON-LD injected later by a script in the browser will not be seen here.
Related SEO tools
Schema Generator
Valid JSON-LD for 17 schema types from a form.
Free, unlimitedOn-Page Audit Pro
70 checks on one page, scored against the basics.
1 free run a daySite Audit Pro
Crawl up to 100 pages and get a technical health score.
1 free run a daySERP Competitor Analysis
How the top ranking pages are built, side by side.
Your own key