Skip to main content

Allow the scanner

camolabs must read public marketing pages before it can generate agent-ready versions.

Some bot protection tools challenge automated traffic. If that happens, camolabs sees the challenge page instead of your content, and the scan marks those pages as blocked.

This affects scanning only. It does not change how your site handles live automated traffic.

If your site is already installed with camolabs, scans include an origin request parameter so the scanner reads your real page rather than the agent-ready version camolabs would otherwise serve back to it.

How it appears​

The scan detail page can show:

Your site's bot protection blocked our scanner.

Blocked rows may also say that the page showed a security checkpoint instead of the requested content.

Fix it​

Allow the scanner long enough to run the scan, then rescan.

Vercel​

  1. Open the project in Vercel.
  2. Go to Firewall.
  3. Add a rule that allows requests to the marketing paths you want scanned.
  4. If you use Bot Protection, add a temporary exception for the scan window.

Cloudflare​

  1. Open the zone in Cloudflare.
  2. Go to Security > WAF > Custom rules.
  3. Add a path-scoped Skip rule for the scan window, or temporarily lower Bot Fight Mode.

Other providers​

Most WAF and bot-management tools support a temporary allow rule or path-scoped exception.

The scanner reads a bounded set of public marketing pages once per run, so a short window is usually enough.

If pages are still blocked​

Once camolabs reads a page successfully, rescans skip it until the source changes.

If you cannot change protection settings, contact support.