What is a 301 redirect? It is a server's way of saying "that page lives somewhere else now, permanently." When a browser or a search crawler requests the old URL, the server answers with a 301 status code and the address of the new page, and the request routes there instead. The old URL stops loading, the visitor lands on the new page, and nearly all of the ranking power the old page earned moves with it. It is the cleanest tool for changing a URL without throwing away the years of authority attached to it.
What is a 301 redirect, in plain English?
Every time a browser asks a server for a page, the server replies with a status code. A 200 means "here's the page." A 404 means "that page doesn't exist." A 301 means "that page has permanently moved, here's where it went," and it hands over the new address so the browser can follow it.
The "permanent" part is the whole point. A 301 is a one-way door. Once it's in place, the old URL no longer serves its own content. Users typing the old link, clicking an old bookmark, or following an old backlink all get carried to the new page without doing anything. They often don't even notice the jump.
What makes the 301 matter for search is what happens behind the scenes. When Googlebot recrawls the old URL and sees the 301, it does more than forward the visitor. It transfers the page's accumulated signals (its link equity, its relevance, its ranking history) onto the destination and folds the old URL out of its index. The new page inherits the authority the old one spent years building. That transfer is why a 301 is the default move whenever a URL changes, and why getting it wrong is one of the more expensive mistakes in technical SEO.
How a 301 redirect works
A 301 is an HTTP response. When the request comes in for the old URL, the server returns two things: the status code and a Location header pointing at the new URL.
```
GET /old-page HTTP/1.1
Host: example.com
HTTP/1.1 301 Moved Permanently
Location: https://example.com/new-page
```
The browser reads that Location header and immediately requests the new page. From the user's side it's one smooth jump. From a crawler's side, the 301 is a clear instruction: stop indexing the old URL, consolidate everything onto the new one.
You set redirects up at the server level (an .htaccess file on Apache, a config block on Nginx), through your CMS, through a plugin, or at the CDN edge. Where you implement them matters less than that they return a true 301 status and not a soft redirect faked with JavaScript or a meta refresh, both of which search engines handle slowly and inconsistently.
301 vs 302: the distinction that costs rankings
The single most important thing to get right is permanent versus temporary, because they look identical to a visitor and behave very differently for search.
| Redirect | Meaning | What Google does | Use it when |
|---|---|---|---|
| 301 | Permanent move | Drops the old URL from the index, transfers signals to the new URL | The change is permanent: a page moved, merged, or was renamed for good |
| 302 | Temporary move | Keeps the old URL indexed, treats the new URL as a stand-in | The original will return: A/B tests, short promotions, geo or maintenance pages |
The classic, expensive error is using a 302 (or a CMS default that quietly issues 302s) for a permanent change. Because a 302 tells Google to keep the original URL in the index and not fully transfer authority, the new page never inherits the old one's ranking power, and the move silently caps your visibility. If the move is forever, it has to be a 301. This is one of the first things worth checking in any technical SEO audit.
Why 301 redirects matter
A 301 protects the asset most sites underestimate: the authority their URLs have already earned. A page that has ranked for years has collected backlinks, internal links, crawl priority, and a track record with search engines. Change that URL without a redirect and all of it vanishes. The old URL 404s, the backlinks point at a dead page, and the new URL starts from zero as if it were brand new.
Per Google's own documentation, 301 redirects do not cause a loss of PageRank, so a clean redirect carries that hard-won equity forward instead of leaving it stranded on a dead URL. That is the entire reason the redirect exists. It lets you change your URL structure, move to a new domain, or merge two competing pages into one stronger page, all without resetting the clock.
There is a crawl-efficiency angle too. Clean, direct redirects help search engines spend their crawl budget on live pages instead of wasting requests rediscovering moved ones. And the benefit isn't limited to traditional search. AI answer engines crawl and follow redirects the same way Google does, so a tidy redirect map keeps your pages reachable and citable across both classic SERP results and generative answers. Lose the redirect and you lose visibility in both at once.
How to use 301 redirects without breaking things
Most redirect damage comes from a handful of repeatable mistakes. Avoid these and the tool does its job quietly.
- Redirect to the closest relevant page, not the homepage. A 301 only passes full equity when the destination matches the intent of the old page. Point a retired blue-widget page at your blue-widget category, not at the homepage. Mass-redirecting dead pages to the homepage is treated more like a soft 404, and most of the equity evaporates.
- Flatten redirect chains. When URL A redirects to B, B to C, and C to D, every hop wastes crawl budget and slows the page. Point each old URL straight at its final destination in one hop. After any migration, audit for chains and loops and collapse them.
- Map every URL before a migration. A site redesign, replatform, or domain change is where redirects matter most and break most often. Crawl the old site, export every indexed URL, and map each one to its new home before launch, not after the traffic graph drops.
- Don't redirect through HTTP. Sending users from
http://tohttp://wwwtohttps://stacks three hops and drags on your Core Web Vitals. Redirect straight to the final HTTPS URL. - Keep them in place. Search engines need to recrawl the old URL to process the move, which takes time, and external links keep sending visitors for years. Pull a redirect too early and that traffic and equity are gone. Treat 301s as permanent infrastructure.
- Use the right tool for the job. If both URLs need to stay live for users, you want a canonical tag, not a redirect. A 301 is for when the old URL should genuinely disappear.
The bottom line
A 301 redirect is plumbing, not strategy, and that's exactly why it gets neglected and exactly why it matters. It never shows up in a marketing deck, but it decides whether a redesign, a domain move, or a URL cleanup keeps your rankings or quietly resets them. Done right, it carries years of earned authority onto a new URL with almost nothing lost. Done wrong (a 302 where a 301 belonged, a chain three hops deep, every dead page dumped on the homepage) it leaks traffic so slowly that nobody connects the drop to its cause until months later.
The fix is not complicated, it is just unglamorous: map every old URL to its closest live equivalent, return a true 301, point it there in one hop, and leave it in place. The sites that treat redirects as permanent infrastructure keep their rankings through changes that wipe out the sites that treat them as an afterthought.
Planning a redesign, a replatform, or a domain change, and want to keep the rankings you've already earned? Our technical SEO work starts with a full redirect map so nothing leaks during the move, and our broader SEO service builds on a foundation that holds. Email us at admin@moonsauceagency.com and you'll get a straight read on your current redirects, the chains and dead ends worth fixing, and what a clean migration plan looks like before you launch.
Keep reading: What is a backlink? · Canonical tag · Technical SEO · Back to the glossary
Sources: Google Search Central documentation · Google Search Central: how Google Search works
