A large UK retailer spent over £7.6 million redesigning their website. Their SEO consultants handed over a detailed map of which old URLs should redirect to which new ones. The IT team rejected it. In the first month after launch, the company lost roughly £3.8 million in revenue — about $5 million — because search traffic to the old pages simply stopped working (see our deeper dive on why poorly planned website migrations lose traffic). That's not a hypothetical. That's one line item in a spreadsheet somewhere, and it happened because of something as unglamorous as a redirect.
If you're planning any kind of website move — a redesign, a rebrand, a platform switch (such as a WordPress to Webflow migration) — you're going to run into the term "301 redirect." This guide explains what it actually is, what it can and can't do, and how to get through a migration without becoming the next case study.
What a 301 Redirect Actually Is
A 301 redirect is a signal your web server sends to browsers and search engines that says: this page has moved permanently, and here's the new address. Someone clicks an old link or a bookmark, and instead of hitting a dead page, they land on the current one automatically. Behind the scenes, "301" is just the HTTP status code for "moved permanently" — the same numbering system that gives you the dreaded "404" for a missing page.
The reason this matters beyond user convenience is search engines use that signal too. When Google's crawler hits a 301, it updates its index to treat the new URL as the authoritative version and — under the right conditions — transfers most of the ranking value the old page had built up. That's the theory, and it's mostly true. The nuance is in that phrase "under the right conditions," which is where most migrations quietly go wrong.
There's also a persistent myth worth killing outright: for years, SEOs believed Google docked a percentage of "PageRank" every time a 301 fired, so redirects were treated as a leak you just had to accept. Google has since clarified that this isn't how it works today — a properly configured 301 doesn't cost you a fixed tax on rankings. What actually costs you is everything downstream of a sloppy setup: redirect chains, wrong destinations, and pages that Google decides aren't really equivalent to what used to be there.
301 vs. 302: The Difference That Actually Matters
This is the one technical distinction worth understanding, because getting it backwards is one of the most common migration mistakes.
| Aspect | 301 Redirect | 302 Redirect |
|---|---|---|
| Meaning | Permanent move | Temporary move |
| SEO value transfer | Yes — passes ranking signals to new URL | No — search engines keep indexing the original URL |
| When to use it | Redesigns, rebrands, permanent URL changes, platform migrations | A/B tests, maintenance pages, genuinely short-term swaps |
| Common mistake | N/A | Leaving a 302 in place for months, hoping it "counts" as permanent |
If your developer or platform defaults to a 302 during a redesign — which happens more often than you'd think, especially with certain e-commerce platforms — you can do everything else right and still lose ground, simply because you used the wrong code for a permanent change.
Reality Check: What Redirects Can and Can't Save You From
Here's where a lot of marketing copy overpromises. Vendors selling redirect plugins or migration services will sometimes imply that a correctly mapped 301 is a guarantee — set it up right and your traffic is safe, full stop. That's not the honest picture.
Industry data on this is sobering. One technical SEO firm's analysis found only about 1 in 10 website migrations actually improve rankings afterward — the other 9 either hold steady in the best case or lose ground. A separate breakdown from a migration-focused agency put the range at 60–80% of migrations resulting in significant traffic loss, with recovery often taking 6 to 12 months. Even well-planned migrations aren't immune: one widely cited agency benchmark expects a 10% traffic dip in the first 30 days as completely normal, even when everything is done correctly, simply because search engines need time to recrawl and re-index.
The genuinely bad outcomes tend to share a pattern, and it's rarely "we forgot redirects existed." It's usually one of these:
- Wildcard or blanket redirects. Sending every old URL to the new homepage instead of its actual equivalent. One documented case saw a site's search visibility collapse by roughly 99% in UK rankings after old pages were funneled through a blanket redirect that Google essentially read as content having vanished.
- Redirect chains. Page A redirects to B, which redirects to C. Each hop adds latency and weakens the signal; a widely cited 2016 case study found each additional hop in a chain correlated with a further drop in organic traffic to that page.
- 1:1 mismatches. Google has been explicit that redirects only reliably pass value when the destination is a genuine replacement for the original. Redirect an expired product to a vaguely similar one, and Google may treat it as a soft 404 and pass along little to nothing.
- No pre-launch testing. A CMS replatform in one documented case mis-redirected over 15,000 URLs, changed URL case-sensitivity, and dropped entire product categories without redirecting them — Google effectively treated the relaunched site as brand new, and daily organic clicks fell from the 40–70 range to near zero within two months.
The flip side is just as real, and it's the part that gets buried under the horror stories: migrations planned properly do work. One retail case study maintained organic traffic and grew visibility more than 50% after a well-executed platform move. Another company merging three domains during a simultaneous rebrand tested nearly 1,000 redirects before launch and ended up exceeding traffic expectations by 14.5% a year later. The difference between the disaster stories and the success stories isn't luck — it's whether redirects were planned as part of the project from day one or bolted on three weeks before launch (refer to our pre-launch website redesign SEO checklist for the full list of safeguards).
How to Actually Do This (Without Hiring a Developer for Every Step)
- Crawl and inventory your current site. Before anything changes, get a full list of every existing URL — not just the pages you remember, but everything Google has indexed. Free tools like Google Search Console's coverage report, or a crawler like Screaming Frog, will surface this.
- Identify your highest-value pages first. Not every page needs equal attention, but your top traffic drivers and highest-ranking pages absolutely do. Cross-reference your analytics against your search rankings to find these before you touch anything.
- Build a 1:1 redirect map. For every old URL that's changing, document its exact new destination in a spreadsheet — old URL, new URL, nothing left to guess. Avoid the temptation to redirect a batch of similar pages to one generic "closest match" unless there truly is no equivalent.
- Set every redirect to 301, not 302, unless it's genuinely temporary. This is the single most common technical error in DIY migrations, and it's the easiest one to check.
- Test before you launch, not after. Deploy the new site to a staging environment first and verify every redirect actually resolves correctly — no chains, no loops, no accidental 404s.
- Update your internal links to point directly to new URLs. Don't rely on the redirect to catch internal links that could just be updated correctly the first time; every internal link that still points to an old URL and relies on a redirect is a small extra tax on your site's crawl efficiency.
- Monitor daily for the first two to four weeks. Watch Search Console for crawl errors and 404 spikes, and check your analytics against pre-migration baselines. The businesses that avoid disaster catch problems within hours, not the following Wednesday.
If you're on WordPress, the free Redirection plugin (2 million+ active installs, genuinely free with no paid tier) handles most small-business needs — bulk redirects, 404 logging, CSV import/export. If you're already paying for Yoast SEO Premium (around $99/year) or All in One SEO's Pro plan (around $199.60/year), both bundle in a capable redirect manager, so you may not need a separate tool at all. Shopify and other hosted platforms typically include a basic redirect tool in their admin panel, though it's worth checking whether it handles bulk CSV imports if you're moving more than a handful of pages.
Quick Stats: Migration Risk at a Glance
| Metric | Figure |
|---|---|
| Migrations that improve rankings afterward | ~10% |
| Migrations resulting in significant traffic loss | 60–80% (varies by source and migration complexity) |
| "Normal" traffic dip in first 30 days, even done well | ~10% |
| Typical recovery timeline if things go wrong | 6–12 months |
| Documented worst-case revenue loss (single case) | ~$5M in month one |
| Documented best-case outcome (well-planned) | Traffic exceeding pre-migration expectations by 14.5%+ |
The spread between those best and worst outcomes isn't random. It tracks almost exactly with whether redirects were planned from the start or handled as an afterthought.
When This Is a DIY Job vs. When It Isn't
A straightforward blog URL change on a 15-page site with modest traffic is well within reach of a business owner with an afternoon and a free plugin. A full platform migration — especially one involving a domain change, a CMS switch, or a simultaneous rebrand — is a different animal, and it's exactly where the case studies above turned into cautionary tales.
A decent gut check: if you can count your total indexed pages on two hands, or your organic traffic is genuinely modest, following the checklist above yourself is reasonable. If you have hundreds of pages, meaningful organic traffic you rely on for leads, or you're changing more than one major variable at once (new domain and new platform and a rebrand, say), that's the exact combination that's burned larger companies with bigger budgets than yours. Layering multiple risky changes into one launch is how a manageable project becomes a five-figure traffic problem.
This is usually where DIY setups hit their ceiling — not because the redirect itself is hard to set up, but because getting the mapping, testing, and monitoring right across a real site takes more attention than a side task allows. If your redesign is more than a cosmetic refresh, it's worth having someone who's done this before at least review your redirect plan before you launch — a second set of eyes here is cheap insurance against a mistake that's expensive to unwind. It's also worth noting that redesigns and migrations are frequently bundled together: if your site needs both a visual overhaul and a proper technical migration plan, that's the kind of project Brandywebs builds custom, starting from $999, with the redirect mapping handled as part of the process rather than an afterthought.
Where Brandywebs Fits In
Most of the businesses that end up needing this comparison aren't trying to become AI infrastructure experts — they're trying to stop losing $126,000 a year to a phone that rings out. If you're at the stage where you know missed calls are costing you but the platform landscape feels like it needs a translator, that's a reasonable place to stop and get a second opinion before committing to a monthly plan.
Brandywebs handles the platform selection, the setup, the calendar and CRM integration, and the testing so the agent actually works on day one instead of month three. And if the missed-call problem is really a symptom of an outdated website that doesn't make booking or contacting you easy in the first place, that's worth fixing at the same time — custom website builds start at $999, and a voice agent connected to a site that converts is a different outcome than one bolted onto a site that doesn't (see our guide on how to identify an outdated website).
Get a free quote from Brandywebs →
Bottom Line
A 301 redirect is a simple tool doing a specific job: telling search engines and visitors that a page moved permanently, so link value and traffic follow it to the new address. Used correctly, it's genuinely one of the least dramatic parts of a website migration. Used carelessly — wildcarded, chained, or skipped entirely — it's the single most common reason companies watch years of search visibility disappear in a matter of weeks.
The honest takeaway from the data isn't "redirects are scary." It's that migrations succeed or fail based on planning, not luck. The businesses that tested nearly a thousand redirects before launch didn't get lucky — they built in the time to catch problems before they went live. The ones that lost 50-99% of their visibility overnight usually skipped exactly one of the steps above.
If you're planning a redesign, a rebrand, or a platform switch and you're not sure where your current site stands or what a proper migration plan looks like for your situation, that's worth a second opinion before you flip the switch.
Get a free quote from Brandywebs →
FAQs
Do I need a developer to set up a 301 redirect? No, not for most small business needs. WordPress plugins like Redirection (free) or the redirect managers bundled into Yoast SEO Premium and AIOSEO let you set up redirects through a simple dashboard. Shopify and most other hosted platforms include a basic redirect tool in their admin panel. You'd typically only need a developer for large-scale migrations with thousands of URLs or server-level redirect rules.
Will a 301 redirect hurt my SEO rankings? A properly configured 301 pointing to a genuinely equivalent page generally preserves most of your ranking value, though some temporary dip while search engines recrawl and re-index is normal and expected — often cited around 10% in the first month even in well-executed migrations. What actually hurts rankings is redirecting to an irrelevant page, chaining multiple redirects together, or using a 302 instead of a 301 for a permanent change.
How long does it take for a 301 redirect to fully work for SEO? The redirect works instantly for visitors clicking the link. The SEO impact is slower — search engines typically need days to weeks to recrawl the old URL and update their index, and for competitive keywords it can take two to three months before rankings fully transfer to the new URL.
What's the difference between a 301 and a 302 redirect? A 301 tells search engines a page has moved permanently, and ranking value transfers to the new URL. A 302 signals a temporary move, so search engines keep indexing the original URL and don't pass along ranking value. Use a 301 for redesigns, rebrands, and permanent URL changes; reserve 302s for genuinely short-term situations like A/B tests or maintenance pages.
How many redirects can I have before it hurts my site? There's no hard cap, but the real risk is redirect chains (Page A to B to C) rather than the raw count. Each additional hop in a chain adds page-load latency and can weaken how much SEO value transfers. A site with a few hundred well-mapped, direct redirects is fine; a site with long chains or loops is the actual problem.
What happens if I redesign my website without setting up redirects? This is how businesses lose the majority of their search traffic overnight. Documented cases include a site whose search visibility collapsed by roughly 99% after old URLs were blanket-redirected to a homepage that didn't match the original content, and another where daily organic clicks fell from 40-70 down to near zero within two months of a poorly executed platform migration.
Should I redirect an old product page to a similar but different product? Generally, no. Google has said it only reliably passes SEO value through a redirect when the destination is a true 1:1 replacement for the original page. If a product is genuinely discontinued, it's usually better to let that page return a "sold out" message with a link to a similar product, rather than redirecting it — the redirect may just get treated as a soft 404 anyway.
How much does a website redesign that properly handles SEO migration cost? Industry pricing for a professional small business redesign that includes proper redirect mapping and SEO preservation typically runs a few thousand dollars and up, depending on site size and complexity. At Brandywebs, custom website builds start from $999 — worth getting a free quote to see where your specific project lands.