Allowlist the Peak Visibility scanner

Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/126.0.0.0 Safari/537.36

X-Scanner: PeakVisibility SEO Scanner (+https://www.peakvisibility.io)

We crawl from Vercel's shared infrastructure, so our requests don't come from one fixed IP or IP range — allowlisting by User-Agent or the header above is the reliable option, not IP allowlisting.

1. Log in to the Cloudflare dashboard for your domain.
2. Go to Security → Bots and turn off Bot Fight Mode (or Super Bot Fight Mode) temporarily, or exclude our User-Agent from it.
3. For a permanent fix: go to Security → WAF → Custom rules → Create rule → set the condition to Header "X-Scanner" contains "PeakVisibility" → action Skip (skip remaining bot-management rules) → Deploy.
4. Re-run your scan from Peak Visibility.

1. In your Sucuri firewall dashboard, go to Settings → Whitelist.
2. Add a User-Agent whitelist entry matching the Chrome User-Agent string above.
3. Save, then re-run your scan.

1. In Akamai Bot Manager, create a Bot Category or Custom Bot entry for the User-Agent above.
2. Set its action to Allow / Monitor rather than Deny or Challenge.
3. If you don't manage Akamai directly, ask whoever does (often your host or agency) to add this exception.

1. In the AWS WAF console, edit the Web ACL attached to your CloudFront distribution.
2. Add a rule that matches the X-Scanner header value above with action Allow, and set its priority above any bot-control managed rule group.
3. Save and re-run your scan (AWS WAF changes can take a minute or two to propagate).

1. In your Fastly service, add a VCL snippet or edge dictionary entry that matches the X-Scanner header and bypasses your bot-detection logic for matching requests.
2. If you use a third-party bot product on top of Fastly (e.g. a WAF add-on), add the exception there instead.

1. Go to Site Settings → Bots in the Imperva dashboard.
2. Add the User-Agent above to your "Good Bots" or custom allowlist.
3. Re-run your scan.

1. Log in to your SiteLock dashboard (often via your hosting provider's panel).
2. Look for firewall/WAF settings and add a User-Agent exception matching the string above.
3. If you can't find this setting, contact SiteLock or your host's support and ask them to allowlist the User-Agent for a one-time crawl.

You can skip all of this — export your site's HTML (most CMS platforms have a static export option) and upload it as a ZIP instead. That bypasses any firewall entirely since nothing is crawled live.