Topics: Website design & costs
Want this done for your business? Get a fixed quote or book a free 30-minute call.
In this guide
- Do you need a redesign, a refresh or just fixes?
- What should you audit on your current site first?
- How do you protect rankings and links during a redesign?
- How do you plan content and structure before design starts?
- What should you test before and after launch?
- How do you measure whether the redesign worked?
- Frequently asked questions
- Get a second pair of eyes on your redesign
Quick answer: Before you rebuild, decide whether the site needs fixes, a refresh or a full redesign, then record a baseline of traffic, enquiries, top pages and every existing URL. Plan redirects and content before design begins, test forms and tracking on launch day, and judge the new site against that baseline at 30 and 90 days.
Redesigns rarely go wrong at the design stage. They go wrong a few weeks after launch, when somebody notices enquiries have dipped, the old service pages return errors and the contact form has been emailing an inbox nobody reads. Almost all of that can be prevented by work done before a designer opens a file, and this checklist walks through it in order.
Do you need a redesign, a refresh or just fixes?
Match the scope to the symptom. A full rebuild is the most expensive answer, and it isn't always the right one.
| What you're seeing | Likely scope | What it involves |
|---|---|---|
| Slow pages, broken forms, outdated details, a few confusing pages | Fixes | Targeted repairs on the existing site |
| Dated look or a new brand, but the structure and platform still work | Refresh | New visual layer on the same structure and CMS |
| Hard to edit, unsupported platform, structure no longer matches your services, weak results across most pages | Redesign | New structure, design and often a new platform |
A refresh is often underrated. When the structure, copy and platform are sound, a new visual layer, better photography and sharper calls to action can deliver much of a redesign's benefit with far less risk to search visibility.
If you're unsure, run the audit below first; it usually makes the answer obvious. For budgets at each level, see our guide to website redesign cost, which compares refresh and full rebuild pricing.
What should you audit on your current site first?
Record what the current site achieves before you change anything, or you'll have nothing to compare against later. Work through this list and save the results in one shared folder:
- Analytics baseline. Twelve months of visits by channel, enquiries (forms, calls, WhatsApp clicks), sales if you sell online, and the top landing pages.
- Search Console data. The queries and pages that earn clicks, plus the pages other sites link to most.
- A full crawl. Every URL on the site, including PDFs and old campaign pages, using a crawler such as Screaming Frog.
- Content inventory. A spreadsheet listing each page's URL, title, traffic, enquiries and a decision column: keep, merge, rewrite or retire.
- Conversion paths. How people currently reach your contact or checkout pages, and where they drop off.
- Integrations. CRM, booking, payments, email marketing, chat and anything else connected to the site.
- Tracking tags. Analytics, Google Ads conversions, the Meta pixel and any server-side tracking.
- Speed. Current Core Web Vitals for your main templates; our guide to Core Web Vitals explained covers what each metric means.
- Access. Who holds the domain, DNS, hosting, CMS and analytics logins.
- Customer questions. What your team gets asked on calls and WhatsApp that the current site fails to answer.
How do you protect rankings and links during a redesign?
Keep URLs where you can, redirect every one you change, and carry over the signals that made strong pages rank. Search visibility is lost in redesigns through neglect far more often than through bad luck.
- Build a URL map. List every old URL beside its new destination. Pages being retired should point to the closest relevant page, not all to the homepage.
- Set up 301 redirects for every changed URL, and test them from the list before and after launch.
- Preserve what works. Keep the titles, meta descriptions, headings and core copy of pages that already rank, unless you have a clear reason to change them.
- Rebuild internal links so menus, footers and body copy point straight to new URLs rather than through redirects.
- Keep the staging site out of search with a password or noindex, and remove that block at launch. Forgetting this step is one of the most common launch-day mistakes.
- Submit the new XML sitemap in Search Console and watch the coverage reports for errors.
Our pre-launch guide to a website redesign without losing SEO goes deeper on the search side. If the redesign also moves customer records, orders or bookings to a new platform, read up on migrating data without losing it before you start.
How do you plan content and structure before design starts?
Agree the sitemap, the page templates and the content for key pages before anyone chooses colours. Design built on top of an unsettled structure is the main reason redesigns overrun.
- Draft the new sitemap from your services and the searches your customers make, using the content inventory as a guide
- Decide which pages to keep, merge or retire, and write the decisions into the URL map
- Wireframe the key templates: homepage, service page, contact page and any product or booking pages
- Set clear jobs for the homepage; our piece on what your homepage must do explains the first few seconds
- Write or rewrite copy for the main pages before the design stage, so layouts fit real words
- Confirm the CMS, and who will edit which pages after launch
This is also the moment to compare your content with how people search today. Clear answers to common questions, real prices or price ranges, and specific service and location pages help both search engines and AI assistants understand what you offer.
What should you test before and after launch?
Run this launch checklist on the staging site, then again on the live site within an hour of switching over:
- Every form submits, reaches the right inbox and shows a confirmation message
- Conversion events fire for forms, calls, WhatsApp clicks and purchases
- Redirects resolve correctly for every URL on the map
- No unexpected 404 errors appear in crawls or Search Console
- Pages load quickly on a mid-range phone over mobile data
- Layouts work on real phones, tablets and desktop browsers
- Keyboard navigation, alt text and colour contrast pass basic checks
- The noindex or password block is removed and robots.txt allows crawling
- HTTPS works on every page, with no mixed-content warnings
- Social sharing images and page titles display properly
- Backups and security updates are scheduled
Before launch, ask someone outside the project to complete your three most important tasks on the new site, such as requesting a quote, booking an appointment and finding your phone number. Fresh eyes catch problems the team can no longer see.
For the first week, check enquiries daily and compare them with the same week last year.
How do you measure whether the redesign worked?
Compare like with like: the same metrics, over equal periods, against the baseline you recorded. Review at 30 days for problems and at 90 days for results.
| Metric | Where to find it | What to look for |
|---|---|---|
| Enquiries and sales | Analytics, CRM | Steady or rising against the same period last year |
| Conversion rate | Analytics | Improvement on key pages |
| Organic clicks | Search Console | Recovery to baseline within weeks, then growth |
| Rankings for top queries | Search Console | No lasting drops on pages that earned traffic |
| Core Web Vitals | Search Console, PageSpeed Insights | Pass on main templates |
| 404 errors | Search Console, crawls | Falling to near zero |
If your business is seasonal, compare against the same weeks last year rather than the month before launch, or a quiet season can look like a failed redesign. Some short-term movement in search is also normal while Google processes redirects. A drop that persists past the first month deserves investigation, starting with the URL map.
Frequently asked questions
How often should a business website be redesigned?
There's no fixed cycle. Redesign when the site no longer reflects your services, can't be edited easily, runs on an unsupported platform or consistently fails to convert. Between redesigns, regular fixes and content updates keep a well-built site useful for years.
Will redesigning my website affect my rankings?
It can, in either direction. Rankings suffer when URLs change without redirects, ranking content disappears or pages become slower. With a URL map, 301 redirects and preserved content, most sites hold their positions and the improved experience can help over time.
Should I change my URLs during a redesign?
Only when there's a clear benefit, such as a confusing structure or URLs full of dates and codes. Every changed URL needs a 301 redirect to its closest new equivalent. If your current URLs are clean and descriptive, keep them.
Can I keep my old content on the new site?
Yes, and you should keep anything that earns traffic, links or enquiries. Use the content inventory to decide what to keep, update, merge or retire. Moving strong content across with its URL intact is one of the best ways to protect search visibility.
Should I redesign and rebrand at the same time?
You can, but it adds decisions and risk. If the brand work is unfinished, the website will stall waiting for it. Many businesses finish the brand identity first, then redesign the site once logo, colours and messaging are settled.
Get a second pair of eyes on your redesign
A redesign is a good moment to fix structure, speed and tracking together. Our website redesign services start with the audit and URL map, not with mood boards. If you're weighing up a rebuild, plan your redesign with us and we'll send a fixed-price scope.