Does the engine fix this itself?

Yes. The corrected artefact is generated and queued for your approval, then pushed and re-fetched to confirm it went live.

Check library · Technical and crawl

No robots.txt

lowrobots_missingfix written automatically

Why it matters

Without one, every crawler guesses, and you lose the place to declare your sitemap.

What to do about it

Publish a robots.txt that allows what should be crawled and names the sitemap.

The engine generates this fix itself using the generate_robots strategy. It arrives in your queue as a complete artefact, because an incomplete fix never reaches the queue, and once you approve it the change is pushed and the page re-fetched to confirm it is live.

How it is weighted

These are the values the scoring actually uses, not a description of them. Priority is derived from all three rather than chosen, which is why a high-impact, low-effort finding surfaces above a severe one that would take a quarter to fix.

Severity: low
Impact: 25% of the weight this category can carry
Effort: 10%, where 100% is a project rather than a change
Confidence: 80% that a hit is a real problem rather than a pattern we misread
Area: Technical and crawl

Other checks in Technical and crawl

criticalPage is blocked from indexingpage_noindexneeds a decision criticalServer errorpage_5xxneeds a decision criticalRedirect loopredirect_loopneeds a decision criticalrobots.txt blocks a page that should rankrobots_blocks_importantneeds a decision criticalPage is not served over HTTPSno_httpsneeds a decision highBroken internal linkpage_404_linkedfix written highNo XML sitemap foundno_sitemapfix written highHTTPS page loads insecure resourcesmixed_contentneeds a decision

Check your own site for this

The whole catalogue over a real crawl, in about four minutes, in your browser. No account and no card.

See what we would fix this week Back to the library