Why does the URL Inspection Tool show a 200 code for a 301 redirect?

What really happens in the URL Inspection Tool?

The URL Inspection Tool in Google Search Console does not operate as a simple HTTP status checker. It simulates the complete behavior of Googlebot: the bot follows the redirects, executes JavaScript, and then displays the final status of the page after all this processing.

When you inspect a URL that returns a 301 redirect, the tool does not stop at the first status code. It automatically follows the redirect to the final destination, and it is this arrival page that is analyzed and shows a 200 code. This is exactly what Googlebot does in reality — it does not care about the intermediate URL but about the final accessible resource.

How does this differ from a standard HTTP code test?

A tool like cURL or a traditional header analyzer will show you the 301 code on the original URL. This is normal: these tools do not automatically follow redirects, or they show you each step of the chain if you ask explicitly.

The fundamental difference: Search Console does not show you the intermediate steps. It shows you the final result as Googlebot sees it once all redirects are resolved. It's a logic of usability, not a raw technical logic.

Does this mean that Google ignores my 301 redirects?

Absolutely not. Google follows and respects your 301 redirects perfectly. The consolidation of PageRank authority, the transfer of signals, and the indexing of the correct target URL all function normally.

The display of the 200 code in the inspection tool does not undermine the consideration of your redirects. It's simply a matter of interface: Google shows you what it has ultimately indexed, not the path taken to get there. The redirect is processed upstream, invisible in this specific report.

• The inspection tool simulates the complete behavior of Googlebot, including following redirects
• The displayed 200 code corresponds to the final destination page, not the original URL
• Classic technical tools show the 301 code, Search Console shows the result after processing
• This distinction is purely cosmetic: your redirects are correctly interpreted and respected by Google
• Do not confuse inspection reports and HTTP header analysis — they are two different logics

Is this statement consistent with field observations?

Yes, absolutely. In the field, I have seen dozens of clients panic over this behavior from Search Console, believing their 301 redirects were not functioning. In reality, a quick test with an external tool confirms that the redirect is indeed in place on the server side.

This confusion arises from a misalignment of expectations: one expects a diagnostic tool to show raw HTTP codes, while Google has chosen a results-oriented approach. Both logics are valid, but they do not answer the same question. One asks "what does the server return?", while the other asks "what does Googlebot ultimately index?".

What issues can this interface mask?

The real risk is that displaying the 200 code may prevent you from detecting certain anomalies in the redirect chain. If you have a cascading chain (URL A → URL B → URL C), Search Console will just show the final 200 on C, without indicating that you have a structural problem.

Specifically? You will not see that you have a two-hop redirect instead of a single one, which dilutes the transferred authority and slows down crawling. To identify this type of issue, cross-reference with an external technical audit — Screaming Frog, OnCrawl, or even a simple server script that traces each redirection hop.

When should I truly worry about a displayed 200 code?

If you see a 200 code on a URL you thought you had redirected, two scenarios can occur. First case: your redirect is working, it's just the interface that shows the destination. Check with cURL or another tool — if the 301 is there, everything is fine.

Second case: your redirect was never put in place. Here, the displayed 200 is a real warning sign. You thought you had configured a redirect on the server or in your CMS, but it was never activated or was overwritten by a later configuration. [To be checked] systematically if you have any doubts — never solely rely on Search Console to validate the presence of a 301 redirect.

How to verify that my redirects are correctly configured?

Never solely rely on the URL inspection tool to validate your 301 redirects. Use an external tool that displays raw HTTP codes: cURL from the command line, a browser plugin like Redirect Path, or a crawler like Screaming Frog in list mode.

Test the original URL directly. If you get a 301 code with the correct destination, your redirect is working. If you get a 200, either it does not exist, or it has been misconfigured. This is the only way to definitively determine what’s happening, regardless of what Google Search Console shows.

What to do if I detect a chain of redirects?

A redirect chain (A → B → C) is an SEO anti-pattern. It dilutes the transferred PageRank, slows down crawling, and complicates the consolidation of signals. The inspection tool will not help you detect it since it will just show the final 200.

Use a technical crawler configured to follow and record each step of redirection. Identify all chains, then correct them by pointing directly from A to C. This is an essential maintenance task, especially after a site migration or redesign where multiple layers of redirects may accumulate unnoticed.

Should I modify my SEO audit strategy following this statement?

Yes, in the sense that you should diversify your information sources. Search Console is excellent for understanding what Google indexes, but it does not replace a comprehensive technical audit with third-party tools. Both perspectives are complementary, not interchangeable.

Always integrate a check of raw HTTP codes into your redirect audits. Never assume that a 200 code in Search Console means the absence of a redirect. Conversely, do not panic if you see a 200 while knowing that you have set up a 301 — check the server reality before concluding that there is a bug. The optimal management of these configurations can be complex, especially on large sites with a history of migrations. In such cases, the expertise of a specialized SEO agency can make a difference in accurately mapping your redirects, identifying hidden chains, and establishing a clean architecture that maximizes authority transmission.

• Test your redirects with cURL or Screaming Frog, not just with Search Console
• Ensure there are no cascading redirect chains (A → B → C)
• Document every 301 redirect in a database or spreadsheet to track the history
• Consistently cross-reference Search Console data with an external technical audit during migrations
• Train your teams to distinguish between server HTTP codes and Googlebot post-processing display
• Automate the detection of new chains via monitoring scripts if your site evolves frequently