301 Redirects Explained: When and How to Use Them

What a 301 Redirect Actually Does

A 301 redirect automatically sends anyone who visits an old URL to a new one, instantly and invisibly, without them having to do anything. The "301" is an HTTP status code meaning "moved permanently" — it's the browser and search engine's way of being told, unambiguously, that this content now lives somewhere else, for good.

This matters for two audiences at once. For visitors, it means an old bookmark, a link from a years-old blog post elsewhere, or a printed business card with an old URL still works — the person lands where they intended to, without a broken page in between. For search engines, a 301 tells Google to transfer the old URL's ranking signals — the links pointing to it, the trust it had built up, its position in search results — to the new URL, rather than starting from zero.

Without that redirect, both of those things fail. Visitors following an old link hit a dead page. And Google, finding nothing at the old URL, eventually drops it from the index — taking with it whatever ranking history that page had earned, with nothing automatically transferring to wherever the content moved.

When You Actually Need One

Changing a URL Structure

If yoursite.com/services/roofing becomes yoursite.com/roofing-services during a redesign, every external link, every bookmark, and every search ranking pointing to the old URL needs a redirect or it's simply lost.

Retiring a Page

If you discontinue a service and remove its page, redirecting it to the closest relevant current page (a related service, or a general services page) preserves some value from any links pointing to the old page, and gives a visitor somewhere useful to land instead of a dead end.

Migrating Domains

If you rebrand and move from oldcompanyname.com to newcompanyname.com, every single page needs to redirect to its equivalent on the new domain. This is one of the highest-risk moments in a site's life for losing search visibility, and it's almost always because redirects were partial or missing rather than because the new domain itself was somehow worse.

Switching Platforms

Moving from WordPress to a custom build, or from Wix to Shopify, often changes the URL structure even when the content itself doesn't change much. Every old URL pattern needs a mapped redirect to its new equivalent — this is a task that needs to happen before the old site goes offline, not discovered afterward.

Fixing WWW / HTTPS Inconsistencies

If your site is reachable at both http://yoursite.com and https://www.yoursite.com without one redirecting to the other, you have duplicate, competing versions of every page. A site-wide 301 forcing traffic to one canonical version (typically HTTPS with or without www, whichever you've standardized on) is standard practice, and most hosting setups configure this by default — worth confirming rather than assuming, especially on older sites.

What Happens If You Skip It

This is where the real damage happens, and it's almost always avoidable. A common scenario: a business redesigns its site, the developer builds clean new URLs, the old site goes offline, and nobody builds a redirect map connecting old URLs to new ones. Within a few weeks, organic traffic drops sharply — not because the new site is worse, but because every page that had built up rankings over months or years is now returning a 404 error, and Google is in the process of dropping all of it from the index while the new pages start from nothing.

This is one of the most common and most preventable causes of a business losing search visibility after a site relaunch. It's not a mysterious algorithm problem — it's a missing technical step during migration that a competent developer should catch as a standard part of the launch checklist.

301 vs. Other Redirect Types

A 302 redirect means "moved temporarily" — functionally similar for a visitor, but it tells search engines not to transfer ranking signals, because the move is expected to be reversed. Using a 302 for a permanent change is a common mistake that leaves ranking value stranded on the old URL even though visitors are being sent to the new one. If the move is permanent, use a 301; only use a 302 for genuinely temporary situations, like a page taken down briefly for maintenance.

A meta refresh (a page that loads and then automatically forwards the visitor after a delay, often used in older or poorly built sites) is a much weaker signal to search engines than a proper 301 and adds an unnecessary load delay for visitors. It's worth replacing if you find one on your site rather than treating it as equivalent to a real redirect.

Redirect Chains: A Subtler Problem

A redirect chain happens when URL A redirects to URL B, which itself redirects to URL C — often the accumulated result of multiple redesigns over the years, each adding a new layer without cleaning up the old one. Each hop in a chain adds load time and, past a few hops, can weaken how much ranking signal actually makes it through to the final destination. The fix is straightforward once identified: update URL A to redirect directly to URL C, skipping the middle step entirely.

How to Check Your Own Site

If you've redesigned your site or changed any URLs recently, pull up your old sitemap (if you still have access to it) or check Google Search Console's "Pages" report for URLs it previously indexed that are now returning errors. A tool like Screaming Frog can crawl a list of old URLs and confirm whether each one redirects correctly, redirects to the wrong place, or returns a dead 404. This kind of audit is worth doing any time you've launched a redesign, changed platforms, or removed pages — treat it as a standard step in the process rather than something to check only after traffic has already dropped.