Do blocked redirects by robots.txt really break your links?

Why does Google emphasize the visibility of redirects?

A HTTP redirect functions like a road sign: it tells the browser (and bot) that a resource has changed its address. Google follows these signs, whether they pass through URLs with parameters or not.

The problem arises when the robots.txt file blocks the intermediate path. Googlebot stops dead: it cannot see where the redirect leads, so it cannot pass on the link equity. It's like putting opaque tape over the sign.

What’s the difference between a visible redirect and a blocked redirect?

A visible redirect allows Googlebot to follow the entire chain: URL A → URL B → URL C. The bot registers the final destination and transfers the accumulated PageRank.

A blocked redirect cuts the chain in half. If robots.txt disallows access to the intermediate URL, Googlebot gives up. The link remains technically functional for humans, but Google treats it as a dead end. You lose the SEO benefit of the incoming link.

Do URL parameters pose a particular risk?

URL parameters (such as ?utm_source=X or ?ref=Y) do not inherently bother Google. The bot follows these links without issue. The risk lies elsewhere: in poorly configured tracking systems that redirect through third-party domains or blocked subfolders.

For instance, a partner link pointing to example.com/track?dest=pageZ then redirects to the final /pageZ. If /track/ is blocked in robots.txt to avoid crawling thousands of parameterized variations, Google stops before reaching /pageZ. The result: zero value transmitted.

• An inaccessible redirect to Googlebot equals a dead link from an SEO perspective, even if it works for human visitors.
• URL parameters are only problematic if intermediate paths are blocked by robots.txt.
• Check the complete chain of your redirects: every jump must remain crawlable.
• Avoid blocking entire subdirectories if you are routing strategic redirects through them.
• 301/302 redirects pass PageRank equivalently according to Google, as long as they are followed.

Is this statement consistent with real-world observations?

Yes, and it is even a frequent source of unexplained link losses. Audits regularly reveal redirects that go through blocked subfolders by robots.txt to prevent content duplication or wasting crawl budget.

The classic case: an e-commerce site blocks /cart/, /checkout/, /tracking/ in robots.txt. A partner points to a tracking URL that then redirects to a product page. Google never follows the redirect. The partner thinks they are passing juice, but the site receives none. [To be verified]: how many of your backlinks go through blocked intermediate paths? Few tools automatically flag this.

In what contexts does this rule pose the most problems?

Affiliate programs and marketing campaigns are the first ones affected. Links often pass through tracking URLs with parameters (utm, fbclid, gclid) and then redirect. If the redirect path is blocked, you lose the SEO benefit of the external link.

Poorly planned site migrations also create drama. The old domain redirects to the new one through an intermediary server or a CDN with some routes blocked. Redirects work for users, but Google does not follow them. You think you have transferred your authority, but in reality, you have buried it.

What nuances should be added to this statement?

Google does not specify how many redirect jumps it accepts before giving up. Real-world observations suggest that 3 to 5 jumps are tolerated, but beyond that, transmission becomes random. Even without robots.txt blocking, a chain that is too long dilutes the equity transmitted.

Another point: Google talks about “counting” links, but does not detail whether a blocked redirect actively harms (negative signal) or simply cancels the benefit (neutral signal). In practice, no observable difference: the link does not count, period. But this remains a gray area not officially documented anywhere.

How can you check that your redirects are visible to Google?

First step: audit your robots.txt. List all blocked paths (Disallow), then identify the URLs on your site that redirect. Cross-reference the two lists. If a redirect goes through a blocked path, you have a problem.

Use the URL Inspection Tool in Google Search Console. Paste the source URL of a redirect and check if Google can follow it. If the status indicates “Blocked by robots.txt,” you know the link transmits nothing. Also test the intermediate URLs in a redirect chain.

What specific actions should you take to correct this issue?

If you are blocking a subdirectory that contains strategic redirects, refine your robots.txt rules. Instead of blocking /tracking/ entirely, only block the URLs that should not be crawled (e.g., /tracking/*?session=*) while allowing permanent redirects.

For affiliate or partner links, prefer direct redirects from your main domain, without going through blocked subdomains or paths. If you must use tracking URLs, ensure they remain accessible to Googlebot or that the final redirect is encoded in a visible canonical attribute.

What mistakes should you absolutely avoid?

Never block a path in robots.txt without checking if it serves as a pass-through point for redirects. Standard SEO audit tools do not automatically detect this case: you need to manually cross-reference robots.txt and the mapping of redirects.

Avoid unnecessary redirect chains. Each additional jump increases the risk that a link is blocked. Always redirect directly from A to Z, not from A to B to C to Z. Google might give up midway, even if no path is blocked.

• Audit your robots.txt file and list all blocked paths (Disallow).
• Map your active redirects (301, 302, 307) and ensure none cross a blocked path.
• Test redirect URLs with the URL Inspection Tool in Google Search Console.
• Simplify redirect chains: go directly from A to Z without intermediate steps.
• Explicitly allow tracking or affiliate paths in robots.txt if they serve as relays for backlinks.
• Check incoming backlinks in Search Console: how many point to redirecting URLs? Manually follow the chain.