What pSEO Guard sends — and what stays local
Most page-plan auditing happens in your browser. Existing Site Guard is the exception: to compare your plan with a live site, it has to request public pages from the site you choose.
Last updated
Your page plan stays in your browser
The current CSV audit runs locally in your browser. You do not need to upload the page plan to pSEO Guard for the core audit workflow.
When you scan an existing site
Existing Site Guard sends requests to the public website you ask it to check, then compares the pages it can retrieve with your proposed page set. The scan is deliberately limited so it does not behave like an unrestricted crawler.
- It follows robots.txt.
- Redirects must stay on the site you asked to scan.
- Request volume and response size are capped.
What the scanner will not access
The scan service is restricted to ordinary public web destinations. It rejects private or reserved network addresses, non-web protocols, embedded credentials and unsupported ports.
What a successful scan does not guarantee
A scan is not a security certification, and it only describes the pages it could safely retrieve and compare. pSEO Guard makes those coverage limits visible rather than turning missing evidence into a clean result.
- A clean scan result only describes the pages the scanner could retrieve and compare.
- Coverage limits are reported separately from audit findings.
Next action
Use the rule reference when a page needs a decision, or continue through the Docs in order.