Technical Issue

robots.txt not discovered

The scan could not fetch /robots.txt with an HTTP 200 response.

Quick win: Publish /robots.txt on the primary host.

Run free scan Create account View Pro pricing All issue guides

Plan coverage for this workflow

Free includes SEO checks, crawl health, and WordPress security posture visibility. Pro unlocks full WordPress vulnerability intelligence, weekly vulnerability monitoring, and project-level security history.

Run free scan Compare Free vs Pro

Why it matters

Missing robots.txt removes a simple crawl-control and sitemap-discovery mechanism.

How to fix

Publish /robots.txt on the primary host.
Include clear crawl directives and at least one sitemap URL.
Keep robots output stable across environments.

Related issue guides

robots sitemap inconsistency
Missing sitemap discovery

Next step: run a fresh scan for current issue counts, then triage fixes in order. You can also browse by category in SEO checks and WordPress checks.