Do 301 redirects really enforce the canonical URL to Google?

Why doesn't a 301 always suffice to enforce the new URL?

Google operates on a combined signals model to determine which URL to display in the SERPs. A 301 redirect is a strong signal, but it competes with other indicators: canonical tags, internal links, external links, sitemaps, mentions in Search Console.

When these signals converge, there’s no problem. But if your internal linking is still heavily pointing to the old URL, or if your canonical tags create conflicts, Google may decide to display the source URL despite the 301. The engine aims to identify what it considers the most legitimate version, not necessarily the one you redirected.

How does Google arbitrate between contradictory signals?

No one knows the exact weighting of the different signals. What we observe in practice: internal links hold immense weight. A site with 1,000 internal links pointing to the old URL and a 301 to the new one might see Google hesitate for weeks, or even months.

Declarative canonical tags also come into play. If you redirect A to B via 301 but B contains a canonical tag pointing to A, you create a conflict that Google must resolve. Spoiler alert: it won’t always side with your expectations.

What really happens during a migration with 301?

In a clean migration scenario, Google crawls the old URL, encounters the 301, follows the redirect, indexes the new URL, and transfers PageRank and historical signals. Observed delay: from a few days to several weeks depending on crawl frequency.

But if your signals are inconsistent, you enter an algorithmic indecision phase. Google may alternate between the two URLs in the SERPs, dilute PageRank between both versions, or even continue displaying the old URL with a snippet pulled from the new one. In short, chaos.

• The 301 is a canonicalization signal, not an absolute directive that overrides all other indicators
• Google combines several factors: redirects, canonical, internal/external links, sitemaps, indexing history
• Conflicts between signals create indecision scenarios where Google may display the old URL despite the redirect
• The time to take effect depends on crawl frequency and the consistency of the signals sent
• A successful migration requires total consistency among all canonicalization signals across the entire site

Is this statement consistent with real-world observations?

Absolutely. We regularly see migrations where the 301s have been in place for months, yet the old URL remains visible in the SERPs. Systematic cause: an internal linking structure that hasn’t been updated, or massive backlinks that continue to point to the old domain.

What’s frustrating is that Google gives no numeric weighting of the signals. It's clear that internal links carry significant weight, but to what extent compared to a 301? Impossible to say. [To be verified] in each migration context, as there’s no universal rule.

What are the gray areas and limits of this logic?

First point: Google talks about "signals" without specifying their hierarchy or validity duration. Does a 301 active for 6 months have the same weight as a 301 implemented yesterday? No official data on that.

Second problem: cases of circular or chained 301s. If A redirects to B which redirects to C, Google may choose to ignore the chain and index A or B. Or not index anything at all. The official documentation remains vague about these scenarios.

In what situations does this rule not apply as expected?

On sites with a complex SEO history — several successive migrations, expired domains purchased, old duplicate content — Google may cache contradictory signals that persist for months. I've seen cases where the target URL of a 301 still did not appear in the index after 90 days because orphaned canonicals pointed to a third URL.

Another limit: migrations between subdomains and subdirectories. Google sometimes treats these structures differently, and a 301 from blog.example.com to example.com/blog might take longer to stabilize than a simple 301 between pages on the same domain. No documented rule, just empirical observations.

What should you do during a migration with 301?

First rule: update ALL internal links to the new URLs before even activating the redirects. A linking structure that points directly to the new URLs strengthens the canonicalization signal. Don’t let Google follow hundreds of unnecessary 301s.

Second action: check that your canonical tags point to the new URLs, not to the old ones. The same goes for XML sitemaps: only submit new URLs. Remove old URLs from Search Console if you want to speed up the deindexing process.

What mistakes should you absolutely avoid?

Classic mistake: activating 301s without checking the redirect chains. If A redirects to B which redirects to C, Google may lose PageRank along the way, and the canonicalization signal weakens. Limit yourself to a single redirect per URL.

Another pitfall: leaving external links pointing to old URLs without taking action. Reach out to critical sites to update the links. The fewer 301s Google encounters on reference URLs, the faster it stabilizes indexing on the new ones.

How can you check that Google has properly acknowledged the canonicalization?

Use the URL inspection tool in Search Console for each critical URL. Google will tell you which URL it considers canonical. If it’s not the one you’re targeting, dig deeper: remaining internal links to the old URL, misconfigured canonical, outdated sitemap.

Also monitor crawl data in server logs. If Googlebot continues to hit the old URLs massively despite the 301s, it indicates that external signals (backlinks, old sitemaps) are encouraging it. Clean up those signals.

• Update all internal links to the new URLs before activating the 301s
• Ensure that canonical tags point to the target URLs, not the sources
• Submit an XML sitemap containing only the new URLs
• Eliminate any redirect chain (A→B→C) to avoid signal dilution
• Contact major referring sites to update backlinks to the new URLs
• Use the URL inspection tool in Search Console to verify the canonical URL adopted by Google