What Is a 301 Redirect — and Why Do They Matter?
Moved Pages · Saved Rankings · Zero Dead Ends
When you move to a new house, you file a mail-forwarding order so nothing important gets lost. A 301 redirect is exactly that — for your web pages. It's one of the smallest, least glamorous pieces of website plumbing, and skipping it is the #1 reason businesses watch years of Google rankings vanish after a redesign. Here's the whole story in plain English.
Every page on your website has an address — and addresses change
Every page lives at a specific URL: yourbusiness.com/services, yourbusiness.com/about. Over a website's life, those addresses change constantly — a redesign reorganizes everything, a page gets renamed, you switch to HTTPS, you rebrand to a new domain, an old product retires. Perfectly normal. The problem is what you leave behind: the whole internet still knows the old addresses. Google's search results point there. Other websites link there. Customers bookmarked there. Your old emails, business cards, and social posts all point there.
A 301 redirect is the mail-forwarding order for a moved page: a small server instruction that says “this page has permanently moved — here's the new address.” Anyone (and anything) arriving at the old URL is seamlessly delivered to the new one, usually without even noticing. The “301” is just the technical code number for “moved permanently” — and that word permanently is what makes it special, because it tells Google something important: transfer everything this old page earned to the new one.
If you've read our indexing guide, this page will feel familiar — redirects came up there again and again, because missing or broken redirects are one of the most common reasons Google loses track of a website's pages. Consider this the full story behind all those mentions: our guide to “Crawled – Currently Not Indexed” pairs with this one.
The Same Moved Page, Two Fates
Without a Redirect
Dead end, lost credit
A customer clicks your Google listing or an old link and lands on a “404 — Page Not Found” error. Most leave immediately (many assume you closed). Meanwhile Google keeps hitting the dead end too, eventually removes the old page from search — and the years of ranking credit that page earned simply evaporate. Your new page starts from zero, a stranger to Google.
With a 301 Redirect
Seamless handoff, credit preserved
The same customer clicks the same old link — and lands on the new page without ever seeing an error. Every old bookmark, business card, and backlink keeps working. And Google, seeing the permanent-move signal, transfers the old page's earned reputation to the new address, so your rankings carry over instead of resetting. Same move, entirely different outcome.
What “ranking credit” actually means: over years, a page accumulates reputation with Google — other sites linking to it, a history of satisfying searchers, trust built visit by visit. That reputation is attached to the page's address, not to your business in the abstract. Change the address without a forwarding order, and the reputation stays behind with a dead URL. The 301 is how you take it with you.
301, 302, 404 — the three numbers worth knowing
These are “status codes” — the short numeric messages a website sends browsers and search engines about a page. You only need three of them:
301 — The Workhorse
“This page has moved for good — go here instead, and transfer everything it earned.” The permanent forwarding order. Use it whenever a page's address changes and isn't coming back: redesigns, renames, HTTPS moves, rebrands. When people say “set up redirects,” this is the one they mean.
→ Passes your Google ranking credit to the new address302 — The Placeholder
“This page is elsewhere for now — but it's coming back, so don't transfer anything.” For genuinely temporary situations: a page under maintenance, a seasonal promotion, a short-term detour. The classic mistake is using a 302 for a permanent move — Google then hesitates to pass the credit along.
→ When in doubt about permanence, it's almost always a 301404 — The Honest Dead End
“Nothing lives at this address.” Not always a villain! When a page truly has no successor — a discontinued service with no replacement — an honest 404 is the correct answer, and a friendly custom 404 page (“Hmm, that page has moved on — here's our menu”) softens the landing.
→ A few honest 404s are fine; hundreds of accidental ones aren'tOne tempting shortcut to avoid: redirecting every old page to your homepage. It feels tidy, but it strands visitors (someone seeking your old pricing page doesn't want your homepage) and Google treats mass homepage-redirects as “soft 404s” — dead ends in disguise — and passes little or no credit. The rule: redirect each old page to its most relevant new counterpart, and let truly retired pages 404 honestly.
Redirect problems in the wild — match your situation
Redirect issues rarely announce themselves as redirect issues. Here's what they actually look like from where you're sitting:
| What You're Seeing | What It Usually Means | Severity |
|---|---|---|
| Traffic fell off a cliff right after a redesign or new website launch | The classic. The new site used new URLs and nobody set up redirects — Google's listings and every old link now hit dead ends | Urgent — fixable |
| Clicking your own site in Google results lands on “Page Not Found” | Google still lists old URLs that no longer exist and were never redirected — every one is a customer bouncing off an error page | Urgent — fixable |
| Search Console shows a pile of 404 “Not Found” errors | Google is telling you exactly which old addresses need forwarding orders — this report is your redirect to-do list, gift-wrapped | Fix this month |
| Search Console shows “Page with redirect” | Usually not a problem at all — Google noting that an old URL forwards somewhere, exactly as designed. Only worth a look if pages that shouldn't redirect appear here | Usually fine |
| “Too many redirects” error — the page won't load at all | A redirect loop: A forwards to B, and B forwards back to A, forever. Usually two systems (host, plugin, CDN) each adding their own redirect rule | Urgent — site is down |
| A link takes several visible “hops” before landing | A redirect chain (A→B→C→D) — each hop adds delay and shaves reliability. Usually the residue of multiple redesigns stacking forwarding orders | Worth cleaning up |
| Your site loads at both http:// and https://, or with and without www | Missing sitewide redirects — your site exists as multiple duplicate versions splitting credit between them. One version should win; the rest should 301 to it | Fix this month |
| You changed your business name and the old domain just... sits there | Every link, listing, and memory of the old name is going nowhere — a domain-level 301 forwards all of it (and its accumulated credit) to the new name | High-value fix |
Check any URL in ten seconds: paste it into a free redirect checker like httpstatus.io — it shows you the exact status code (301, 302, 404) and every hop in the journey. Wondering about your own old pages? Search Google for site:yourbusiness.com, click your listings, and see where they land.
The 10 moments that call for a redirect
Bookmark this list — every one of these is a moment when a few minutes of redirect setup protects years of earned visibility.
Moment 01 · The Big One
A website redesign or rebuild
New sites almost always mean new URL structures — /our-services becomes /services, blog posts get new paths, everything shuffles. This is where the “traffic fell off a cliff after our beautiful new site launched” story is born: the new site is lovely, and Google's map to it points entirely at demolished addresses.
The move: Before launch, list every old URL and map it to its new home. Redirects go live the same moment the new site does — never “we'll get to it after launch.”
Moment 02
Switching to HTTPS
Getting an SSL certificate makes the secure version of your site available — the sitewide 301 from http:// to https:// is what makes it the only version, moving every visitor and all your credit to the secure address.
The move: Turn on “Force HTTPS” at your host. The full story lives in our “Not Secure” guide.
Moment 03
Renaming a page (changing its slug)
Even a tiny cleanup — /services-2 to /services, or improving a blog post's URL for SEO — creates an orphaned old address the moment you hit save. WordPress sometimes creates the redirect automatically... and sometimes doesn't, which is exactly the kind of “sometimes” that bites.
The move: After any rename, test the old URL yourself. If it 404s, add the 301 manually — thirty seconds now versus lost visitors indefinitely.
Moment 04
A rebrand or new domain name
The highest-stakes version: your entire accumulated reputation lives on the old domain. A domain-level 301 (every old page forwarding to its counterpart on the new domain) carries years of credit — and every old link, listing, and printed card — across the rename.
The move: Keep renewing the old domain (it's cheap insurance — our Domain vs. Hosting vs. Website guide covers why) and leave the redirect in place for years, not months.
Moment 05
Retiring a page, product, or service that has a successor
The old workshop page, the discontinued package, last year's event — if something newer fills the same need, forward the old page to it. Visitors seeking the old thing find its replacement, and the old page's credit boosts the new offering instead of evaporating.
The move: Redirect to the closest relevant successor. No successor at all? An honest 404 with a friendly custom page beats a misleading redirect.
Moment 06
Merging two pages into one
Two thin, overlapping pages (say, two similar service pages competing with each other in search — a problem our indexing guide calls cannibalization) often perform better combined into one strong page. The 301 from the retired page to the survivor is what pools their credit instead of discarding half of it.
The move: Merge the content first, then 301 the retired URL to the combined page. One page, all the credit.
Moment 07
Consolidating www vs. non-www (and other duplicates)
If www.yourbusiness.com and yourbusiness.com both load without one forwarding to the other, Google sees two duplicate websites splitting one site's credit. Same for trailing-slash variants and stray capitalized URLs. Pick one canonical version; 301 everything else to it.
The move: Most hosts handle this with one setting. Test both versions of your address right now — do they end up in the same place?
Moment 08
Moving platforms (builder to WordPress, or between builders)
Wix, Squarespace, Shopify, and WordPress all structure URLs differently, so a platform move silently changes most of your addresses even when the content looks identical. It's a redesign in disguise — with all the same redirect stakes.
The move: Treat every platform migration like Moment 01: full URL inventory before, full redirect map at launch. Each platform has its own redirect tool — they all support this.
Moment 09
Cleaning up after past redesigns you inherited
Maybe the cliff already happened — a redesign two years ago, a platform move under a previous marketing person — and old dead URLs have been quietly bouncing visitors ever since. Good news: it's genuinely never too late. Old links keep pointing at old addresses for years, waiting for a forwarding order.
The move: Search Console's “Not Found” report lists the dead URLs still getting traffic — redirect those first. Recovery follows as Google recrawls.
Moment 10 · The Fun One
Friendly marketing URLs
Redirects aren't only damage control — they're also how you create memorable short addresses on purpose: yourbusiness.com/sale forwarding to a long promotion URL, /podcast to your show page, /book to your scheduling link. Perfect for radio spots, print, and anything people have to remember and type.
The move: Same tools, happier occasion — and pair them with UTM tags so you can see in your analytics exactly how many people typed the short address.
Why missing redirects hurt twice
A missing forwarding order costs you with two different audiences at once — the humans arriving today, and the search engine deciding who arrives tomorrow:
Cost 1 — Today's Visitors
Every dead end is a customer turned away at the door
The people clicking old links are your warmest traffic — they searched for you, saved you, or were referred to you. A 404 greets that ready-to-buy visitor with a shrug. Few click around to hunt for the new page; many quietly conclude you've closed or moved on, and the referral or ranking that brought them gets wasted at the last possible step.
Cost 2 — Tomorrow's Rankings
Years of earned reputation, abandoned with the old address
Google's trust in a page — built from every site that linked to it and every searcher it satisfied — belongs to the URL. When the URL dies without a 301, that trust doesn't find your new page on its own; it decays with the dead address, and the replacement page starts life as an unknown. This is the mechanism behind “we redesigned and our Google traffic never recovered” — and it's the through-line of our indexing guide.
The hopeful flip side: because both costs flow from one missing instruction, one added instruction fixes both — even retroactively. Add the 301s today and the old links start delivering customers again immediately, while Google gradually re-routes the old credit as it recrawls. Here's what a fully healthy redirect setup looks like:
The Redirect Health Audit — 12 Things to Verify
Old URLs inventoried
You know which past addresses existed — from old sitemaps, crawls, or Search Console?
Each mapped to its best match
Every old page forwards to its most relevant successor — not dumped on the homepage?
301s, not 302s
Permanent moves marked permanent, so the credit actually transfers?
No chains
Old URLs jump straight to the final destination — not A→B→C through redesign history?
No loops
Nothing forwards back to itself — no “too many redirects” errors anywhere?
HTTPS enforced
Every http:// address 301s to https:// sitewide?
One canonical version
www vs. non-www settled — one wins, the other forwards?
Internal links updated
Your own menus and in-page links point at final URLs — not routed through redirects?
Sitemap is clean
Your sitemap lists only live, final URLs — no redirecting or dead addresses?
404 report reviewed
Search Console's Not Found list checked — real pages redirected, junk ignored?
A friendly 404 page
Genuine dead ends land somewhere warm — with a search box and paths onward?
Redirects kept long-term
Forwarding orders left in place for years — not cleaned up prematurely?
A step-by-step plan — whether you're preventing or recovering
Same six steps either way: before a redesign, they prevent the cliff; after one, they climb back out of it.
Build Your List of Old URLs
Before a redesign: export every current URL (your sitemap at yourbusiness.com/sitemap.xml is the easy source, plus your analytics' top-pages report). After the fact: Search Console's Pages report shows the “Not Found (404)” addresses Google still visits — that list, sorted by traffic, is your priority order, handed to you.
Map Each Old Address to Its Best New Home
A simple two-column spreadsheet: old URL, new URL. The guiding question for every row: “if someone wanted the old page, which new page serves them best?” Match like to like — old service page to new service page, old post to its updated version. Resist the homepage shortcut; a page with no true successor gets an honest 404 instead.
Put the Redirects In Place
On WordPress, a free plugin like Redirection makes this a paste-in list — no code required. Website builders (Squarespace, Wix, Shopify) each have a built-in URL-redirects panel in settings. Sitewide rules (http→https, www consolidation) belong at your host — usually a single toggle. If your list is hundreds of rows, this is an hour of careful copy-paste, not a technical feat.
Test Like a Visitor Would
Click your way through a healthy sample of old URLs — especially your former top pages — and confirm each lands exactly where intended. Run a few through httpstatus.io to verify they return a single 301 hop (no chains, no loops, no sneaky 302s). Then test the sitewide basics: http and https, www and non-www, all arriving at one address.
Point Your Own House at the New Addresses
Redirects catch outsiders; your own site shouldn't need catching. Update your menus, footer links, and in-page links to the final URLs, confirm your sitemap contains only live final addresses, and submit it in Search Console. Then update the outside world's most important pointers: your Google Business Profile link, ad destinations, and social bios.
Watch, Then Leave Them Alone
Check Search Console every few weeks: the 404 count should shrink as “Page with redirect” entries grow (that's the system working). Then the counterintuitive final step: don't tidy the redirects away later. External links point at old addresses for years — forwarding orders are meant to stay. They cost nothing to keep and something every time one is removed.