Does blocking a folder via robots.txt kill the PageRank transfer to your strategic pages?

Why does blocking a folder cut off the incoming PageRank flow?

When you add a Disallow directive in your robots.txt to block an entire directory, Google can no longer access the content of those pages. The bot stops at the door.

The problem is that Google does not recognize internal redirects or outgoing links from these blocked pages. If an external backlink points to /blog-archive/article-123, and you block /blog-archive/, Google sees the incoming link but cannot follow the 301 redirect that you may have set up to /blog/article-123.

How does Google handle backlinks to blocked URLs?

Google considers these backlinks as orphan signals: it knows they exist, but it cannot leverage them to strengthen the authority of your active pages. The theoretical PageRank remains stuck at the entry.

Unlike a 404 or 410 page that Googlebot can crawl and identify redirects from, a URL blocked by robots.txt remains a black box. No content discovery, no juice transmission.

What's the difference with an indexed but empty or removed page?

If you leave a page accessible but empty (or 404), Google can at least crawl the page, detect a possible 301 redirect, and follow the trail to the new target URL. The PageRank transfer occurs normally then.

With robots.txt, you cut off any exploration. Google never sees the HTTP response code, nor the redirect headers. It's like denying access to a warehouse: delivery trucks (backlinks) arrive, but no one knows where to unload the goods.

• Blocking with robots.txt = Google does not crawl, does not see redirects, does not transfer the PageRank from incoming backlinks
• 404/410 crawlable = Google crawls, detects the disappearance, can follow a possible 301 redirect and transfer authority
• Direct 301 redirect = Google follows the redirect, transfers PageRank to the new target URL without major loss
• Never block a folder that receives quality backlinks without first verifying that no redirects need to be crawled
• Use robots.txt only to protect sensitive content, internal duplicate or unnecessary crawl budget — never to manage migrations or URL restructurings

Is this statement consistent with field observations?

Yes, and it's an official confirmation of what many SEO practitioners have already been doing for years. Blocking a complete directory with robots.txt to "clean up" a site is a classic mistake among beginners or sloppy SEO audits.

I have seen sites lose 30 to 40% of their organic traffic after blocking /blog/ or /resources/ because a developer wanted to "hide outdated content". The backlinks were still there, but Google could no longer leverage them. [To be verified]: Google does not publish figures on the percentage of PageRank lost in this scenario, but the impact is practically measurable.

What nuances should be added to this rule?

The indirect transfer that Mueller talks about concerns internal links from blocked pages to active pages. If you block /old-site/ which contained links to /new-site/, Google never sees these internal links and cannot distribute PageRank accordingly.

But be careful: blocking in robots.txt does not always prevent indexing. Google can index a blocked URL if it receives backlinks, even without crawling the content — you will then see an empty snippet in the SERPs. This is counterproductive: the URL clutters the index without adding value, and the PageRank remains stuck.

In what cases does robots.txt remain relevant for blocking a folder?

Blocking with robots.txt makes sense to protect technical content: /wp-admin/, /cgi-bin/, /scripts/, /tmp/. These folders normally do not receive any external backlinks and should not appear in the index.

Also useful to save crawl budget on infinitely paginated pages, redundant facet filters, or automatically generated parameterized URLs. But in these cases, always check that no backlinks point to these paths before blocking.

What should you do if you've already blocked a folder that receives backlinks?

Immediately remove the Disallow directive from the robots.txt file for that directory. Google will then be able to crawl the pages, discover your 301 redirects, and transfer PageRank to the new target URLs.

Check in Google Search Console (Coverage or Indexed Pages section) if blocked URLs appear with the status "Blocked by robots.txt". If so, unblock and submit a new validation to accelerate the re-crawl.

How to audit your robots.txt to identify risky blockages?

Export your backlink profile from Ahrefs, Majestic, or SEMrush. Cross-reference these URLs with the blocked paths in your robots.txt. Any overlap is a red flag.

Use a Python script or spreadsheet to spot patterns: if /resources/ is blocked but receives 150 backlinks from referring domains, you are likely losing PageRank. The same logic applies to old blog URLs, archived landing pages, or past campaigns.

What strategy should be adopted to restructure a site without losing SEO juice?

Never block a folder before you have implemented clean 301 redirects and verified that they work. Allow Google to crawl these redirects for at least 3 to 6 months so it can transfer PageRank.

If you must absolutely remove content from the index, use the noindex tag instead of robots.txt: Google will be able to crawl, see the directive, and properly de-index without cutting off the link flow. Once de-indexed, you may consider blocking if crawl budget is a concern.

• Audit robots.txt and cross-reference with backlink profile to identify problematic blockages
• Remove any Disallow directive on folders receiving quality external links
• Implement permanent 301 redirects before any URL restructuring or migration
• Keep old URLs accessible and crawlable for at least 6 months after migration
• Use noindex instead of robots.txt to remove content from the index without cutting off PageRank transfer
• Monitor Google Search Console to detect blocked URLs that still appear in the index