301 Redirects for SEO: What to Get Right
A 301 redirect passes most ranking signal to its target when the target is the closest live match. Chains and lazy homepage redirects throw that signal away.
A 301 redirect tells browsers and search engines that a page has moved permanently, and it passes nearly all of that page's ranking signal to the new URL. Use one whenever a URL changes for good, and point it at the closest live equivalent, not a generic homepage.
Redirects are one line item on a much longer technical SEO checklist, but they are the one most likely to cost you traffic in a single afternoon if you get them wrong during a migration.
On this page
What is a 301 redirect and when do you need one?
A 301 redirect is a server response that tells a browser or crawler a URL has moved permanently to a new address. Google's own guidance treats it as the clearest signal you can send that a destination should take over the source's ranking history [1].
You need one whenever a URL stops resolving for good: after a page rename, a category merge, a domain change, or a full site migration. The redirect is not optional in any of these cases — without it, every inbound link and every indexed reference to the old URL just points at a dead page, and you lose whatever authority that URL had built.
The common mistake is treating redirects as an afterthought, written the day the old page goes down instead of mapped in advance. By then nobody remembers which old URL matched which new one, and the map gets built from memory instead of from a real list.
What's the difference between a 301 and a 302 redirect?
A 301 says the move is permanent: treat the new URL as the real one and update indexes, bookmarks and links accordingly. A 302 says the move is temporary: keep the original URL as the canonical one and expect it back.
| Situation | Use |
|---|---|
| Page permanently renamed or merged | 301 |
| Site migrated to a new domain | 301 |
| A/B testing an alternate URL temporarily | 302 |
| Maintenance page shown for a few hours | 302 |
| Country or device redirect that should not replace the original | 302 |
Getting this backwards is the single most common mistake in this area. A 302 used for a permanent move tells search engines to keep the old URL as the canonical one, which means the new URL never fully inherits its ranking signal — sometimes for months, because nothing forces a re-evaluation until the crawler happens to revisit both pages.
How do you map redirects during a migration?
Build the map before you touch anything live, as a spreadsheet with one row per old URL and its exact new target. Guessing the target after the old page is already gone is how homepage-redirect mistakes happen.
Export every indexed and linked URL
Pull the list from your CMS, your XML sitemap, Google Search Console's coverage report and your analytics' top-landing-pages report. Any one of these alone will miss URLs the others catch.
Match each one to its closest live equivalent
A renamed product goes to its new page. A removed product goes to its category, not the homepage. A merged article goes to whichever surviving article covers the same topic best.
Write the rules at the server or edge, not in application code
A redirect handled at the CDN or web server responds in one hop and one request. One implemented client-side in JavaScript makes the browser load the old page first, which is slower and less reliable for crawlers.
Test every rule against the live map before cutover
Request each old URL with a tool that shows the status code and final destination, and confirm it is a single 301 straight to the intended target.
Why do redirect chains hurt SEO?
A chain is two or more redirects fired in sequence before the browser reaches the final page: A redirects to B, which redirects to C. Each hop adds latency, and most tools and some crawlers stop following after a handful of hops, which means the final destination may never get credited at all.
Chains accumulate quietly. A page gets renamed once, redirected. It gets renamed again a year later, and someone adds a second redirect on top of the first instead of updating the first one to point straight at the current URL. After a few migrations, popular old URLs can be three or four hops from anything live.
The fix is mechanical: whenever you add a new redirect, check whether its target is itself a redirect, and if it is, update your new rule to point straight at the final page instead. Periodically crawling your own redirect rules and flattening any chain longer than one hop is worth doing on its own schedule, separate from any migration.
How do you handle redirects at scale?
A hand-written rule per URL works for a few dozen pages. Past a few hundred, write pattern-based rules instead, so one rule covers a whole class of old URLs rather than a spreadsheet row per page.
An e-commerce site retiring an old category structure, for example, can usually redirect /old-category/* to /new-category/* with a single wildcard rule instead of mapping every product one by one, as long as the URL segments after the category slug stay identical. Where they do not — because the new site renamed slugs too — you still need a real mapping table, just for the exceptions rather than every URL.
Two failure modes show up specifically at scale. The first is a rule that is too broad and accidentally redirects URLs it should have left alone — a wildcard meant for one section that also matches an unrelated section sharing part of the same path. The second is a rule order problem: most redirect engines apply rules in sequence and stop at the first match, so a broad rule placed above a specific one can swallow traffic the specific rule was meant to handle. List narrow, specific rules before broad, wildcard ones, and re-test the full set any time you add a new rule rather than assuming the new one is isolated from the rest.
What happens if you skip the redirect entirely?
The old URL starts returning a 404, and every inbound link pointing at it stops working. If the page had any external links, that authority does not transfer anywhere — it is simply lost, because there is no signal connecting the old URL to a successor.
This is worse than it sounds for a URL that never ranked particularly well on its own but happened to receive a handful of links from other sites over the years. Those links were quietly propping up the domain's overall authority, and a silent 404 removes that contribution with nothing replacing it.
If you genuinely intend to remove content with no replacement, a 410 (Gone) is more honest than either a bare 404 or a fake redirect to an unrelated page, and it tells crawlers to stop trying that URL rather than to keep checking back.
How do you verify redirects are actually working?
Request each URL directly and read the response, rather than trusting that a browser eventually landed on the right page — a browser follows the whole chain silently and shows you only the end result.
Check the status code, not just the destination
Confirm the response is a genuine 301, not a 302 mislabelled in a CMS setting or a client-side redirect that returns a 200 while JavaScript sends the browser elsewhere.
Follow the full chain
A tool that reports every hop, not just the first or the last, will surface chains you did not know existed.
Re-check a sample after each future migration
Old redirects can silently break when a platform changes, a CDN rule gets rewritten, or a rules file is regenerated without preserving every entry.
Verification catches the mistakes a spreadsheet review misses — a mistyped target, a rule applied to the wrong URL pattern, a redirect that only fires for some devices or locales. None of those show up until someone actually requests the URL.
What else should you check at the same time?
Redirects rarely fail in isolation during a migration. While you are rebuilding the map, confirm that canonical tags on the surviving URLs point at themselves and not at whatever they replaced, that your XML sitemap lists only live, redirect-free URLs, and that any paginated series you redirected still resolves page by page rather than collapsing everyone onto page one.
Questions people also ask
Does a 301 redirect lose ranking value?
Google treats a 301 as a strong signal that the destination replaces the source, and it consolidates most signals there over time. Some loss is normal during the transition; a permanent large drop usually means the target is a poor match for the old page, not that redirects are inherently lossy.
Should I redirect to the homepage if I can't find a match?
No. A homepage redirect tells both users and Google that the old content is gone, not replaced, which is closer to a soft 404 in effect. Redirect to the nearest live equivalent — a parent category, a merged article, a current product — even if it is not a perfect match.
How long do I need to keep old redirects live?
Indefinitely for anything that earned external links or still gets direct traffic. Removing a redirect turns it back into a 404, and old links pointing at it will start failing the moment you do, sometimes years after the migration.
What's the difference between a 301 and a 302 redirect?
A 301 says the move is permanent and should be treated as the new address; a 302 says it is temporary and the original URL should stay indexed. Use a 302 only when you plan to restore the original URL, such as a short maintenance redirect.
Can too many redirects slow down my site?
Each redirect hop adds a round trip before the browser reaches real content, which shows up in load time metrics. Two or three hops is a minor cost; chains of five or more are worth fixing on performance grounds alone, separate from any SEO effect.
Sources
- Redirects and Google Search — Google Search Central (checked 22 September 2026)
- HTTP redirections — MDN Web Docs (checked 22 September 2026)
Get your redirect map audited before your next migration
Book a free 30-minute consultation with Ibrahem and Jeremy. We look at your site while we talk, and you leave with a prioritised plan.
Who wrote this
Ibrahem HelalCo-founder
Leads strategy and delivery.
Works on: SEO, GEO
Reviewed before publishing by Jeremy Zava, Co-founder.
- Technical SEO: the complete checklist for 2026Technical SEO makes sure search engines and AI crawlers can reach, render and index your pages. This checklist covers every layer, in the order to fix it.
- Canonical Tag Mistakes and How to Fix ThemThe canonical tag mistakes that quietly split ranking signal across duplicate URLs, and how to audit and fix them before they cost you traffic.
- XML Sitemaps: How to Get Them RightAn XML sitemap lists the URLs worth crawling. Get the format, the sitemap index and the submission step right, or search engines mostly ignore it.
- Pagination SEO: A Practical GuideHow to handle paginated pages, rel=next/prev, indexing decisions and infinite scroll so a series of listing pages doesn't compete against itself.