Most scan failures come from reachability, route configuration, login validation, or site protections. The fastest path is to check the basics, then attach the scan to a support ticket.
Site unreachable
Confirm the URL opens in a normal browser without a VPN or private network. PageLens workers need to reach the site from the public internet.
Too few pages found
If the crawler misses important pages, use URL list mode for those routes. Crawlers can miss pages hidden behind search, client-only menus, forms, or links that only appear after interaction.
Login failed
For authenticated scans, check that:
- the test account is active
- the password has not changed
- selectors still match the login form
- allowed origins and path prefixes include the target route
- denied patterns are not blocking the route
Re-run auth profile validation after changing any of these settings.
Blocking and bot protection
Some sites block automated browsers or unknown regions. If your site has bot protection, allow the test route where possible or use a staging environment designed for automation.
Report looks incomplete
Check the scan mode, page limit, viewport choice, and URL list. A desktop-only scan will not show mobile-only issues, and a three-page scan will not cover a large site.
What to send support
Open a support ticket and attach the scan. Include the URL you expected PageLens to reach, what happened instead, whether the route needs login, and any recent site changes.