MadbotzVisibilityBot

What this bot does

MadbotzVisibilityBot fetches public web pages on demand whenever a Madbotz Visibility user requests an analysis of a site. It does not crawl recursively, does not follow links, and does not store the fetched content beyond the user's report (cached for 7 days, then purged). One request to your site equals one report generated by a Madbotz user.

How to identify it

The scanner identifies itself with this exact User-Agent across all three crawling layers (curl, fetch, headless browser):

MadbotzVisibilityBot/1.0 (+https://visibility.madbotz.com/bot)

Example log line

203.0.113.42 - - [22/May/2026:14:31:17 +0000] "GET / HTTP/1.1" 200 12345 "-" "MadbotzVisibilityBot/1.0 (+https://visibility.madbotz.com/bot)"

Hosting: standard Vercel functions in AWS Lambda us-east-1 (dynamic IPs within Vercel's pool — we do not publish static IP ranges, so allowlists should be based on the User-Agent above). The headless-browser layer originates from Google Cloud Run us-central1.

Allowlist the bot in your WAF

If your site is protected by a WAF that challenges bot traffic (Cloudflare Bot Fight Mode, AWS WAF Bot Control, Akamai Bot Manager, etc.), the scanner may receive a challenge page instead of your real content — producing inaccurate scores. To prevent this, add a rule that exempts the User-Agent above.

Cloudflare (Free plan and above)

Security → Security rules → Create rule. Field: User Agent. Operator: contains. Value: MadbotzVisibilityBot. Action: Skip — tick Bot Fight Mode, Browser Integrity Check, and all managed rules.

(http.user_agent contains "MadbotzVisibilityBot")
→ Action: Skip
→ Skip: Bot Fight Mode, Browser Integrity Check, All managed rules

Vercel Firewall

Create a custom rule with the condition «User-Agent contains MadbotzVisibilityBot» and action «Allow».

Other WAFs

Any WAF that supports rule conditions on the User-Agent header can allowlist the scanner. Use a substring match on «MadbotzVisibilityBot» so future versions (1.x, 2.x, …) keep matching the same rule.