Does your robots.txt point search engines to your sitemap?

This search visibility check flags a sitemap that exists but is not named in your robots.txt file. Search engines that only read robots.txt may never find it.

What does this check look at?

It looks at whether your robots.txt file names the sitemap your site has. Google says a Sitemap line anywhere in robots.txt is enough for it to find your sitemap the next time it crawls that file. A Pulse also reads your sitemap, the list of pages you give search engines.

Pulse and Deep scans both run it.

What does a result mean?

It is about search visibility only and never affects your grade. A clean result means nothing was found in what the scan read. It does not prove the problem is absent from parts the scan never sees.

How serious is a finding?

This is information only. It claims no weakness, so it carries no verdict, and you decide whether anything should change. Confidence starts high, because a response from your site shows the thing itself. The report lists what to fix by how directly someone could use it, not by the severity label. Sitemap cards are not security issues and never change your grade.

Fix it with your AI

It is one line, with the full https address of the sitemap.

Add a Sitemap line to my robots.txt that gives the full https address of my sitemap (or sitemap index). If my framework generates robots.txt, change the generator rather than a static file. Show me the final robots.txt.

How to check

Say Atlas, our example app at atlas.example, serves a sitemap at the usual address but its robots.txt never mentions it. The check adds one information card.

Run a Pulse scan from your Lockpick account to see it for your site. Pulse or Deep explains what each scan reads, and the full list of checks shows the rest.