Let SEOScanPRO Scan Your Site

What to allow when a firewall or bot protection stops an audit.

Why an Audit Can Be Blocked

Many hosts run a firewall or bot protection in front of every website. It is there to stop attacks and scrapers, and it decides who gets through by looking at where a request comes from and how it behaves. An audit is automated, so some of these systems treat it as a bot and stop it before the page loads.

When that happens, the audit screen tells you one of these:

  • The site dropped the connection partway through.
  • The site refused the scanner (HTTP 403 or 503).
  • This scan was blocked, because the site answered with a security check page instead of the real site.

When a site drops the connection or shows a security check, the scanner already tries again once with a real browser, and many sites let that through. If the audit still fails, follow the steps below.

What the Scanner Does on Your Site

  • It reads your public pages the same way a visitor's browser does.
  • It never logs in, never submits a form and never changes anything on the site.
  • It checks the files search engines read, such as robots.txt and your XML sitemap.
  • Speed measurements come from Google PageSpeed Insights, which Google runs from its own servers.

The Address to Allow

Every SEOScanPRO scan request comes from one IP address. Allow this address and the scanner can reach your pages:

SEOScanPRO scanner IP address

64.138.203.5

Allow it by address, not by browser name. The scanner identifies itself as an ordinary browser, so there is no separate bot name for a firewall to match on.

Where to Add It

  • Cloudflare: add the address to your IP Access Rules with the action Allow.
  • Wordfence (WordPress): add it to the list of allowlisted IP addresses in the firewall options.
  • Sucuri: add it to the allowlisted IP addresses in the firewall's access control settings.
  • Managed hosting (SiteGround, WP Engine, Kinsta, GoDaddy and similar): the host runs the bot protection, so ask their support team to allowlist the address. The message below says everything they need.

Message to Send Your Host

Copy this into a support ticket or chat with your hosting company:

Message for your host

Please allowlist the IP address 64.138.203.5 in the firewall and bot protection for my website. It is the SEOScanPRO scanner, which I use to audit my own site. It reads public pages the way a visitor does, does not log in or submit forms, and changes nothing. Right now its requests are being blocked or the connection is being dropped before the page loads.

Then Rerun the Audit

Once the address is allowed, open the audit and run it again. If it is still blocked, send us the audit link from the Support page and we will look at what the site is sending back.