301 Redirect
Tells browsers and search engines that a page has permanently moved to a new address.
A 301 redirect is the web's version of permanent mail forwarding. The browser is told "this page has moved — go there instead, and remember it for next time." The visitor lands at the new page without noticing the detour.
If a bakery renames itself from Joe's Bread Co. to Joe's Bakery and moves to joesbakery.com, every old link, search result, and bookmarked page should land on the new site. A 301 tells browsers and search engines the change is permanent — technically, an HTTP response with status code 301 Moved Permanently and the new address attached.
301 vs 302
301 and 302 differ in one practical way: whether browsers and search engines remember where the redirect went.
301 vs 302 — what actually happens
- First request
- Server returns 301 + Location
- Browser cache
- Cached, possibly indefinitely
- Second request
- Skipped — browser uses cached destination
- Search engines
- Drop original from index, transfer ranking to destination
- Hard to undo?
- Yes — caches must expire first
Use for
- · Renamed page or slug
- · Domain migration
- · HTTPS upgrade
- First request
- Server returns 302 + Location
- Browser cache
- Not cached — every request hits the server
- Second request
- Goes back to original URL, server decides again
- Search engines
- Keep original URL in index
- Hard to undo?
- No — change destination anytime
Use for
- · Conditional routing (country, device, time)
- · Short links you may edit later
- · Temporary maintenance pages
The single biggest practical difference: 301s are cached by browsers and search engines, 302s aren't. If the destination might change, you want a 302.
The labels "permanent" and "temporary" are a little misleading. The real question: should browsers and Google stop checking the original URL? If yes, use 301. If the destination might change later or differs by visitor, use 302.
Try it
Three questions and we'll point you at the right status code.
Try it — 301 or 302?
Do all visitors get sent to the same destination?
If different visitors go to different URLs (by country, device, time, randomly, etc.), answer No.
Why "permanent" is hard to undo
Once a browser sees a 301, it's allowed to remember the new address for a long time — sometimes hours, sometimes until the user clears their history. Google does the same: after a few crawls, the old URL drops out of search results and the new one inherits the ranking signals.
That memory is what makes 301s both powerful and risky. Old links keep working and search ranking transfers cleanly. But if you change your mind three weeks later, browsers that already learned the redirect will keep going to the new destination regardless. There's no good way to "undo" a 301 once it's spread.
If there's any chance the destination might change, use a 302.
When you do want 301
301s are the right call when you control both ends of a permanent move:
- Moving domains. Every page on
oldbrand.compermanently forwarded tonewbrand.com. - Renaming pages.
/about-uspermanently renamed to/aboutafter a website rewrite. - Switching to HTTPS. Sending visitors from the old
http://version to the securehttps://one. - Picking one URL format. Deciding whether
example.com/pageorexample.com/page/is the official version, and forwarding the other.
In each case, a 301 hands your search ranking to the new URL and lets browsers stop visiting the old one.
Why most short links use 302
Every short link is a redirect, but most short-link services use 302, not 301. Two reasons:
- You might change the destination later. A 302 picks up the change immediately for every visitor. A 301 leaves browsers stuck on the old destination because they'd remembered it.
- Different visitors, different destinations. A Redirect by Country or Redirect by Device link sends people to different places depending on who they are — exactly what 302 is designed for.
The exception: moving from one short-link service to another. Old links permanently forwarded to new ones, no further changes planned — that's a 301.
What a redirect chain looks like
Most redirects are invisible — you click a link and you're somewhere new. Behind the scenes, the browser may have followed one redirect or several.
See it — recorded redirect chains
Pre-recorded examples
A typical short link issues a single 302 redirect to its destination.
- 1302Found
https://nimble.li/sale
- Browser follows the Location header to the next URL
- 2200OK Final destination
https://example.com/products/spring-sale?utm_campaign=spring
1 hop · finished at example.com
To inspect a real URL, WhereGoes traces the full chain — including JavaScript and meta-refresh redirects that simpler checkers miss.
References
The formal behavior of 301 is defined in RFC 9110 §15.4.2.