# Does your sitemap list pages your robots.txt blocks?

By Mark Kashef, founder of Lockpick. Published 2026-10-08, updated 2026-10-08.

This search visibility check flags sitemap pages that robots.txt tells search engines to skip. One of the two lists needs changing.

This search visibility check flags pages your sitemap asks search engines to visit while your robots.txt tells them to stay away. Search engines report this as an error.

## What does this check look at?

It looks at whether your sitemap lists pages that your robots.txt file tells search engines to skip. Google notes that robots.txt is not a mechanism for keeping a web page out of Google. Listed pages are never requested. 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?

| What the report shows | What it means | What to do |
| --- | --- | --- |
| Info finding | Some sitemap pages match a Disallow rule. | Remove them from the sitemap, or lift the rule if they belong in search. |

Listed pages are not requested, and it is about search visibility only. 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.

## Which standards does it relate to?

None. It is about search visibility, so no security standard applies, and it never moves your grade.

## Fix it with your AI

Decide for each page whether it belongs in search, then make both lists agree.

:::fix-prompt any
My sitemap lists pages that my robots.txt disallows: [paste the problem from the report]. For each one, ask me whether it should appear in search. If not, remove it from the sitemap generator. If it should, remove or narrow the Disallow rule. If a page must stay out of search entirely, use a noindex robots meta tag instead of robots.txt. Show me both files afterwards.
:::

## How to check

Say Atlas, our example app at `atlas.example`, blocks its pricing experiments folder in robots.txt but its sitemap still lists them. The check adds one card.

Run a Pulse scan from your Lockpick account to see it for your site. [Pulse or Deep](/docs/get-started/pulse-or-deep) explains what each scan reads, and the [full list of checks](/checks) shows the rest.

## Questions people ask

### Does blocking a page in robots.txt keep it out of search?

Not reliably. A blocked page can still be listed if other sites link to it. A noindex tag is the way to keep it out.

### Is this a security issue?

No. It is about search visibility and never changes your grade.

## Sources

- [How we rate findings](https://www.lockpick.app/docs/security/how-we-rate-findings), Lockpick docs, read on 2026-10-07
- [Read your report](https://www.lockpick.app/docs/get-started/read-your-report), Lockpick docs, read on 2026-10-07
- [Robots.txt introduction and guide](https://developers.google.com/search/docs/crawling-indexing/robots/intro), Google Search Central, read on 2026-10-07