Kicked off /full-site-audit on a fairly big site (roughly 900 pages) and the progress bar has been sitting on 'crawling' for a long while — much longer than my smaller sites, which finish in a couple of minutes. Is it actually stuck and I should retry, or is it just slow on a site this size? Don't want to burn credits re-running if it's going to eventually complete. Screenshot of the stuck state if it helps.
Not stuck — genuinely slower, and this is expected on heavy sites. The crawl is polite by design (it doesn't hammer your server), so a 900-page site legitimately takes considerably longer than a 60-page one. On large sites the 'crawling' phase can run for a good while before it flips to analysis, and it will complete.
A couple of tips:
We do show a slowness caveat for heavy sites for exactly this reason. Let it run.
You were right — came back after lunch and it had completed, health score and all, no re-run needed. The 'close the tab, it saves to history' bit is the reassurance I needed. Maybe make that message more prominent on big crawls?
Good feedback — making the 'this is safe to leave, we'll save it' messaging more prominent during long crawls is a fair UX ask. Passing it to the product team. Glad it completed cleanly.
