A issue with the cookie concept. The site scan gets stuck on page 400–500 (out of 1,650) and doesn’t update, no matter how long I wait. I’ve tried several times, but nothing changes. It keeps getting stuck on different pages every time.
This looks like a configuration issue rather than a hard limit — we’ve seen this exact symptom on large, complex sites after a v1 to v2 migration, and it was resolved through a couple of setup checks. Here’s what to look at first:
Enable the auto-generated sitemap. Go to Webflow Site Settings > SEO and turn on Auto-generate sitemap. Without it, our scanner falls back to crawling only pages it can discover through the Webflow API and linked pages — on a 1,650+ page CMS site, that fallback crawl is much more likely to stall or miss pages. Enabling the sitemap gives the scanner a complete, direct list of URLs to work from.
Check for draft, password-protected, or archived pages. These can cause the scan to hang or fail partway through. A few ways to address it:
Publish all relevant pages before scanning
Remove unfinished draft pages from the sitemap
Or manually configure trackers for protected content if those pages need to stay private
Once you’ve enabled the sitemap and confirmed there are no blocking draft or password-protected pages, try running the scan again.
Since we can’t inspect your Webflow project settings directly from what’s been shared, could you send over a read-only link or confirm the sitemap and page status? That’ll help us pinpoint exactly what’s happening rather than guessing.
If the scan still stalls after these changes, let us know and we’ll loop in the team to dig into the backend scan behavior directly given the scale of your site.