PageLens AI checks a live site, captures evidence, runs browser-visible checks, and turns the result into a prioritised report. For the lowest-friction start, paste a public URL into the free check on the homepage. You do not need an account or card for that initial result.
Choose the right scan type
The current public offer has three steps:
- Free initial check: checks one public page and shows its score, category counts, up to three issue summaries and one complete example fix, without signup or a card.
- Quick Report — $1 one time: keeps the submitted URL and unlocks the complete one-page finding list, evidence, priorities and repair guidance.
- Full Report — $9 one time: adds PDF and Markdown exports plus one verification re-scan.
Choose the paid report only after the free result shows enough value for your situation. Neither public report is a subscription.
Existing account entitlements
Some existing customers have legacy account-plan allowances or Health Watch access. Those entitlements remain available in their signed-in account, but they are not the current public acquisition offer. The signed-in scan form identifies an included legacy run before submission so an existing customer is not charged twice.
Pick the site
Enter the public URL you want to audit. If you enter example.com, PageLens AI 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 AI 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 selected report controls the maximum number of rendered 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.
Existing customers with Health Watch use a focused recurring scan shape, currently capped at 5 pages per run, so PageLens AI can compare important signals consistently over time.
Choose scan location
PageLens AI runs scans from AWS in the selected region. The default is London (eu-west-2). If your site blocks AWS, data-center IPs, or traffic from a specific region, update your firewall, CDN, or WAF rules before starting the scan. See Allow AWS scan traffic.
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.
Site context matters
PageLens AI also looks at what kind of site it is reviewing. A personal photography portfolio, local gallery, blog, ecommerce catalogue and SaaS landing page should not receive the same generic action plan.
For example, a personal portfolio is judged more on owner identity, gallery structure, image SEO, copyright/licensing clarity, contact discoverability, mobile gallery usability and image-heavy performance. It should not be treated as defective just because it lacks a SaaS-style pricing page, comparison page or buyer FAQ.
Some technical signals, such as HSTS or other response headers, may be controlled by your host, CDN or managed WordPress provider. PageLens AI still reports them because they affect browser security, but the suggested next step may be to ask the provider or document the item as an accepted risk/trade-off.
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.
Decide what to fix, accept, or defer
Not every real finding should be removed immediately. A booking widget, analytics tag, live chat tool, or conversion-critical embed may be worth keeping even when it adds performance, privacy, or reliability trade-offs.
In the report, open a finding and use Accept, defer, or document this finding to record the owner decision:
- Accepted risk when the risk is known and acceptable for now.
- Intentional trade-off when the implementation supports a business goal.
- Won't fix now when the item belongs in the backlog instead of the current repair pass.
- Acknowledged when the team has reviewed it but has not picked a remediation path yet.
These decisions do not change the technical score and they do not hide the finding. They move the item out of the unresolved action plan and carry the context into matching future scans, including manual follow-up scans and Health Watch scans.
After you fix issues, use the Full Report's included verification re-scan to confirm the findings disappear. Existing customers with Health Watch can also continue watching for regressions between deeper audits.
If a scan fails, open a support ticket and attach the scan so the team can inspect the run history.