If your Site Audit crawl appears stuck (for example, 756 of 776 pages) or reports missing pages, this does not always indicate a bug.
In most cases, stalled or incomplete crawls are caused by:
Crawl configuration limits
Redirect-heavy pages
Server response delays
However, there are scenarios where an active Site Auditor issue may also affect crawl completion.
This article explains how to tell the difference.
🧱 Navigation Path
🧱 Navigation Path
Search Atlas → AI SEO → Site Audit → All Audits → View Audit
🧠 Common Reasons a Site Audit Gets Stuck
🧠 Common Reasons a Site Audit Gets Stuck
🔢 1. Crawl Limit Set Too High
If the Pages to Crawl limit is set too high, the crawler may slow down or stall.
This is especially common on sites with:
Heavy pages
Slow server response
Many redirects
🔁 2. Redirect-Heavy Pages
If the audit reports a specific number of redirect pages (for example, 20 redirect pages), the crawl may appear stuck while processing them.
Redirect chains increase crawl time and can delay completion.
⏱ 3. Temporary Processing Delays
Crawls do not always complete in strict numerical order.
It is normal for an audit to pause near the end while processing remaining URLs.
⚙️ How to Troubleshoot a Stuck Crawl
⚙️ How to Troubleshoot a Stuck Crawl
Step 1 — Lower the Crawl Limit
Open the affected audit
Go to Audit Settings
Locate Pages to Crawl
Reduce the limit to 200–500 pages
Save and rerun the audit
Smaller crawls help confirm whether page weight or redirects are causing delays.
Step 2 — Re-run the Audit
After lowering the crawl limit, restart the audit and monitor progress.
If the audit completes successfully at a lower limit, the issue is configuration-related.
🚨 When This May Be a System Issue
🚨 When This May Be a System Issue
If:
The crawl remains stuck across multiple runs
The crawl consistently stops at the same page count
You have already reduced the crawl limit
Other users are experiencing similar behavior
Then the issue may be related to an active Site Auditor incident.
In these cases, support may already be tracking the issue internally.
❓ FAQs
❓ FAQs
❓ Why does my audit stop at the same number every time?
This often indicates redirect-heavy pages or slow responses near the end of the crawl.
❓ Is this caused by my site configuration?
Usually yes, but not always. Lowering the crawl limit helps identify the cause.
❓ Should I keep rerunning the audit?
No. Repeated reruns without changing settings will not resolve the issue.
❓ Do I need to contact support?
Only if the crawl remains stuck after reducing the crawl limit and rerunning the audit.
Most stalled Site Audit crawls are caused by crawl limits or redirects and can be resolved by adjusting audit settings.
If the issue persists after troubleshooting, it may be related to a known Site Auditor issue and will be handled by the team.