Why is GSC still reporting 404 for URLs after I’ve deployed 301 redirects?

New: Dev to Dev Hub
,
1

I’ve got a case where server logs, cURL and HTTP header checks confirm that old URLs are correctly returning 301 → final destination, yet Google Search Console (GSC) still shows them as “404 – Not Found.” I’m trying to determine whether this is due to stale crawl data, redirect chain timing, or even residual canonical signals interfering.

According to sources on 301 redirect behavior and caching, it’s common for GSC to temporarily show mismatched statuses even when the server responds correctly. Has anyone dealt with similar discrepancies between server responses and GSC reporting?

1 Like
2

Hi there!

Welcome to the Auth0 Community!

While I can’t provide a definitive solution from an Auth0 perspective, I recommend seeking expertise from communities dedicated to this specific domain. Your question is very well-formulated and would be perfect for:

  • Google’s Search Central Community: This is the official support forum where Google’s own team and other SEO experts troubleshoot these exact GSC reporting issues.

Thanks!
Dawid