# Consent Pro V2 — scan fails ("couldn't access any pages"), script not detected, and empty consent logs on a live, publicly-accessible site **URL:** \ **Category:** Consent Pro\ **Tags:** consent-pro-v2\ **Created:** [July 16, 2026, 1:13pm UTC](https://forum.finsweet.com/t/consent-pro-v2-scan-fails-couldnt-access-any-pages-script-not-detected-and-empty-consent-logs-on-a-live-publicly-accessible-site/7443 "2026-07-16T13:13:17Z")\ **Posts on this page:** 18\ **Page:** 1
**Author:** ![marco1](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.finsweet.com/marco1/32/3671_2.png) [@marco1](https://forum.finsweet.com/u/marco1)\ **Post date:** [July 16, 2026, 1:13pm UTC](https://forum.finsweet.com/t/consent-pro-v2-scan-fails-couldnt-access-any-pages-script-not-detected-and-empty-consent-logs-on-a-live-publicly-accessible-site/7443/1 "2026-07-16T13:13:17Z")
Consent Pro V2 on my published Webflow site is failing in three related ways — even though the consent banner itself works correctly on the live site: 1. The site scan fails at the very end with “We couldn’t complete the scan — We couldn’t access any pages on your website.” It appears to find and crawl the pages during the scan, then errors out at the finish. I’ve run it several times with the same result. 2. The app does not detect that the consent script is installed, although the banner renders and works on the live site. 3. Consent Logs & Analytics show no entries at all — no accept/reject records — despite the banner functioning. ## Site URL [https://www.tergar.de](https://www.tergar.de) (published, public, no password protection) ## Steps to Reproduce 1. Open the Consent Pro app → Manager → Consent Manager. 2. Run the site scan. 3. The scan appears to find/crawl pages, then ends with “We couldn’t complete the scan / couldn’t access any pages.” 4. The app continues to report the consent script as not installed. 5. Consent Logs remain empty. ## Expected Behavior Scan completes and detects trackers; the app recognizes the installed script; consent logs record accept/reject events. ## Actual Behavior Scan fails, script not detected, logs empty. ## What I’ve already ruled out (so we can skip the usual first steps) - The site is published and publicly reachable — it loads fine in any browser, no password protection. - robots.txt is clean: it contains only the `Sitemap:` directive, no `Disallow`. Crawlers are not blocked. - sitemap.xml is complete and valid — 74 URLs, all consistently on [https://www.tergar.de](https://www.tergar.de). - The consent banner DOES render and work on the live site (verified in a clean Chrome incognito window). - Google Consent Mode signals are flowing correctly client-side: `gcs=G100` (denied) before consent, `gcs=G111` (granted) after clicking Accept — so the script is live and functioning. - No CSP issue: the browser console shows no “Refused to connect” / Content-Security-Policy errors, and the verification call to [accounts.finsweet.com](http://accounts.finsweet.com) is not being blocked by a site-side CSP. - The “publish the site while the app is open” workaround (from another forum thread) did not resolve it. ## Environment - Platform: Webflow (published to the production custom domain) - Consent Pro V2 - Tested in Chrome and Firefox (macOS) Given the above, this looks like a server-side scan/verification issue on Consent Pro’s side rather than a site-configuration problem. Happy to provide any additional details or grant access via DM. Thanks in advance! ---
**Author:** ![jesse.muiruri](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.finsweet.com/jesse.muiruri/32/6611_2.png) [@jesse.muiruri](https://forum.finsweet.com/u/jesse.muiruri)\ **Post date:** [July 16, 2026, 5:58pm UTC](https://forum.finsweet.com/t/consent-pro-v2-scan-fails-couldnt-access-any-pages-script-not-detected-and-empty-consent-logs-on-a-live-publicly-accessible-site/7443/2 "2026-07-16T17:58:53Z")
Hey @marco1! Since you’ve already ruled out the common culprits (sitemap, robots.txt, CSP, gcs signals, the publish-while-open workaround), let’s skip straight to the two things worth investigating in parallel here. **Incomplete V2 migration — check this first** The pattern of scan failing + script not detected + empty logs matches exactly what happens when the V2 migration isn’t fully complete. The Consent Pro v2 migration requires all three of these to be in place: 1. The new V2 script installed in the custom code `` section 2. A banner created fresh inside the v2 app (the old v1 banner is not compatible with v2 logs or scan detection) 3. The old legacy Consent Pro code block removed from “Code Added by Apps” Even if the banner visually renders on the live site (it can pull from a v1 config), logs and scanner detection won’t work until the v2 setup is fully validated with a **“You are all set”** success message in the app’s Actions tab. Was the banner generated fresh inside the Consent Pro v2 app, or was it originally created in v1? **Scanner-level access issue** Since client-side behavior is working fine, the “couldn’t access any pages” error points to a server-side access problem — not a browser issue. Is your Webflow site proxied through any CDN or security service (Cloudflare, Fastly, Sucuri, etc.) at the DNS level? Even with no rules configured, some services apply automated bot filtering by default. **One thing to fix regardless** The Google Tag Manager `