1const e={title:"Internal links that redirect: what it really costs",description:"A link inside your own site pointing at an address that redirects makes visitors wait for an extra hop. Here is what that really costs, and what it does not.",date:"2026-09-17",updated:"2026-09-18",excerpt:"You moved a page and set up the redirect. But the links inside your own site still point at the old address. Here is what that costs.",tags:["internal-links","redirects","technical-seo"]},t=`<p>You moved a page to a new address and set up a permanent redirect from the old one. Good call. 2The problem is that the links scattered across your own site still point at the old address.</p> 3<p>Every click there becomes two trips instead of one. The browser asks for the old page, the server 4answers "that one moved, go to this other one", and only then does the page start loading.</p> 5<p>That is the subject of this article. It is common, easy to find and cheap to fix. And most of what 6gets said about it is wrong.</p> 7<h2>What it looks like in practice</h2> 8<p>Say your consulting page lived at <code>/consulting</code> and you moved it to <code>/services/consulting</code>. A 9permanent redirect was created, and anyone typing the old address lands on the new one without 10noticing. Perfect.</p> 11<p>Except the site menu, the footer, three blog articles and the home page still carry the link 12written like this:</p> 13<pre><code class="language-html"><a href="/consulting">Consulting</a> 14</code></pre> 15<p>Nothing is broken. Visitors do reach the destination. But they take the long road, and everyone 16who clicks pays that toll.</p> 17<h2>Why almost every site has this</h2> 18<p>The causes are always the same:</p> 19<ul> 20<li><strong>Site migration.</strong> Addresses changed in bulk, the links inside the content did not.</li> 21<li><strong>Slug changes.</strong> Someone improved an article's address and forgot who was pointing at it.</li> 22<li><strong>The move from HTTP to HTTPS.</strong> Old links still written with <code>http://</code>.</li> 23<li><strong>With and without <code>www</code>.</strong> The site answers on both, but one redirects to the other.</li> 24<li><strong>Trailing slash.</strong> <code>/page</code> and <code>/page/</code> look identical and are not always treated that way.</li> 25<li><strong>A category or product that no longer exists</strong> and got a replacement destination.</li> 26</ul> 27<p>What makes the number grow fast is repetition. One wrong link in the menu or the footer is not one 28problem, it is one problem multiplied by every page on the site.</p> 29<p>In a measurement we ran on 17 September 2026, on a large public portal, the header logo link 30pointed at an address that redirected. We analysed ten pages and found it on nine of them, twice on 31each. Final count: eighteen links to fix, all for <strong>one</strong> wrong address.</p> 32<h2>What it does NOT cost, despite what almost everyone says</h2> 33<p>The most repeated claim about this is that you are "losing link juice". That claim is wrong.</p> 34<p>In July 2016, Google's Gary Illyes stated publicly that 30x redirects no longer lose PageRank. John 35Mueller then confirmed this was not even news, it had been true for a while. It still holds today.</p> 36<p>So no, the redirect is not eating your page's authority. Anyone saying otherwise is repeating 37advice from 2010 that Google itself retired.</p> 38<p>Keep that in mind, because it also protects your budget: nobody needs to sell you an emergency 39project over this.</p> 40<h2>What it actually costs</h2> 41<p>Three things, and all three are real.</p> 42<p><strong>1. The time of the person who clicked.</strong> Each redirect is a round trip across the network before 43any content starts arriving. Google's own Lighthouse has an audit dedicated to it, called "Avoid 44multiple page redirects", precisely because the hop delays painting the screen. On a phone with a 45weak connection, that extra round trip is felt.</p> 46<p><strong>2. A crawler visit thrown away.</strong> To find out where the page really is, the search engine has to 47ask twice. On a small site that changes nothing. On a large site with tens of thousands of 48addresses, it starts to add up.</p> 49<p><strong>
493. The signal that the migration never finished.</strong> This is the part almost nobody mentions. 50Internal links pointing at old addresses usually come with an outdated sitemap, canonical tags 51aiming at the wrong place and chains of two or three hops. The link is the visible symptom of a 52cleanup that stopped halfway.</p> 53<h2>What Google actually recommends</h2> 54<p>It is worth reading in its own words, because these are four concrete recommendations:</p> 55<table> 56<thead> 57<tr> 58<th>Recommendation</th> 59<th>What it means</th> 60</tr> 61</thead> 62<tbody><tr> 63<td>Change internal links from the old addresses to the new ones</td> 64<td>exactly the subject of this article</td> 65</tr> 66<tr> 67<td>Do not chain redirects</td> 68<td>point straight at the final destination</td> 69</tr> 70<tr> 71<td>Keep chains short</td> 72<td>the crawler follows up to ten hops, but the advice is to stay under five</td> 73</tr> 74<tr> 75<td>Keep the redirect rule live for at least a year</td> 76<td>and this is where the classic mistake lives</td> 77</tr> 78</tbody></table> 79<h2>No drama: this is hygiene, not an emergency</h2> 80<p>On 3 February 2026, in an SEO forum, someone asked whether auditing redirect chains in the browser 81was a time sink. Google's John Mueller answered:</p> 82<blockquote> 83<p><em>"I'd caution against assuming that you need to do this level of analysis for all URLs on a 84website in order to achieve optimal SEO."</em></p> 85</blockquote> 86<p>He added that he does not recall a case like this causing SEO issues that were not also visible to 87average users in their browsers.</p> 88<p>That is a healthy dose of realism. Fixing internal links that redirect is maintenance, like 89changing a water filter. You do it because it is cheap, it makes the site faster and it stops 90grime from building up. Not because the site will collapse tomorrow.</p> 91<h2>How to find them on your site</h2> 92<p>From the most manual to the most practical:</p> 93<ol> 94<li><strong>In the browser.</strong> Click a link and watch whether the address bar changes by itself after 95loading. Fine for confirming a suspicion, useless for sweeping a whole site.</li> 96<li><strong>With a crawler tool.</strong> It walks the site and shows the response of every address. It takes 97setup work and the result arrives as a spreadsheet.</li> 98<li><strong>In a SEOWrench audit.</strong> The report lists every internal link that lands on a redirect, grouped 99by the address that needs replacing, with the pages where it appears and the anchor text of 100each one. The grouping matters: that menu case becomes one line to fix, not eighteen.</li> 101</ol> 102<p>One note on honesty: this finding does not lower your SEO score. Given everything above, it would 103make no sense to deduct points for something Google says is not a ranking factor. It shows up as a 104recommendation, with the list ready to work through.</p> 105<h2>How to fix them</h2> 106<p><strong>The default is to swap the link for the final address.</strong> Where <code>/consulting</code> was written, put 107<code>/services/consulting</code>. Done, the visitor stops paying the toll.</p> 108<p><strong>Sometimes the better move is to remove the link</strong> and keep the plain text. That applies when the 109destination genuinely no longer exists and the replacement has nothing to do with the paragraph it 110sits in. A link that leads anywhere is worse than text with no link.</p> 111<p><strong>Start with whatever repeats.</strong> Menu, footer, sidebar and reusable blocks appear on every page, so 112one edit there clears dozens of occurrences. Only then move on to links inside the content.</p> 113<h2>The mistake that ruins it: deleting the redirect afterwards</h2> 114<p>This is the part that causes the most pain, and the easiest to avoid.</p> 115<p>Fixing internal links does <strong>not</strong> entitle you to delete the redirect rule. The old address stays 116alive outside your control: links from other sites, real people's bookmarks, old shares in chat 117apps, emails sent last year, the search engine's own index.</p> 118<p>Google asks you to keep the rule live for at least a year, and that recommendation exists because 119it is how long it takes to transfer every signal and reprocess third party links.</p> 120<p>The rule of thumb is simple. Internal links you fix today. The redirect rule you keep.</p> 121<h2>When it is not a problem</h2> 122<p>Not every link to a redirecting address is a defect:</p> 123<ul> 124<li><strong>Campaign links</strong>
124 carrying parameters the site strips on purpose.</li> 125<li><strong>Internal short links</strong>, the <code>/promo</code> kind, created precisely to be easy to say out loud.</li> 126<li><strong>Intentional redirects</strong> on a page whose destination changes with the season.</li> 127</ul> 128<p>In those cases the hop is the feature, not the fault. A good list has to let you mark those 129exceptions and stop flagging them.</p> 130<h2>Summary</h2> 131<ul> 132<li>An internal link to a redirecting address does <strong>not</strong> cost you link juice. That is a myth.</li> 133<li>It costs a network round trip for whoever clicked, and one extra crawler visit.</li> 134<li>It almost always points to a migration that stopped halfway.</li> 135<li>Fix the links starting with the menu and the footer, where they multiply.</li> 136<li><strong>Keep the redirect rule live</strong> after fixing them.</li> 137</ul> 138<h2>Sources</h2> 139<ol> 140<li><a href="https://developers.google.com/search/docs/crawling-indexing/site-move-with-url-changes">Google Search Central: site moves with URL changes</a></li> 141<li><a href="https://developers.google.com/search/docs/crawling-indexing/large-site-managing-crawl-budget">Google Search Central: crawl budget for large sites</a></li> 142<li><a href="https://developers.google.com/search/docs/crawling-indexing/301-redirects">Google Search Central: redirects and Google Search</a></li> 143<li><a href="https://developer.chrome.com/docs/lighthouse/performance/redirects/">Lighthouse: avoid multiple page redirects</a></li> 144<li>Gary Illyes on 30x and PageRank, July 2016, via <a href="https://searchengineland.com/google-no-pagerank-dilution-using-301-302-30x-redirects-anymore-254608">Search Engine Land</a></li> 145<li>John Mueller on redirect analysis, 3 February 2026, on <a href="https://www.reddit.com/r/bigseo/comments/1qso38h/is_it_just_me_or_is_auditing_redirect_chains_in/">r/bigseo</a>, reported by <a href="https://www.seroundtable.com/google-on-redirects-analysis-for-seo-40854.html">Search Engine Roundtable</a></li> 146</ol> 147<p>If you want the ground around this, read <a href="/blog/what-is-technical-seo">what technical SEO is</a> and 148<a href="/blog/site-architecture-for-seo">site architecture for SEO</a>, which covers how internal links 149spread relevance across a site.</p> 150<p>And if you want your own list ready, with page and anchor text, a 151<a href="/seo-check">SEOWrench audit</a> hands it over along with the rest of the diagnosis.</p> 152`;export{e as frontmatter,t as html};
Line numbers count LF bytes from the start of the resource, as the search results do. Vendor segments are library code the classifier recognised; they are stored but not indexed. Bytes are shown as Latin1 characters, one per byte.