‹ All documentation
Evidence reference
If robots.txt blocks Googlebot from fetching a page, Google cannot read robots meta directives located in that page's HTML.
SupportedSUPPORTEDclm_adcf15c6-4741-4d79-a7f4-a095516c206b
This is a stable reference page for one canonical claim in the Editory evidence base. It exists for traceability and citations; the curated documentation is the readable entry point.
Sources
- Block Search Indexing with noindex
Google Search Central Documentation · primary source · retrieved 2026-08-18
“If the page is blocked by a robots.txt file or the crawler can't access the page, the crawler will never see the noindex rule” — Important note on noindex effectiveness
- Robots Meta Tags Specifications
Google Search Central Documentation · primary source · retrieved 2026-08-18
“If a page is disallowed from crawling through the robots.txt file, then any information about indexing or serving rules will not be found” — Section on combining robots.txt rules with robots meta tags
- Robots.txt vs Noindex: Why Blocking Crawlers Does Not Remove Pages From Search
3V.org · retrieved 2026-08-18
“Because it never fetches the page, it never sees the noindex tag” — Explanation of the disallow/noindex conflict
- Robots.txt and Meta Robots: Complete SEO Reference
Digital Applied · retrieved 2026-08-18
“If robots.txt blocks the URL, Googlebot cannot fetch the page and will never see the meta noindex tag.” — line 35
Release: seo-geo-product-v0.3 · Phase Two freeze: P2-CORE300-FINAL-v1.0 · Generated: 2026-08-23T08:01:40Z