The Schema App Analyzer crawls your website, finds schema markup (JSON-LD, Microdata, and RDFa), and shows where markup is present, where it is missing, and how coverage changes over time.
Open it from Maintenance > Analyzer (https://app.schemaapp.com/maintenance/analyzer). The Analyzer opens on your latest crawl when one exists.
For page-set opportunities and type suggestions, see Run and read a scoping crawl.
Start a crawl with New Site
You can start an on-demand crawl any time you need a fresh snapshot (for example after a deployment).
- Go to Maintenance > Scoping Reports.
- Select New Site.
- Enter the website URL (your homepage is enough to start).
- Select Start Analyzer.
The crawl is placed on a queue and usually starts within about 20 minutes, depending on available resources. By default it covers up to 10,000 pages. If your site is larger, ask Schema App (support or your CSM) for a larger crawl — see Run and read a scoping crawl.
When the crawl finishes, open the results from Scoping Reports (View results) or open Maintenance > Analyzer. The Analyzer shows the crawl date in the header so you know how fresh the data is.
Read the Coverage tab
The Coverage tab answers: How much of the website currently has schema markup?
Summary cards
- Pages with Schema — pages where markup was found, including overall coverage %.
- Without Schema — pages where no markup was found.
- Pages Scanned — total pages included in this crawl.
Coverage trend
The coverage chart shows coverage % over time. Use the 30 / 60 / 90 day range once you have enough crawl history. Trend graphs that used to live in the Trend Report now appear here on the Analyzer results page.
Schema Types by Page
The table lists pages with detected schema types and markup source (for example Editor or WordPress). Search, filter, and download when you need a closer look.
Always confirm individual URLs with Google's Rich Results Test and the Schema Markup Validator when you need to troubleshoot a specific page.
Empty states and troubleshooting
| What you see | What it usually means | What to try |
|---|---|---|
| No analyzer crawl was found / No scan data yet | This project has not completed a crawl yet | Start a crawl with New Site (steps above) |
| No website on the project | The project needs a website assigned before crawls can run | Ask your CSM to confirm the project website |
| 0 pages found / crawl completes with empty Coverage | The crawler could not reach or process pages | Confirm SchemaBot is allowlisted; check robots/sitemap; contact Schema App if it still returns empty |
| Results stop near 10,000 pages | The default page limit was reached | Ask Schema App for a larger crawl |
| Crawl stuck on RUNNING for a long time | The crawl may be stalled | Wait for a reasonable period, then contact Schema App (include account and crawl) |
About the SchemaBot crawler
SchemaBot visits each page, records and validates markup found as JSON-LD, Microdata, or RDFa, then follows links to continue the crawl. It starts from the URL you enter, looks for sitemap.xml, and processes pages in parallel.
For allowlisting, see Allowlist Schema App IP Address & Endpoints for Full Functionality.
Related
- Run and read a scoping crawl — Scoping tab, Scoping Reports list, Legacy crawls, and larger crawl requests
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article