Let me pop the hood on something most business owners never think about: what happens in the split second before your website even loads. There’s a technical layer running underneath every page on your site, and when it’s messy, search engines get confused about which version of your page is the real one. That confusion costs you rankings you already earned.
This isn’t a flashy topic. Nobody gets excited about redirects. But a handful of small technical issues, left unchecked, quietly split your ranking signal across multiple versions of the same page instead of pointing all that authority at one place.
Here’s what’s going on, what to fix, and how to check your own site.
What’s actually happening under the hood
Every time someone, or Google, requests a page on your site, your server has to answer one question: is this the final destination, or does the visitor need to be sent somewhere else? A redirect is the “somewhere else” instruction. Used correctly, redirects are harmless, even helpful. Used sloppily, they create a maze.
Three problems show up over and over.
Redirect chains
A redirect chain is when Page A redirects to Page B, which redirects to Page C, instead of sending the visitor straight from A to C. Each hop adds load time and makes search engines work harder to figure out which page actually counts. Two or three hops deep, and some crawlers give up before they reach the final page at all.
HTTP and HTTPS both live
HTTPS is the secure, padlocked version of your site. HTTP is the old, unsecured version. Plenty of sites technically have both versions accessible at the same time, even though almost nobody realizes it. Search engines see the HTTP and HTTPS versions of a page as two separate pages. If both are live and neither redirects to the other, you’ve split your own ranking signal in half without knowing it.
Old redirects nobody removed
You changed a URL two years ago and set up a redirect. Fine. But if that old page no longer exists anywhere, and nothing links to it anymore, the redirect is just dead weight sitting on your server, one more thing that can break during a future update.
Where these chains usually come from
Nobody decides to build a redirect chain on purpose. They happen in pieces, from three habits.
Slug changes without updating the source
You rename a service page, from something clunky to something cleaner, and set up a redirect from the old address to the new one. Fine, that’s one hop. Six months later you rename it again for SEO reasons, and now the first old address redirects to the second old address, which redirects to the current one, because nobody went back and pointed the original straight at the final page.
Redirect plugins that stack instead of replace
Most platforms let you add redirect rules one at a time through a plugin or settings panel, and it’s easy to add a new rule without checking whether an old one already covers part of the same path. Over a year or two, a site quietly accumulates overlapping rules that all fire in sequence.
Migrations without a redirect map
This is the big one. When a site moves to a new platform or domain, every URL risks shifting. Without a written map of old URL to new URL, made before the migration, whoever builds the new site ends up guessing at redirects afterward instead of getting it right on day one.
A quick example
A local HVAC company redesigned its site twice in four years, once for a new look, once to add online booking. Each redesign moved the service pages without anyone checking what was already redirecting where. By year four, their crawl report showed three hops before landing on the current “AC repair” page, the kind of quiet drag that adds up without anyone noticing.
How to fix it, step by step
- Pick one canonical version of your site. That means choosing the www version or the non-www version, not both, and sticking with it everywhere: every link, every listing, every piece of marketing.
- Force HTTPS everywhere. Every HTTP request should redirect straight to HTTPS, in one hop, no detours.
- Fix internal links so they point straight to the final page. If your own navigation menu or footer links to a page that then redirects somewhere else, update the link itself instead of relying on the redirect to catch it.
- Collapse chains into a single hop. If Page A redirects to B and B redirects to C, change A to redirect directly to C. Delete the middle step.
- Clean out redirects for pages that no longer matter. If nothing links to the old URL anymore and it’s not still getting traffic, there’s no reason to keep the redirect around.
How to check your own site
You don’t need to guess at any of this. A free crawl tool will scan your site and flag redirect chains, mixed HTTP and HTTPS pages, and broken redirects in a few minutes. Run one after any major site change: a redesign, a URL restructure, a platform migration, anything that touches your site’s structure.
When the report comes back, sort by the pages with the most hops first, those are doing the most damage, and work down the list from there.
While you’re in there, check two related things. Your canonical tag, a small piece of code on each page that tells search engines which version is official, should point to itself on every page. Your sitemap, the file listing every page you want indexed, should only list live URLs, never an old address that redirects elsewhere.
Why this actually matters for your traffic
Here’s the juice-box math version, the kind I’d explain to a nine-year-old on my kid’s soccer team if traffic instead of trophies were on the line. Say your page has earned links and shares pointing at both the HTTP and HTTPS versions. Google doesn’t combine that authority, it splits it. Half a page’s worth of ranking strength going to a URL that isn’t even the one you want to win.
That’s money doing push-ups. Working hard, going nowhere.
Every redirect hop also slows the page down a little, and page speed is its own ranking factor. So a chain isn’t just a technical curiosity, it’s dragging down the exact metric you’re also trying to improve. Getting the technical layer of your site clean is part of what our website care plans handle on an ongoing basis, but you don’t need us to run the basic check yourself.
The move: run one crawl this week, fix the chains it finds, and force HTTPS across the board before your next big site change.
Want your redirects and technical setup actually clean? That’s part of our website care plans.
Frequently asked questions
What’s the difference between a redirect chain and a normal redirect?
A normal redirect sends a visitor from an old page straight to its new location in one step. A chain happens when that new location redirects again to a third page, so visitors and search engines have to follow two or three hops before landing on the real page. Chains slow things down and make it harder for search engines to credit the right page with your ranking signal.
How do I know if my site has both HTTP and HTTPS versions live?
Type both the HTTP and HTTPS versions of your homepage address into a browser and see what happens. If both load without redirecting to a single version, you’ve got two live copies of your site competing against each other. A free crawl tool will also flag this automatically, along with any redirect chains.
How often should I check my site for redirect issues?
Run a crawl after any change that touches your site’s structure: a redesign, a URL change, a new page builder, or a platform move. Outside of that, checking once or twice a year is enough to catch anything that snuck in on its own.
