Audit incomplete, slow or empty
Why an audit finds too few pages, stops early, shows no score or takes a long time, and the crawl settings that fix each case.
Only one or a few pages were crawled
- Links are added by JavaScript. Turn on JavaScript rendering.
- The start URL redirects to another domain or subdomain. Start from the final URL, or tick Include subdomains.
- robots.txt blocks the crawler. Check the Blocked count in URL health.
- Maximum click depth is set low. Set it back to Unlimited.
No score is shown
No page could be read. Every request failed, timed out or was rate limited. Look at the first URL in Pages: a fetch error usually means a firewall, bot protection or SSL problem. See About SiteAuditLintBot for allowing the crawler.
Many pages say rate limited
The host limits request speed. Set Parallel requests to 1 and Delay to 1 second. See Rate limiting and HTTP 429.
The crawl stopped at a round number
That is the edition's page limit or your Maximum pages setting. The banner says how many URLs were found but not checked.
The end of the audit is slow
After the last page, outbound links are checked, then site-wide checks run. Since 0.6.1 the status line shows each step and a 3,000-page audit finishes in about 40 seconds instead of two minutes. The external link check stops after 3 minutes at most. To skip it, untick Check external links.
Pages found by sitemap only
Pages listed in the XML sitemap but not linked from any crawled page are reported as orphans. They are hard for crawlers and visitors to find; link to them from relevant pages.
Applies to SiteAud!tLint 0.6.1 and later. Current version 0.7.1.