Everything prospects, builders and clients usually ask before running PageLens AI: what gets scanned, what it costs, what the report includes, and how private scan data is handled.
How crawls, scan locations, viewports, JavaScript rendering and logged-in routes work.
Agentic journey reports, safe actions, limitations and beta boundaries.
One-off scans, QA Audit, page limits, Launch Pack and optional monitoring.
What is included, how views work and how teams use the output.
How crawls, scan locations, viewports, JavaScript rendering and logged-in routes work.
PageLens AI uses real browser automation to visit your site, capture optimised screenshots, inspect rendered HTML, and read HTTP headers. The report combines deterministic checks with AI review so you get practical findings across UX, SEO, accessibility, performance, content, security, tracking, trust and AI Search readiness.
Most scans complete quickly. Larger sites and scans that include both desktop and mobile take longer, but you can leave the tab and PageLens AI will email you when the report is ready.
You can run scans from AWS London, Frankfurt, Virginia, Oregon or Sydney. Choose the scan location when starting a one-off scan or subscription monitor. This helps when your site, CDN, firewall or bot-protection rules behave differently by region.
Data handling, authenticated scans, private access and retention.
Yes. Choose Desktop, Mobile or Both when starting a scan. Both viewports cost twice the single-viewport tier because every URL is rendered twice with separate browser contexts, screenshots and analysis.
Yes. Authenticated scans use verified-domain auth profiles, scoped test credentials, allowed route rules and denied route rules. You validate the login flow before scanning, and authenticated artifacts stay private by default.
Yes. PageLens AI runs pages in headless Chrome, so Next.js, React, Vue, Webflow, Framer, Shopify themes and other JavaScript-rendered sites can be reviewed after rendering.
You can retry failed scans. If PageLens AI genuinely cannot access the site and the scan cannot complete, contact support and we will help or refund the scan.
Agentic journey reports, safe actions, limitations and beta boundaries.
QA Audit is an agentic PageLens AI scan for public production or staging apps. Instead of only listing page findings, it safely explores the site like a first-time user, records the journey, flags broken or risky interactions, and produces a flow-focused report with design critique and recommended next tests.
QA Audit avoids committing actions such as signup, purchase, payment, booking, contact form submission, file upload/download, destructive changes and account changes. It can click navigation, open menus, follow links and type harmless values into search or filter-style inputs.
No. QA Audit can use a validated auth profile for scoped post-login routes, but it cannot complete SSO, CAPTCHA, MFA, passkey, magic-link or other human-verification flows. Those should be tested manually or with a dedicated staging bypass.
One-off scans, QA Audit, page limits, Launch Pack and optional monitoring.
No. Launch Scan, Launch Pack and Full Site Scan are one-off purchases. Weekly monitoring is optional for verified domains when you want PageLens AI to rescan regularly and flag regressions.
Yes. The $1 Launch Scan audits up to 3 pages and is designed for landing pages, homepages and small launches. It is not a trial that turns into a subscription.
Page limits are caps, not quotas. PageLens AI starts from the URL you provide and follows internal links until it runs out of reachable pages or hits the tier limit. If your site is smaller than the cap, you still receive the full report for the tier you selected.
What is included, how views work and how teams use the output.
A report includes an executive summary, health score, prioritized findings, impact and effort labels, page screenshots, persona reviews, security headers, email security checks, cookie and privacy signals, AI Answer Engine readiness checks, a glossary and a downloadable PDF.
Story turns the most important issues into a stakeholder-friendly narrative. Quick Wins maps impact against effort so you can plan fixes quickly. All Findings gives engineers the filterable inventory with rule IDs, evidence and suggested fixes.
Yes. Findings include effort labels such as Quick, Moderate or Involved. That lets you sort by impact and effort instead of treating every issue as equally urgent.
Data handling, authenticated scans, private access and retention.
Public scans crawl public pages only. Authenticated scans require verified-domain profiles and scoped test credentials. Screenshots and HTML are attached to the scan and served through private report access, not exposed as public files.
Screenshots are retained for a limited period after scans complete, then automatically deleted from blob storage. Findings, summaries, scores and metadata remain available so reports continue to render even after image cleanup.
Readiness for answer engines, citations and AEO-style content.
AI Search readiness checks whether answer engines can crawl, understand, summarize and cite your site. PageLens AI looks at crawl access, answerable content, entity clarity, structured data, citation trust and comparison-friendly content.
No. PageLens AI does not query ChatGPT, Gemini, Perplexity or AI Overviews for rankings. It audits the website conditions that make those systems more likely to understand and cite you.
Yes. Choose Scan authenticated app routes, select a passing auth profile, and provide scoped post-login URLs. QA Audit will log in with that profile, stay inside the allowed route scope, and continue to avoid committing or destructive actions.
Yes. Paid reports include a private share link, and you can download a PDF for stakeholders, clients or your build team.
Yes. Choose a lens such as Pre-launch, Conversion, Investor, Brand polish or AI Search readiness. The report voice, finding priority and persona ordering adapt to that use case.