Frequently asked questions
The questions we hear most, answered without hedging.
Frequently asked questions
How do I get access?
Page Lookout is open by invitation. Request an invitation through the contact form and we will get back to you. Already invited? Sign in at https://platform.pagelookout.com/sign-in.
What exactly does Page Lookout scan?
Publicly reachable pages on the sites you add to your organization. The modules run against them: security baseline (HTTPS and redirects, the TLS handshake and certificate expiry, security headers, server version disclosure, cookie attributes, mixed content), performance (Lighthouse, on a fixed list of up to 20 pages per site that you can edit), accessibility, technical SEO, cookie and consent observation, visual changes and AI search.
Is this uptime monitoring?
No. We do not continuously check whether your site responds and we do not send outage alarms. We analyse the technical quality of pages at scan time, whether you start the scan by hand or leave it to a schedule.
Will I get a legal assessment or a certificate?
No. The platform describes what it observed technically and recommends changes. We do not issue legal opinions or documents attesting to the legal status of a site. Drawing the conclusions is up to you and your advisers.
How does the scanner treat my site?
It identifies itself with a User-Agent that contains PageLookout, works within a bounded request budget at a limited rate, only visits URLs within the registered site, and signs in to nothing. The rate, the URL limit and the crawl depth are yours to set in the site scan policy. How to recognize the scanner and how to block it: https://pagelookout.com/bot.
How do you decide which URLs to check?
A scan starts from the seed URLs you give us, reads sitemap.xml if the site publishes one, and crawls onward from there up to the crawl depth and URL limit in your scan policy. We treat robots.txt as a signal from the site owner and take it into account. robots.txt and sitemap.xml are themselves subjects of findings in the technical SEO module.
Do you scan pages behind a login?
No. The scanner does not accept or store credentials to your systems. We analyse what is publicly reachable. We also never request private addresses or resources on internal networks.
How long do you keep scan data?
Findings and their evidence are kept in the site history so consecutive scans can be compared. Raw tool output is preserved as artifacts. Final retention periods and deletion rules are set out in the contract and the privacy policy.
Where does the platform run and where is the data?
The platform runs on Google Cloud in the EU (europe-west1), in Belgium.
Can I keep many sites in one place?
Yes, that is the core scenario. An organization holds many sites, each with its own scan policy: the set of modules, the URL limit, the crawl depth, the request rate and the schedule. Admin and member roles keep team access tidy, and tags and optional access groups help you group sites and limit who sees which.
Can scans run on a recurring schedule?
Yes. On every plan you can scan daily, weekly or on demand, within the monthly page-scan allowance of the plan. You can also start a scan by hand at any time. When a scan finishes, your alert rules can e-mail the organization admins and a signed webhook can call your own endpoint, and the same results are available through the API.