## **🔍 Understanding the Error**

When the Onpage Audit tool returns the message **"Auditing URL failed - Status Code: 200"**, it can feel confusing — HTTP 200 normally means a page loaded successfully. However, this error does not mean the page is broken. It means our audit crawler received a 200 response but was **blocked from reading the page content** it needs to complete the audit.

Common reasons this happens include:

- The website blocks automated crawlers or bots via server-side rules
- A firewall, WAF (Web Application Firewall), or CDN (e.g. Cloudflare) is intercepting the request
- The page requires JavaScript to render content before it becomes accessible
- Bot-detection scripts are serving a blank or restricted page to non-browser requests
- The server returns a 200 status but redirects internally to a login wall or CAPTCHA

## **✅ Steps to Resolve the Issue**

1. **Confirm the URL is publicly accessible.** Open the URL in an incognito or private browser window. If you are prompted to log in or see a CAPTCHA, the page is not publicly crawlable and the audit tool will not be able to access it.
2. **Check your firewall or CDN settings.** If your site uses Cloudflare, Sucuri, or a similar service, check whether bot protection or "Under Attack Mode" is enabled. These settings frequently block automated audit requests even when returning a 200 status code.
3. **Whitelist Search Atlas crawlers.** Ask your developer or hosting provider to allow requests from the Search Atlas crawler user-agent. Whitelisting our crawler ensures the audit tool can read page content without being intercepted.
4. **Check your robots.txt file.** Visit **yourdomain.com/robots.txt** and confirm the page or directory is not disallowed for all bots. A disallow rule can cause the crawler to receive a restricted response even with a 200 status.
5. **Test with a different URL on the same domain.** Try auditing another page on the same website. If other pages audit successfully, the issue is specific to that page's configuration rather than a platform-wide problem.
6. **Re-run the audit after making changes.** Once you have adjusted firewall rules or bot-detection settings, return to the Onpage Audit tool, enter the URL again, and run a fresh audit.

## **⚙️ How to Re-Run an Onpage Audit**

1. Navigate to the **Onpage Audit** tool within the platform.
2. Locate the project or enter the URL you want to audit.
3. Start a new audit for that URL.
4. Wait for the audit to complete and review the results.

## **💡 Tips to Prevent This Error**

- Always audit publicly accessible pages. Password-protected, staging, or members-only pages cannot be audited.
- If your site uses heavy JavaScript rendering, ensure the page content is accessible to non-browser crawlers.

If you need further assistance, open the chat widget in the bottom-right corner of the platform and type **human teammate** to be connected with a member of our team.