A website redesign is one of those projects that looks straightforward from the outside and turns out to have a hundred moving parts. New design, new content, new structure — and underneath it all, a live website that’s currently bringing in enquiries and can’t afford to break.
The uncomfortable truth is that redesigns go wrong more often than agencies like to admit. Not because the new site looks bad, but because something technical gets missed: old URLs aren’t redirected, the staging site gets indexed, tracking stops recording conversions, or pages that used to rank simply vanish from Google. Businesses have relaunched beautiful new websites and watched their organic traffic fall off a cliff the following week.
This checklist is designed to stop that happening. It walks through a redesign in the order the work actually needs doing — from the groundwork before anyone opens a design tool, through to the checks in the days after launch. Use it whether you’re managing the project yourself or briefing an web design agency.
Before You Change Anything: Benchmark and Audit
This is the phase most people skip, and it’s the one that protects everything else. You cannot tell whether a redesign succeeded if you never recorded where you started.
- Record your current performance. Capture organic traffic, top landing pages, conversion rates, enquiry volumes and average time on page from the last 12 months. Screenshot or export it — don’t rely on being able to reconstruct it later.
- Export a full list of your existing URLs. Crawl the site and save every page address. This becomes the foundation of your redirect map, and it’s far harder to recover after the old site is gone.
- Identify your best-performing pages. Which pages bring in the most traffic, rankings and leads? These need special care — sometimes the right decision is to keep their content and URL almost untouched.
- Note your current keyword rankings. You need a before-and-after comparison, especially for the terms driving enquiries.
- Audit what’s actually there. List every page, form, PDF, integration and third-party embed. Redesigns routinely lose a form or a tracking script simply because nobody knew it existed.
- Check what’s broken. Existing 404s, slow pages, mobile issues and thin content are all things to fix rather than carry across.
Define Why You’re Redesigning
“It looks dated” is a reason, but it isn’t a strategy. A redesign without clear objectives tends to produce a prettier version of the same problems.
- Set specific goals. More enquiries? Better conversion rate? Easier updates for your team? Faster loading? Reaching a new audience? Write them down.
- Attach measurable targets where you can, so you’ll know afterwards whether it worked.
- Understand your users. Who visits, what are they trying to do, and where do they currently give up? Session recordings, heatmaps and simply asking your sales team are all useful here.
- Review competitors honestly. Not to copy them, but to understand what visitors are comparing you against.
- Agree what success looks like with everyone involved before design begins. This prevents the late-stage disagreements that derail timelines.
Plan the Structure and Content
Structure decisions made here determine how well the site performs — and how much rebuilding you’ll need later.
- Map your new site architecture. Keep important pages within a few clicks of the homepage, and group related content logically.
- Decide what to keep, merge, rewrite or remove. Merging two thin pages into one strong one is usually better than keeping both. Deleting genuinely useless pages is fine — as long as you handle redirects.
- Preserve URLs where you sensibly can. Every URL change is a small risk. If a page ranks well and the URL still makes sense, leave it alone.
- Plan your content properly. Content is the most common cause of delays. Assign owners and deadlines, and don’t let “we’ll write it later” become the reason launch slips by two months.
- Write for people first. Clear, specific, genuinely helpful copy outperforms keyword-padded filler — both with visitors and with search engines.
- Get your calls to action right. Every key page should make the next step obvious.
Design and User Experience
- Design mobile-first. Most visitors will be on a phone, so design for that constraint and expand upward rather than shrinking a desktop layout.
- Keep navigation obvious. Clever menus that visitors can’t work out are a conversion problem, not a design feature.
- Maintain brand consistency across colours, fonts, imagery and tone.
- Design for accessibility. Sufficient colour contrast, readable text sizes, keyboard navigation, meaningful alt text and clear form labels. It widens your audience and, for many organisations, it’s a legal expectation.
- Optimise images before they go anywhere near the site. Correctly sized, compressed, modern formats.
- Prototype and test with real people before build. Watching three users attempt a task will teach you more than a month of internal debate.
Technical Build and SEO Foundations
This is where a redesign is won or lost. Build these in as you go rather than bolting them on afterwards.
- Keep the staging site out of Google. Password-protect it or block indexing — and make an unmissable note to remove that block at launch. A noindex tag left in place after go-live is the single most damaging redesign mistake, and it’s alarmingly common.
- Build the redirect map. Every old URL that’s changing needs a 301 redirect to its closest new equivalent. Not the homepage — the actual relevant page. This is how you carry your accumulated ranking value across to the new site.
- Preserve page titles and meta descriptions on pages that already perform well, adapting rather than discarding them.
- Keep your heading structure clean — one H1 per page, logical subheadings beneath it.
- Prioritise site speed. Google’s Core Web Vitals measure loading (LCP), responsiveness (INP) and visual stability (CLS). Compressed images, efficient code, sensible hosting and caching all matter.
- Confirm the site is genuinely mobile-friendly, not merely responsive in theory.
- Set up SSL properly, with everything served over HTTPS and no mixed-content warnings.
- Add structured data where relevant — organisation, local business, FAQ, reviews — to help search engines understand your content.
- Generate an XML sitemap and check your robots.txt before launch.
- Carry over your tracking. Analytics, Search Console, conversion goals, call tracking and any ad platform tags. Broken tracking means you lose the data that proves the project worked. For this setting, you can take help from SEO agency near you.
Pre-Launch Checks
Run through this immediately before going live. It’s worth being pedantic.
- Test every form — submit them, and confirm the notification actually arrives in the right inbox.
- Click every link and check every page for broken links, missing images and placeholder text.
- Proofread everything. Fresh eyes catch what the writer can’t see.
- Test across browsers and devices, including older phones.
- Verify the redirect map works by spot-checking your most important old URLs.
- Remove the staging block. Then check it again.
- Confirm contact details, opening hours and legal pages (privacy policy, cookie notice, terms) are present and correct.
- Take a full backup of both the old and new sites.
- Check the cookie consent banner behaves correctly.
- Plan the timing. Launch when your team is available to respond — not at 5pm on a Friday or the day before everyone’s on leave.
Launch Day and the First Week
Going live is the start of the monitoring period, not the end of the project.
- Submit your new sitemap in Google Search Console and request indexing for key pages.
- Crawl the live site immediately to catch broken links, redirect chains or missed pages.
- Confirm analytics and conversion tracking are recording real data.
- Watch Search Console daily for crawl errors, coverage issues and manual actions.
- Monitor rankings and traffic closely. A small dip in the first week or two is normal while Google reprocesses the site; a sustained drop means something needs investigating.
- Fix 404s as they appear — real user behaviour will surface URLs your crawl missed.
- Ask people to use it. Colleagues, customers, anyone. Real usage reveals friction that testing doesn’t.
- Update anywhere your URLs are published — Google Business Profile, social profiles, directories, email signatures and paid campaign destinations.
After Launch: Measure and Improve
- Compare against your benchmarks at 30, 60 and 90 days. This is why the first phase mattered.
- Review actual user behaviour with heatmaps and recordings, and refine the pages that underperform.
- Keep publishing. A new site is a foundation, not a finished product — ongoing content and optimisation are what compound its value.
- Schedule maintenance. Updates, backups, security checks and regular link testing.
Common Redesign Mistakes to Avoid
A few failures come up again and again:
- No redirects, or lazy redirects. Pointing every old URL at the homepage wastes the authority those pages had earned.
- Leaving the site blocked from search engines after launch.
- Ignoring SEO until the site is built, then trying to retrofit it.
- Redesigning around internal taste rather than what users actually need.
- Losing tracking, and with it any ability to prove the investment worked.
- Launching with unfinished content and promising to fix it later.
- Treating launch as the finish line.
Getting Your Redesign Right
The pattern behind every successful redesign is the same: understand what’s working before you change it, plan the structure deliberately, build the technical foundations in from the beginning, and keep watching after launch. The design matters — but what makes a website earn its keep is everything sitting underneath it.
That’s the part worth getting help with. At Giraffe Digital, we’re a B Corp certified Web design agency in Milton Keynes working with B2B and professional services businesses, and because our web design and development team works alongside our SEO and PPC specialists, search performance is designed into a project from day one rather than repaired afterwards.
If you’re planning a redesign and want to protect the rankings and enquiries you’ve already built, get in touch for a conversation about what your site needs.
Frequently Asked Questions
-
How long does a website redesign take?
Most business websites take somewhere between four and twelve weeks depending on the number of pages, the complexity of the functionality, and how quickly content is supplied. Content is usually the biggest variable — projects rarely stall on design.
-
Will a redesign affect my Google rankings?
It can, in either direction. Handled properly — with a complete redirect map, preserved content and technical SEO built in — a redesign usually improves rankings over time. Handled carelessly, it can lose years of accumulated visibility. The redirect map and pre-launch checks are what make the difference.
-
Should I change my URLs during a redesign?
Only where there's a good reason. If a URL is unclear, inconsistent or reflects an outdated structure, change it and redirect properly. If a page ranks well and its URL still makes sense, leave it as it is.
-
How often should a website be redesigned?
Most businesses find a full redesign is worthwhile every three to five years, though continuous smaller improvements are often better than waiting for a big overhaul. The real triggers are business change, poor performance, or a site that's become difficult to update.
-
What's the difference between a redesign and a refresh?
A refresh updates the visual layer — colours, imagery, typography — while keeping the underlying structure. A redesign rethinks structure, content and functionality as well. A refresh is quicker and cheaper; a redesign is what you need when the site isn't working, not just looking tired.
-
Can I redesign my website without losing traffic?
Yes, with planning. Benchmark first, keep your best-performing content, map every redirect, build SEO in from the start, and monitor closely after launch. Traffic loss during a redesign is almost always preventable rather than inevitable.


