Site scan
Find the pages on your site that are missing structured data
Give the scan a sitemap and it checks each page for the structured data it carries and the schema it could carry. Use it to decide which pages to fix first.
Results
| Page | Score | Schema found | Could add | Issues | Next step |
|---|
How a scan works
Read the sitemap
Pages on the same host are collected. Sitemap indexes are followed to their first three child sitemaps.
Check each page
The same analysis as the generator runs on every page, a few at a time.
Fix the worst first
Each row has a score and links to the generator for that page. Download the markup for every page at once, or export the table to share it.
Scans cover up to 10 pages and three a minute for each address. For larger sites, scan one section at a time or use the API.
Questions
Which pages does the scan check?
The pages listed in the sitemap that are on the same host as the sitemap, up to 10. Images, documents and other files are skipped, and each address is checked once.
Can I scan a site I do not own?
Only scan sites you own or have permission to check. The scanner identifies itself as SchemaForge in its User-Agent so site owners can recognise it, and it reads one small batch of pages at a time.
What does the Issues column count?
Errors are missing properties that Google requires, such as an offer with no currency, plus any JSON-LD block that cannot be parsed. Notes are recommended properties that are absent.
How do I get the results out?
When the scan finishes, Download markup (zip) gives you one file with a summary, every issue on its own line, and ready-to-paste JSON-LD for each page that could use some. Export CSV gives just the summary table. Both include each page’s schema health score.