A 301 redirect sounds more technical than it actually is. In plain English, it tells browsers and search engines: this page permanently moved over here instead. Google treats permanent redirects as a strong canonical signal, meaning they help clarify which URL should be the one search engines index and rank.
That is why 301s matter so much during migrations and restructures. And it is why doing them badly, or skipping them altogether, can cost you rankings you spent years building.
Why do you need a 301 redirect?
Think about what happens when a page moves and there is nothing in place to handle the old URL. Someone clicks an old backlink. Google tries to crawl the original path. The page is gone. Dead end. Any equity that URL had built up goes nowhere.
A 301 redirect prevents that when there is a relevant new destination. Google specifically recommends them for site moves, domain changes, URL restructures, and consolidating duplicate content.
The most common situations that call for a 301
- A page URL changed permanently after a redesign or restructure
- You moved to a new domain
- You merged or consolidated pages
- You removed a page that has a close replacement
- You are cleaning up old URLs from a migration or rebrand
This is also where orphan pages and redirects overlap. If you have a disconnected page that no longer deserves to exist and there is a strong replacement, a 301 is often the cleanest fix. For the full picture on that, read What Are Orphan Pages?
What does a 301 redirect do for SEO, GEO, and AEO?
At the simplest level, it keeps people and search engines from hitting dead ends. Beyond that, it tells Google which URL should now be treated as canonical for that content. That matters for traditional rankings, but it also matters for GEO and AEO: if AI systems are trying to surface the right, current version of your content, messy redirect logic or stale URLs make that harder.
301 vs. 302: what is the actual difference?
Moved for good. Google treats this as a strong canonical signal. Use it when the change is truly permanent.
Moved for now. Google treats this as a weak canonical signal. Use it when you genuinely plan to bring the original URL back.
I see 302s used where 301s should be all the time, usually because someone grabbed the first redirect option in their CMS without thinking about it. If the move is permanent, use the permanent redirect. The signal matters.
What about redirects in the sitemap?
Your XML sitemap should list the final canonical URLs you want indexed. Not the old ones that now redirect. Google says to update sitemaps with new URLs after a migration, and having redirected URLs sitting in your sitemap is a common post-migration issue that creates unnecessary confusion.
The goal is simple: your sitemap points straight to live, indexable destination URLs, not URLs that bounce somewhere else.
What if there is no good replacement page?
Then do not force a redirect. Google's guidance is clear that if content is removed and there is no replacement with similar content, a proper 404 or 410 is often the better answer. A 404 is not always a problem. A bad redirect to an unrelated page is usually worse than letting the URL return a clean 404.
Redirect to the closest relevant match, not just the homepage. Sending every dead URL to the homepage is one of the worst redirect habits I see in the field.
Redirect mistakes worth knowing about
URL A redirects to B, then B redirects to C. Every hop adds latency and dilutes the signal. Point old URLs directly to the final destination.
URL A redirects to B, B redirects back to A. Crawlers get stuck, users see errors. These need to be found and fixed immediately.
Every deleted page sending to the homepage is a signal to Google that the destination is relevant. It is not. A clean 404 is often better than a lazy redirect.
Even when the redirect works, update your internal links so they point to the final URL. Redirects are a safety net, not a reason to leave your site architecture messy.
301 redirects are not complicated in concept, but they are easy to get wrong at scale. The key is having a clear process before anything moves: know what you have, map where it is going, use permanent redirects for permanent moves, keep them out of the sitemap once the new URL is live, and do not redirect to irrelevant destinations just to avoid a 404.
Frequently asked questions
A 301 redirect permanently sends users and search engines from one URL to another. Google treats it as a strong canonical signal, meaning it helps clarify which URL should be ranked and indexed.
Use one when a page has moved permanently and there is a relevant new destination for the old URL. Do not use one just to avoid a 404 when there is no good replacement.
Usually no. Your sitemap should list the final canonical URLs you want indexed, not redirected ones.
A 301 is permanent. A 302 is temporary. If the move is truly permanent, use a 301. Google treats them differently as canonical signals.