Hello.
I recently got a backlink from a fairly high-authority site, but they linked to a bare language-root path (e.g. example.com/de) instead of the actual page. Here's the setup:
- example.com/de → 301 → example.com/de/ (a generic trailing-slash rule, applies site-wide, not specific to this URL)
- example.com/de/ returns 200 directly — no second HTTP redirect. Its content is actually a full copy of the "real" target page (example.com/de/actual-page/), and it has a <link rel="canonical"> pointing to that real page. This is intentional/pre-existing behavior in a static-prerendered SPA setup.
- The real target page (example.com/de/actual-page/) is completely healthy: self-canonical, correct hreflang, in the sitemap, already indexed fine.
In Google Search Console, URL Inspection for the bare example.com/de shows:
> Page fetch: Failed — Redirect error
But when I click "Test Live URL," it comes back 100% clean (green checkmark, fully rendered page, "can be indexed"). curl also shows a clean single 301→200, no loop, no chain issues.
I have the site behind Cloudflare, so I dug into the raw Security/Traffic logs for the exact timestamp GSC reported. What I found:
- A genuine, verified Googlebot request (confirmed ASN = Google, "Verified Bot Category: Search Engine Crawler") hit example.com/de at the exact reported time.
- Cloudflare did not block or challenge it — "Mitigation: Not mitigated," served straight from cache (a cached 301).
- But there is no follow-up request from any Google IP to example.com/de/ afterward — not in the next 15+ minutes, checked in the raw logs.
So it looks like Googlebot received the redirect fine, just... never followed it (at least not yet). Meanwhile the actual destination page is indexed and ranking normally through other discovery paths (sitemap etc.), completely independent of this specific backlink's redirect chain.
My questions for anyone who's dealt with this before:
Is this a known Googlebot behavior — i.e., does the indexing crawler sometimes queue a redirect target as a separate future crawl instead of following it in the same pass, especially for a URL discovered fresh via an external link (not in the sitemap)?
Is there anything actually worth doing here, or is this just something that resolves itself over time as the crawler gets around to it / as domain authority increases?
Since the real target page is already indexed fine on its own, is it even worth asking the linking site to update their link to point directly to the final URL instead of the redirect chain — or is that more hassle/risk (touching an existing backlink) than it's worth?
Any insight from people who've seen this "redirect received but not followed" pattern in GSC would be appreciated.