Three steps to a readiness report
- 01
Discover sampled product pages
CatalogProof finds product URLs from sitemaps and storefront links, then selects a representative sample - 10 pages on the free scan, up to 250 on a full crawl upgrade.
- 02
Scan rendered product pages
Each page is loaded in a headless browser. We check visible text, structured data, images, forms, GPSR listing signals, and accessibility issues such as labels, contrast, and alt text.
- 03
Review the executive report
You get a readiness score, recurring pattern table, affected product pages ranked by risk, and prioritized fix buckets for catalog, theme, and content owners.
What is in the report
- Executive conclusion - high-level takeaways from patterns across sampled pages.
- Top recurring patterns - grouped by issue type, severity, and coverage across the sample.
- Affected pages - one row per product page with expandable GPSR and EAA findings.
- What to fix first - prioritized implementation buckets; becomes a full checklist on unlocked reports.
- Live progress - watch discovery and page scans in real time while the job runs.
Free scan vs full crawl
The free scan is designed to be genuinely useful: you see real patterns and real affected pages from a sampled subset. When you need broader coverage, unlock a one-time full crawl for:
- Up to 250 product pages
- CSV export of affected URLs and findings
- Full affected page list and implementation checklist
- Shareable report link for your team or agency
Who should run a scan?
Any ecommerce store with a public product catalog selling into EU markets - especially when product-safety fields live in metafields, theme sections, or PIM exports that are hard to QA page by page.