PageLens scans a site with a real browser, captures evidence, runs checks, and turns the result into a prioritized report. Start from Dashboard -> New scan or any "Run scan" call to action while signed in.
Pick the site
Enter the public URL you want to audit. If you enter example.com, PageLens normalizes it to https://example.com. Use the exact hostname you want reviewed, because www.example.com and app.example.com may behave differently.
Choose crawl or URL list
Use Crawl when PageLens should start at one URL and discover pages automatically. This is best for marketing sites, public documentation, and stores with normal links.
Use URL list when you know the exact pages to check. Paste one URL per line or separate URLs with commas. This is useful for launch checklists, pricing pages, checkout steps, or any site where important routes are hard to discover from links.
Choose pages and viewports
Your scan tier controls the maximum number of pages. The scan form shows the page limit before you submit.
Viewport choices control the device profile:
- Desktop only checks the laptop/monitor experience.
- Mobile only checks the phone layout, tap targets, menus, and responsive behaviour.
- Desktop + mobile renders every selected page in both profiles and can surface device-specific issues.
Choose a report preset
Presets change how the report is framed, not the underlying evidence. Pick one when you want the audit to answer a specific business question, such as pre-sales polish, launch readiness, conversion, trust, or a general product review.
After submission
New scans move through queued, crawling, reviewing, and complete states. You can leave the page while the worker runs. When the report is ready, open it from the dashboard or your scan list.
If a scan fails, open a support ticket and attach the scan so the team can inspect the run history.