Matan · Security · Exposure
Exposed files (Security)
Read-only probes for /.git, /.env and similar must not return content.
Pass condition in our engine: Common sensitive paths are not publicly readable.
This Security check is part of SEO-GEO scoring 3.0.0, last updated 2026-10-25. The number on this page is the developer scoring version. It is not an announcement that public release 3.0.0 is live. A free report shows the same pass condition for the pages it fetched.
1. Problem description
We request a short list of well-known sensitive paths. A 200 with a body is a critical finding. This is not a full content-discovery scan and never sends payloads.
2. Most common causes
- The site root is a git checkout.
- .env deployed into the web root.
- Directory listing on the server.
Test this check
We fetch only this URL (plus robots.txt / llms.txt at the domain root when the check needs them). We do not crawl the rest of the site like a full report.
3. How to fix it
- Deny those paths at nginx/Apache/IIS.
- Keep git and env files outside the public directory.
- Rotate secrets if .env was public.
Scoring rules for the scan of fetched pages are documented in methodology. Want every category at once? Generate a free report.
Get your free website audit
Enter a public URL. The scan reads up to 300 pages and returns an HTML report with scores for measured pillars and a recommendation for each finding. No sign-up required.