Isolated URL Found Only Via a Redirect
A destination URL has zero internal inlinks and is reachable only as the target of a redirect, so it depends entirely on that hop.
What you see
Screaming Frog → Inlinks URL: https://example.com/blog/new-post Inlinks (internal): 0 Discovered via: 301 from /blog/old-post No direct internal links point here
What’s actually happening
A crawler reports the live URL with 0 internal inlinks, yet it's in the crawl — because the only way in is a redirect. Every internal link on the site still points at the old, redirecting URL; nothing links to the new one directly. So the page exists in the index only as long as the redirect does, and every visitor and crawler eats an extra hop to reach it. Pull the old redirect during some future cleanup and the page silently becomes unreachable. It's the redirect-source twin of an orphan: links exist, they just all aim at the wrong (pre-redirect) address.
Common causes
- A page moved (slug/URL change) and a 301 was added, but the internal links to the old URL were never rewritten to the new one.
- An HTTPS or www migration redirects old→new while every menu/footer/body link still uses the old scheme/host.
- Content was bulk-redirected via a redirect map, with no follow-up pass to update the linking pages.
- An external or paid link points at the old URL; internally there are no links to the destination at all.
- A trailing-slash or case change created a redirect that all existing links route through instead of targeting the final form.
How to fix it
- List the links feeding the old URLIn Screaming Frog, find the redirecting (old) URL and open its Inlinks tab — that's every internal link still pointing at the redirect. Bulk Export → Response Codes → Redirection (3xx) Inlinks gives you the full source list to fix.
- Repoint those links at the final 200 URLUpdate each href to the destination that returns 200 directly — correct slug, scheme, host, and trailing slash. Now the links carry traffic and equity straight in, instead of bouncing through the redirect.
- Fix templates and high-traffic pages firstIf the link lives in nav, footer, or a related-posts block, one edit fixes it sitewide and removes the most hops. Body-copy links are the long tail — do them after the templated ones.
- Keep the redirect, but stop depending on itLeave the 301 in place for external/inbound links and bookmarks — just don't let it be the only path. Once internal links point at the final URL, the redirect is a safety net, not a lifeline.
- Recrawl and verify direct inlinksRe-run the crawl; the destination URL should now show internal inlinks > 0 and be discovered via links, not solely via a redirect.
Stop it recurring
Whenever you add a redirect, immediately rewrite the internal links that pointed at the old URL so the destination is reachable without the hop.