Skip to main content

Scan Issues

Having trouble with scans? This guide covers common scan problems and solutions.

Scans Won't Start​

"Site not verified"​

You must verify site ownership before scanning.

Solution: Complete DNS verification.

"Scan limit reached"​

You've used all scans for this billing period.

Solutions:

  • Wait for your billing cycle to reset
  • Upgrade to a plan with more scans
  • Check usage in Settings → Billing

"Site not accessible"​

Auditoro couldn't reach your site.

Solutions:

  1. Verify the site loads in a browser
  2. Check if the site is behind a firewall
  3. Ensure Auditoro isn't being blocked (see below)

Scans Not Completing​

Stuck at "Discovering pages"​

Possible causes:

  • Sitemap is very large
  • Sitemap has errors
  • Site is slow to respond

Solutions:

  1. Verify your sitemap is valid
  2. Check your server's response time
  3. Wait—large sites take longer

Stuck at a specific percentage​

Possible causes:

  • Some pages are slow to load
  • Server is rate limiting
  • Network issues

Solutions:

  1. Check if your site is under heavy load
  2. Review server access logs
  3. Wait and let it complete

Scans timing out​

Possible causes:

  • Very large site (thousands of pages)
  • Slow server response times
  • Complex pages with heavy JavaScript

Solutions:

  1. Ensure your server is healthy
  2. Check for rate limiting
  3. Contact support for large sites

Scans Completing With Errors​

"Failed to fetch pages"​

Some pages couldn't be retrieved.

Possible causes:

  • Pages require authentication
  • Pages behind IP restrictions
  • Server errors (500s)

Solutions:

  1. Check if pages work in incognito mode
  2. Review server logs for errors
  3. Ensure no IP blocking

"Sitemap errors"​

Problems with your sitemap.xml.

Possible causes:

  • Invalid XML syntax
  • URLs returning errors
  • Incorrect sitemap location

Solutions:

  1. Validate your sitemap at Google Search Console
  2. Fix any XML errors
  3. Update sitemap location in site settings

Missing Pages​

Pages not being scanned​

Possible causes:

  • Pages not in sitemap
  • Pages blocked by robots.txt
  • Pages require authentication

Solutions:

  1. Add pages to your sitemap
  2. Check robots.txt directives
  3. Ensure public access

Robots.txt blocking​

If robots.txt is blocking Auditoro:

Allow Auditoro specifically:

User-agent: *
Disallow: /private/

User-agent: Auditoro
Allow: /

Slow Scans​

Why scans take time​

Factors affecting scan duration:

  • Number of pages
  • Server response time
  • Check complexity (browser-based checks take longer)
  • Rate limiting

Improving scan speed​

On your end:

  1. Improve server response times
  2. Don't rate limit the Auditoro crawler
  3. Keep sitemap up to date

Note: Auditoro intentionally paces requests to avoid overwhelming your server.

Auditoro Being Blocked​

Signs of blocking​

  • Scans fail or return empty
  • Only partial pages scanned
  • "Failed to fetch" errors

Unblock Auditoro​

Identify our crawler:

User-agent: Auditoro

Whitelist in firewall: Contact support for IP ranges if your firewall blocks by IP.

Check WAF/CDN settings:

  • Cloudflare: Create a firewall rule to allow
  • AWS WAF: Add allow rule
  • Other WAFs: Whitelist by user-agent

Inconsistent Results​

Results vary between scans​

Possible causes:

  • A/B testing on your site
  • Dynamic content
  • CDN caching issues
  • Load balancing to different servers

Solutions:

  1. Disable A/B tests during scans if possible
  2. Check if different servers return different content
  3. Review CDN cache settings

Getting Help​

If scan issues persist:

  1. Check the basics:

    • Site accessible in browser
    • Sitemap valid
    • Not blocked by firewall

  2. Contact support with:

    • Your site URL
    • Description of the issue
    • When the problem started
    • Any recent server/DNS changes