Crawler safety
Public HTTP/HTTPS only, standard ports, private and loopback address blocking, redirect limits, timeouts and response-size caps.
Security and privacy
Designed to inspect public signals without becoming a new risk.
Access is scoped, tenant boundaries are enforced server-side and crawler requests are deliberately constrained.
Account security
Strong password derivation, HTTP-only sessions, origin checks, brute-force controls and verified-email workflows.
Tenant isolation
Organisation filters apply to every protected website query. Cross-tenant attempts fail securely and create reviewable events.
Data minimisation
Public scans retain limited public evidence for a configurable period. Passwords, tokens and authentication headers are never logged.
Operational evidence
Audit events record meaningful account, website and crawl actions without storing secrets.
Honest boundaries
Patch 1 does not accept credentials for private website areas and does not perform privileged fixes.
Important
eeziIndex can improve technical indexing readiness. It cannot force or guarantee crawling, indexing, search visibility, traffic or ranking.