Scanner Issues

If your cookie scans are failing or returning incomplete results, here are the common causes.

Scan Timeouts

Problem: The scan takes too long and times out. Causes:

Too many pages to crawl
Slow server response times
Complex JavaScript rendering

Fix: Reduce the crawl depth in your scan settings. Start with depth 2 and increase gradually. You can also use the URL blocklist to exclude non-essential sections like blog archives or paginated listings.

Missing Pages

Problem: The scanner doesn't find all your pages. Causes:

No sitemap.xml available
Pages require authentication
Pages are JavaScript-rendered with no server-side fallback

Fix: 1. Make sure your site has a valid sitemap.xml at the root 2. Add important URLs to the scan allowlist manually 3. The scanner cannot access pages behind login — these are excluded by design

No Cookies Found

Problem: The scan completes but reports zero cookies. Causes:

The site genuinely uses no cookies (unlikely but possible)
Cookies are only set after user interaction (clicking buttons, submitting forms)
Third-party scripts load conditionally

Fix: This may be accurate if your site is a simple static page. If you know cookies should be present, check that third-party scripts aren't loaded lazily behind user interaction.

Incorrect Categorization

Problem: Cookies are assigned to the wrong category. Fix: Auto-categorization uses vendor pattern matching which isn't perfect. Go to your site's Scanning tab, review the findings, and manually reassign any miscategorized items.

Scan Limits

Remember that scan limits vary by plan:

Free — 50 URLs per weekly scan, 1 on-demand scan per month
Starter — 500 URLs, 10 on-demand scans
Pro — 5,000 URLs, 100 on-demand scans

If you're hitting limits, consider upgrading or using the blocklist to focus on important pages.