AutoSEO is engineered with security safeguards to protect target websites, prevent service abuse, and safeguard user data. This page outlines our technical security architecture and transparent system limitations.
1. Network & Crawling Security Controls
To prevent our crawler from being misused as an attack proxy or internal network scanner, AutoSEO enforces strict network controls:
Server-Side Request Forgery (SSRF) Protection
- IP Address Validation: Before fetching any requested target URL, AutoSEO resolves the domain DNS and validates the destination IP address.
- Blocked IP Ranges: Requests to loopback addresses (
127.0.0.1,localhost), private subnets (10.x.x.x,172.16.x.x,192.168.x.x), link-local addresses (169.254.x.x), and cloud provider metadata endpoints (169.254.169.254) are strictly blocked. - Redirect Chain Controls: Redirect targets are validated at every hop to prevent open-redirect SSRF bypasses.
Rate Limiting and Workload Budgets
- Per-Domain Rate Capping: Crawl requests are capped at 1 request per second per target domain to ensure zero impact on host performance.
- Bounded Crawl Limits: Runs are limited to 100 HTML pages maximum.
- Byte and Timeout Caps: Page fetches enforce short request timeouts and byte size limits to prevent memory exhaustion attacks.
2. WordPress Connector Security Architecture
Connecting a WordPress website for automated repairs utilizes secure credential handling:
- Scoped Application Passwords: Connection pairing uses WordPress Application Passwords specifically created for AutoSEO. Your primary administrative login password is never requested or stored.
- Encrypted Short-Lived Grants: Granted access credentials are encrypted at rest using keys stored outside database tables.
- Minimal Field Access: The connector plugin limits write access strictly to title tag and meta description fields owned by the connector or Yoast SEO.
- Instant Revocation: Revoking the Application Password in the WordPress dashboard immediately terminates all connector access.
3. Data Isolation and Privacy Safeguards
- In-Memory Parsing: Page response bodies are processed in temporary server memory and discarded immediately. No page HTML, detailed audit logs, or PDF files are saved to central databases.
- Browser-Side Findings: Detailed finding inventories reside in your local browser tab session memory. Closing the browser tab clears all session data.
4. Known System Limitations
Website owners should be aware of technical limitations inherent to automated scanning:
- Static HTML Parsing: Crawlers parse static HTML responses. Content rendered exclusively via client-side JavaScript (e.g., single-page React apps) may not be fully evaluated.
- Firewall Restrictions: Websites protected by strict WAF rules (such as Cloudflare or AWS WAF) that block unrecognized user-agents may block audit fetches.
- 100-Page Boundary: Audits analyze up to 100 pages as a representative sample, not exhaustive coverage for enterprise sites.
Learn How It Works, review our Privacy Policy, or consult our Terms of Service.