Internal Link via Redirect
Internal links that go through a 301/302 redirect waste a server round-trip and leak a small amount of PageRank.
Why it matters
Internal links that go through a 301/302 redirect waste a server round-trip and leak a small amount of PageRank. Direct links to the final URL are strictly better for performance and SEO.
Address when convenient — notices usually mark a polish opportunity rather than a defect. Estimated SEO impact: low — small marginal improvement, but cheap to fix.
How to fix
- Update the link to point to the final URL directly
- Audit templates / menus that still reference old paths
- Keep the redirect in place for external references, but fix your own site
Common causes
If the rule is firing across many pages, the root cause is almost always one of these:
- Pages reachable only through search, sitemap, or external links — never from another internal page.
- Deep section pages buried 5+ clicks from the homepage with no shortcut hub.
- Important pages weakly linked because the navigation never surfaces them.
- Broken internal targets after a slug or section rename without a redirect map.
Anti-patterns to avoid
Even with the best intentions, these "fixes" make the issue worse — recognise them so you don't ship them:
- Hub pages only reachable via the sitemap, not from any header or body link.
- Pagination depth so high that
?page=42is the only way to reach important content. - Renaming sections without adding redirects.
How atlookup detects this
Our crawler renders each page with a real headless browser, then builds a graph of internal links across the entire crawl and analyses orphans, depth, and weak nodes. Pages where the rule fires for internal link via redirect are flagged on the report.
If you'd like to see this rule fire on your own site, run a free 60-second audit — every page is reported with the exact lines that triggered it.
Tools to verify the fix
Once you've applied the fix, double-check with these external validators:
- Screaming Frog — Crawl-depth + orphan-page reports.
- Sitebulb — Visual graph of internal link weight distribution.
Frequently asked questions
Why does Internal Link via Redirect matter for SEO?
Internal links that go through a 301/302 redirect waste a server round-trip and leak a small amount of PageRank. Direct links to the final URL are strictly better for performance and SEO.
How do I fix internal link via redirect?
Update the link to point to the final URL directly Audit templates / menus that still reference old paths Keep the redirect in place for external references, but fix your own site
Is this a critical SEO issue?
Address when convenient — notices usually mark a polish opportunity rather than a defect. Estimated SEO impact: low — small marginal improvement, but cheap to fix.
How does atlookup detect internal link via redirect?
Our crawler renders each page with a real headless browser, then builds a graph of internal links across the entire crawl and analyses orphans, depth, and weak nodes. Pages where the rule fires for internal link via redirect are flagged on the report.
How long does it take to fix?
5–15 minutes per page. Most teams batch similar issues across templates so the per-page time goes down at scale.
Related issues
ARCH_IMPORTANT_PAGE_WEAK_INTERNAL_LINKS
Important Page Has Weak Internal Links
A high-importance page (homepage, pricing, key landing page) with few unique inlinks is under-supported by your site structure.
ARCH_BROKEN_INTERNAL_LINK_TARGET
Internal Link to Broken Page
Internal links pointing to pages that return 4xx/5xx waste PageRank and create a broken user experience.
ARCH_PAGE_ORPHAN
Orphan Page (No Internal Inlinks)
Pages with zero internal links are unreachable through site navigation.
ARCH_ANCHOR_TEXT_GENERIC
Generic Internal Link Anchor Text
Anchors like "click here", "read more", "learn more" give Google no topical signal and give users no preview of the destination.