A scan fails or looks empty when Amevia cannot fetch your public pages — not when the agent is misconfigured. Start with reachability, then robots rules, then per-URL errors.
Troubleshoot scans
- Open the connected domain in a private window — homepage must load without VPN-only access
- Finish website verification or install steps if Overview still shows them pending
- Fetch /robots.txt and confirm you are not disallowing the paths you need
- Open Scan and read errors for failed URLs — note 403, 404, timeout or redirect loops
- Fix the live site, then start a new scan from Scan or Overview
After partial success
- Publish successful imports in Knowledge even if some URLs failed
- Add manual FAQs for pages that cannot be crawled
- See Pages missing from a scan for one-off URL diagnosis
Infrastructure blockers
- Bot fight modes at the CDN may throttle crawlers — allowlist or relax for scan windows
- Very slow TTFB can timeout fetches — improve host response first
- Scan the correct website connection if you operate multiple domains