Letting the scanner read your site

1. If your site sits behind Cloudflare (many clinic sites do, sometimes via the hosting company), start with the Cloudflare section below.
2. If it's a WordPress site, check for a security plugin — Wordfence, Sucuri, iThemes/SolidWP, or All-In-One Security are the common ones. Each has its own section or the generic steps below apply.
3. If neither, ask your hosting provider or web person: "Please allowlist the crawler user agent AuthoritizeAuditBot so it can read our public pages." That one sentence is all they need.
4. Also confirm your robots.txt doesn't contain a blanket Disallow: / — the scanner respects obvious signals the way search crawlers do.

1. Log in at dash.cloudflare.com and pick your site.
2. Go to Security → WAF → Custom rules (on older dashboards: Firewall Rules) and create a rule: If User Agent contains AuthoritizeAuditBot then Skip (skip all remaining security features, or at minimum Bot Fight Mode and Super Bot Fight Mode).
3. If you use Bot Fight Mode (Security → Bots) and can't add a skip rule on your plan, the practical options are turning Bot Fight Mode off or upgrading to a plan that allows WAF skip rules — Bot Fight Mode has no allowlist of its own on the free plan.
4. Save. The next scan attempt will get through immediately — use the "scan again now" link in the email.

1. WordPress admin → Wordfence → Firewall → All Firewall Options.
2. Under Allowlisted URLs / Advanced Firewall Options, find "Allowlisted user agents" (older versions: whitelist) and add AuthoritizeAuditBot.
3. Also check Wordfence → Blocking for any custom pattern that matches generic bots, and Rate Limiting rules that "throttle" or "block" crawlers — set crawler rules to at least 50 requests per minute, or exempt the user agent.

1. Log in to the Sucuri dashboard (WAF product, not just the WordPress plugin).
2. Go to Firewall → Settings → Access Control → Allow User Agents and add AuthoritizeAuditBot.
3. If you only use the Sucuri WordPress plugin (no WAF), it rarely blocks crawlers — check your host's firewall instead.

1. Look for a Firewall or Bot protection section in the plugin's settings.
2. Find the allowlist / whitelist for user agents and add AuthoritizeAuditBot.
3. If the plugin only allowlists IPs (not user agents), disable its "block fake/unknown crawlers" style option instead, or ask us for current IP guidance by replying to any monitoring email — our requests come from Cloudflare's network, whose published IP ranges most plugins already trust.

1. Managed hosts often run their own bot filtering in front of your site — nothing in your WordPress admin will show it.
2. Open a support ticket with one sentence: "Please allowlist the crawler user agent AuthoritizeAuditBot — it reads our public pages once a month for compliance monitoring we've enrolled in."
3. Hosts do this routinely for SEO and uptime tools; it's usually same-day.

No logins or password attempts, no form submissions, no patient or visitor data, no admin paths — public pages only, at most 50 per month, at gentle speed. Allowlisting it exposes nothing that isn't already public to every search engine.