Troubleshooting

Single-URL report failed or timed out

• Authentication wall — We cannot complete forms or MFA. Test in a private window while logged out, or use a public staging URL.
• Very slow responses — Heavy pages or overloaded hosts may time out. Try again off-peak or reduce server-side work on that URL.
• WAF / bot protection — Some firewalls block automated fetches. Temporarily allow our crawler User-Agent or whitelist our IPs (contact support for current ranges if needed).
• Wrong URL — Trailing slashes, www vs non-www, and redirects matter. Paste the exact URL users can open without logging in.

Monthly run oddities

Monthly automation runs once per billing period per website when your plan includes monthly reports. If a button is disabled:

• You may have already used this period’s run—wait for the next cycle or check the dashboard message.
• Free plan does not include monthly multi-page automation; use single-URL reports or upgrade to Basic or higher.
• A site stuck in an error state may need the same URL/access checks as single-URL scans for the pages in your crawl list.

robots.txt, sitemap, and “no pages”

If robots.txt disallows crawling important paths, we may see fewer (or no) pages than you expect. Ensure important URLs are allowed, your sitemap is reachable if you rely on it, and that canonical URLs are not accidentally blocking alternate entry points you care about.

Still stuck?

Use the in-app AI assistant on the report or contact page for a first pass, then contact support with the workspace name, URL, approximate time of the failure, and any error text shown in the UI—this saves a round trip.

Related: Understanding Your Report, Manually Generated Reports, Help & Guides.