Definition
A 301 redirect is an HTTP status code telling browsers and search engines that a URL has moved permanently to a new address. Google treats it as a strong signal to transfer indexing to the new URL. A 302 signals a temporary move and keeps the original URL indexed.

Why it matters
Redirects are where site changes go wrong. A redesign, a platform move or a tidy-up of URLs all produce old addresses that people and search engines still hold. Handle them with 301s and the link equity those URLs accumulated follows them. Handle them badly, or not at all, and it is lost along with the rankings it supported.
The 301 versus 302 question matters because the two codes tell Google opposite things about which URL should be in the index.
How it works
Both are HTTP status codes, defined in RFC 9110, returned by the server before any page is sent. Google's documentation on redirects and Google Search sets out how each is treated.
| Code | Meaning | What Google does |
|---|---|---|
| 301 | Moved permanently | Treats the new URL as canonical and transfers indexing signals |
| 302 | Found, temporary | Keeps the original URL as the one to index |
| 307 | Temporary, method preserved | Equivalent intent to a 302 |
| 308 | Permanent, method preserved | Equivalent intent to a 301 |
The practical rule is simple. If the old URL is never coming back, use a 301. If it genuinely is temporary, such as a page diverted for a sale that ends next week, use a 302. Using a 302 for a permanent move is the common error, and it leaves the old URL in the index competing with the new one, which creates the duplicate content situation a canonical tag exists to resolve.
Worked example
A redirect map is the deliverable for any migration. One row per old URL, pointing at the closest equivalent, with the status each one returns:
/old-services/seo-packages/seo301/blog/2019/seo-tips/glossary/seo-services301/products?id=42/products/blue-widget301/summer-sale-2025/sale302

The last row is deliberate: a sale page that genuinely comes back next year is one of the few honest uses of a 302.
Two rules make the difference between a map that works and one that loses traffic. Point at the closest relevant page, not at the home page: a blanket redirect of everything to the root is treated as a soft 404 and keeps nothing. And point directly at the final destination rather than at another redirect, because each hop adds latency and chains can be abandoned.
Common mistakes
- Using 302 for a permanent move. The old URL stays indexed and the new one struggles to replace it.
- Redirecting everything to the home page. Google documents this as being treated like a 404, so the value is not preserved.
- Chaining. A to B to C. Collapse it to A to C.
- Forgetting the sitemap. Old URLs should leave the XML sitemap; redirected URLs do not belong in it.
- Redirecting instead of fixing. A redirect is right when content moved. When content was deleted and has no equivalent, a 404 or 410 is the honest answer, and Google handles those cleanly.
How long to keep them
Indefinitely, where practical. Google consolidates signals to the new URL within weeks of recrawling, but external links to the old address do not expire, and a visitor following a five year old link is still a visitor. Removing redirects a year later is a common way to quietly lose the links a migration was careful to preserve.