Every studio has seen the horror story. A business spends six months and a serious budget on a beautiful new website, launches it on a Friday, and by the following month organic traffic is down by half. Nobody broke anything on purpose. The designers designed, the developers developed, and the search engine quietly lost track of pages it had spent years learning to trust. Surveys of businesses that redesigned without an SEO plan put the casualty rate around 60 per cent experiencing significant traffic drops within three months. This checklist exists so that’s never you.
Key takeaways
- Most “we need a redesign” problems are actually refresh problems; know which one you’re solving before spending redesign money.
- Rankings are attached to URLs and content, not to your brand. Change either without a plan and Google starts from scratch.
- The 301 redirect map is the single load-bearing document of the entire project. Every old URL goes somewhere, no exceptions.
- The two weeks after launch decide whether small problems stay small. Monitoring is part of the project, not an afterthought.
First: do you actually need a redesign?
Honest answer from people who sell redesigns: sometimes you don’t. A redesign is warranted when the problem is structural. The site can’t support what the business has become, the platform is a dead end, the information architecture fights every new page you add, conversion is broken at the layout level, or the brand itself has genuinely moved on. Those are rebuild problems.
“It looks a bit dated” is usually a refresh problem: new typography, updated colour, better imagery, a tightened homepage, all on the existing structure. A refresh costs a fraction of a rebuild and carries close to zero SEO risk, because the URLs and content that Google ranks don’t move. Plenty of the “less perfect on purpose” personality we covered in our piece on human-first web design can be layered onto an existing site without touching a single URL. Spend redesign money on redesign problems.
Phase 1: Before anyone opens a design tool
Crawl and inventory everything
Run a full crawl of the current site so you hold a complete list of every URL that exists. This list is the raw material for the redirect map later, and you can’t redirect what you never knew you had. Old landing pages, forgotten PDFs, that campaign microsite from 2021: all of it.
Identify what’s earning its keep
Pull analytics and Search Console data and mark the pages that actually drive traffic, rankings and conversions. These are the crown jewels, and the redesign’s first commandment is written about them: thou shalt not delete, merge, gut or “simplify” a page that’s earning, however inconvenient it is for the new sitemap. When a top page must change, its content, headings and target keywords travel intact to wherever it lands.
Benchmark the before
Record current rankings for your key terms, monthly organic traffic by page, and Core Web Vitals scores. Post-launch, this benchmark is how you distinguish “normal migration wobble” from “something’s on fire,” and without it every dip becomes a mystery and an argument.
Phase 2: Decisions that protect rankings
Keep URLs unless there’s a real reason not to
Rankings and authority are attached to specific URLs. The safest migration is the one where nothing moves: same addresses, new clothes. Change a URL only for a genuine structural or strategic reason, and accept that each change spends a little trust that redirects mostly, not entirely, preserve.
Build the 301 map like your traffic depends on it
For every URL that does change, create a line in a spreadsheet: old URL, new URL. A 301 is the permanent signal that tells Google a page has moved and to transfer its accumulated authority to the new address. Not a 302, which says “temporary” and passes authority poorly. Map each old page to its closest relevant new equivalent, never lazily to the homepage, and give retired pages a sensible destination such as their parent category, with the homepage as a genuine last resort. Every single old URL goes somewhere. A crawler pointed at your old URL list after launch should find zero 404s among pages that mattered.
Don’t design away the SEO furniture
Title tags, meta descriptions, H1s, heading structure, internal links, image alt text: this is where years of optimisation live, and redesigns are where it quietly dies, because a fresh template ships with fresh empty fields. Carry every element across deliberately, page by page, and keep the internal links between pages intact; a beautiful new site whose pages no longer link to each other has amputated its own link equity. Minimalist layouts that delete “all that text” are deleting the content the rankings stood on; find it a home in the new design instead.
Phase 3: Build and pre-launch
Build on a staging environment blocked from search engines, and put “remove the noindex” at the top of the launch checklist in bold, because launching a gorgeous site that’s still telling Google to ignore it is the oldest facepalm in the industry, and it still happens every week somewhere.
On staging, before anyone celebrates: implement and test the full redirect map; verify titles, metas, H1s and alt text carried over; check the site on phones first, since Google indexes mobile-first and a desktop-led design process drifts desktop-heavy without supervision; and test speed. A redesign is the cheapest moment you’ll ever have to fix Core Web Vitals, because performance decisions are still decisions rather than retrofits: compressed images, restrained scripts, and a hero section that loads like it means it. New sites should launch faster than what they replace, and it’s worth being loud about that requirement early, because heavy animation and speed budgets negotiate badly late. If the build brief includes AI-assisted tooling, our take on where that helps and where it doesn’t is in AI in web design.
Phase 4: Launch day and the two weeks after
On the day: remove the noindex, confirm the redirects are live on the production domain, update the XML sitemap to the new URL set, and submit it in Google Search Console. That combination, redirects plus navigation plus sitemap all telling the same story, is how search engines understand the change as fast as they’re able to.
Then watch, daily, for two weeks. Search Console’s coverage and page-indexing reports surface crawl errors and 404s; fix them the day they appear. Recrawl your old URL list to catch redirect gaps. Compare rankings and traffic against your Phase 1 benchmark, expecting some volatility for a few weeks even in a clean migration, and investigating anything that keeps falling past that window. The difference between a site that dips 10 per cent for a fortnight and one that loses half its traffic for a year is rarely the size of the mistake; it’s how fast somebody noticed.
The condensed checklist
- Confirm it’s a redesign problem, not a refresh problem
- Crawl the current site into a complete URL inventory
- Flag high-performing pages as protected content
- Benchmark rankings, traffic and Core Web Vitals
- Keep URLs where possible; map every change with a 301
- Migrate titles, metas, headings, alt text and internal links deliberately
- Build on noindexed staging; test redirects, mobile and speed there
- Launch: remove noindex, verify redirects, submit new sitemap in Search Console
- Monitor daily for two weeks against the benchmark; fix errors same-day
Quick answers
Does a website redesign affect SEO?
Almost always, and some volatility around launch is normal even in a clean migration. Whether the effect is a temporary wobble or a lasting loss depends on URL handling, redirects and content preservation, which is what this checklist controls.
How long does it take rankings to recover after a redesign?
A well-executed migration typically settles within a few weeks as search engines recrawl and reconcile the changes. Drops that persist beyond that window usually point to a specific fixable problem: missed redirects, lost content or a lingering noindex.
Should I use 301 or 302 redirects?
301, always, for a permanent move. It passes accumulated ranking authority to the new URL. A 302 signals a temporary change and transfers that authority poorly, making it the wrong tool for a redesign by definition.
Can I change my URLs during a redesign?
You can, with a one-to-one 301 map, and each change still spends a little trust. The professional default is to keep URLs identical wherever possible and change them only for genuine structural or strategic reasons.
Redesign or refresh: how do I decide?
If the problem is structural (architecture, platform, conversion at the layout level, a genuinely changed brand), redesign. If the problem is cosmetic, a refresh on the existing structure delivers the facelift at a fraction of the cost and close to zero SEO risk.
None of this is glamorous, which is exactly why it gets skipped, and exactly why the businesses that do it keep their traffic while the launch-and-pray crowd writes the horror stories. A redesign done properly comes out the other side better-looking and better-ranking at the same time; the two were never actually in competition. And if you’d rather have people who’ve run this playbook before handle the unglamorous parts, that’s rather the point of a studio: bring us the ambition, we’ll bring the spreadsheet, at FearNaught that trade has always seemed fair.