Website redesign services UK: a new site that keeps the rankings and enquiries you already earn

What do website redesign services in the UK actually cover?

Website redesign services cover three jobs at once: a new design, a new or cleaned-up build, and a controlled move of everything that already works from the old site to the new one. The third job is the one most often underpriced, and it is the one that protects your enquiries.

A business usually needs a redesign when at least one of these is true: the site looks dated next to competitors, it is hard to use on a phone, staff cannot edit it without help, it is slow, or it runs on a platform you no longer want to pay for. A redesign is not the answer when the only problem is weak copy or a missing page; those are cheaper fixes.

For UK businesses, good website redesign services also account for local expectations: a privacy notice and cookie consent that match ICO guidance, accessible forms, VAT-inclusive pricing where you sell to consumers, and contact details that match your Google Business Profile. We fold those into the plan from the start rather than patching them in during the final week.

• Discovery: what the site must do, who edits it, which pages earn money
• Inventory: every URL, its traffic, links and indexing status
• Design and build: new templates, content moved or rewritten
• Migration: redirects, metadata, structured data, analytics
• Launch and monitoring: checklist, Search Console, fixes

How do you redesign a website without losing Google rankings?

Keep the pages Google trusts, keep their addresses where you can, and redirect every address you do change to the closest matching new page. Rankings drop after a redesign mostly because pages disappear, URLs change without redirects, or content that earned the ranking is cut.

Google’s own site-move guidance recommends server-side permanent redirects (301 or 308), advises keeping redirects for “generally at least 1 year”, and warns that you may see ranking fluctuations while pages are recrawled; for medium-sized sites it can take a few weeks or more for new URLs to replace old ones. That is normal. What is not normal is a sustained loss, and that almost always traces back to a missed step.

The missed steps we see most: blog posts dropped because “nobody reads them” even though they bring half the search visits; service pages merged into one long page; title tags reset to the page name; internal links still pointing at old URLs; and the new site launched with a “noindex” setting left over from staging. Each one is avoidable with a list and a check, which is why our redesign process leans on spreadsheets more than mood boards.

The content and URL inventory: the first job in any redesign

The inventory is a single spreadsheet listing every URL your site has, with the evidence needed to decide its future. Nothing gets designed until it exists, because design decisions (which pages to merge, what the menu holds) depend on it.

We build it from four sources, because no single one is complete: a crawl of the live site, your XML sitemap, the Pages report and Performance report in Google Search Console, and your analytics landing pages for the last twelve months. Old platforms often hide URLs that only a combination reveals: image attachment pages, tag archives, PDF downloads and forgotten campaign pages that still receive links.

Each row then gets a decision: keep (same URL), move (new URL, 301 redirect), merge (combine with another page, redirect both to the survivor), or remove (410 or redirect to the nearest parent if it has links or traffic). You see and approve the decisions. Another of us handles the crawl and Search Console side; you know which pages matter commercially, so your input on the “keep or merge” column is the most valuable part.

• URL, page title and main heading
• Clicks and impressions from Search Console (last 12 months)
• Sessions and enquiries from analytics
• External links pointing at it, where known
• Decision: keep, move, merge or remove, with the new URL

301 redirect mapping for website redesign services: how the map is built

A redirect map pairs each old URL with exactly one new URL and is loaded onto the server so the change happens before any page loads. It is the most important file in a redesign, and it should be tested before launch, not written on launch day.

Good maps follow a few rules. Redirect to the closest equivalent page, not the homepage; Google may treat mass redirects to a homepage as soft errors, and visitors land somewhere unhelpful. Avoid chains: if a URL was already redirected once in a previous redesign, point the original straight at the final destination. Keep query-string variations in mind for shops and filtered listings. Redirect the old non-https and www variants in one hop.

On WordPress we load the map at server or plugin level; on static hosting, through the host’s redirect file; on a headless setup, in the edge configuration. Before launch we run every old URL against the staging site and check the status code and final destination of each. The sample table further down shows what the finished map looks like, including how merged pages are handled.

Moving off Wix, Squarespace or an old WordPress theme

Leaving a hosted builder is mostly an export problem: the text and images come out, but layouts, forms and some settings do not, so plan to rebuild those rather than migrate them. Moving off an old WordPress theme is easier because the content stays in the same database.

Wix does not give you a full site export in a format another platform can import, so pages are rebuilt and blog posts moved through their feed or copied across in batches; images are downloaded at their original size. Squarespace offers a WordPress-format export for some content types, typically blog posts and basic pages, but galleries, product pages and custom blocks usually need rebuilding. Both platforms use their own URL patterns (for example, blog posts under a fixed path), so the redirect map matters even if you keep the same domain.

For a WordPress site on a dated premium theme or a page builder, we replace the theme with a lighter custom block theme and convert builder layouts into native blocks. Posts, pages, users and media stay; URLs usually stay too. The WordPress design guide for UK businesses explains that choice in more depth.

Whichever platform you leave, point your domain’s DNS only after the new site passes checks, and keep the old subscription running for a few days so nothing is lost if something needs to be copied again.

Should you refresh, redesign or rebuild your website?

Refresh when the structure works and only the look is dated; redesign when the structure and look both need work but the platform is fine; rebuild when the platform itself is the problem. Choosing the smallest job that fixes the real problem saves money and risk.

A refresh changes colours, typography, images and a few layouts while keeping every URL and template. SEO risk is low and the job is quick. A redesign rethinks navigation, page types and content, which means some URLs change and redirect planning becomes essential. A rebuild changes the platform: Wix to WordPress, an ageing custom PHP site to a modern framework, or a page-builder site to a clean theme. That carries the most migration work.

A simple rule: if you cannot edit your site without paying someone, it is slow on a phone even after image fixes, or its platform no longer receives security updates, you need a rebuild, whatever the design looks like. If staff are happy with editing and the site is quick, a refresh may be all you need, and it is a smaller quote.

How much do website redesign services cost in the UK?

Quotes for website redesign services in the UK vary widely, mostly with the number of URLs, how much content must be rewritten, and the supplier’s overheads. With us, a business site redesign starts at US$150, content-heavy sites of 299+ pages start at US$300, and shop redesigns start at US$750.

What moves the number up: a large blog or resource library that needs individual redirects; product catalogues with variants; copy that needs rewriting rather than moving; complex forms such as multi-step quotes; integrations with CRMs or booking tools; and multilingual content. What keeps it down: reusing good copy and photography, a clear list of page types, and a decision-maker who replies within a day or two.

Add running costs when you compare. Leaving a hosted builder often reduces monthly fees because you pay for hosting directly, but you then need someone to apply updates. That is what the two free months cover, and afterwards a care plan starts at US$120/mo. For a line-by-line view of UK budgets, see how much a website costs in the UK.

How long does a website redesign take?

For a typical business site, allow a few days for the inventory and redirect plan, one to two weeks of build once content is agreed, and a week of checks around launch. Content-heavy sites take three to five weeks of build; shops take four to eight.

The calendar is usually set by content rather than code. If pages need rewriting, the redesign waits for copy. If photography is being reshot, it waits for images. We suggest locking the page list and the redirect decisions in week one, then letting design and copy run in parallel so neither blocks the other.

Avoid launching on a Friday or just before a bank holiday. You want a normal working day after launch so that any broken form or missing redirect is spotted and fixed while traffic is ordinary. We also avoid launching in the run-up to your busiest season, for example a heating engineer in October or a garden centre in spring; the plumbing and heating website guide shows why seasonality matters for trades.

Using a redesign to fix accessibility: WCAG 2.2 AA in practice

A redesign is the cheapest moment to fix accessibility, because templates are being rebuilt anyway. We test new templates against WCAG 2.2 level AA, the current version of the W3C’s Web Content Accessibility Guidelines.

WCAG 2.2 added criteria that older sites commonly fail. Focus Not Obscured (Minimum), criterion 2.4.11, means sticky headers and cookie banners must not hide the element a keyboard user is on. Target Size (Minimum), 2.5.8, sets a minimum size or spacing for tap targets such as small icon links. Accessible Authentication (Minimum), 3.3.8, matters if your site has a login. The WCAG 2.2 specification sets out each criterion in full.

In practical terms we check colour contrast on every text style, give each form field a visible label and helpful error messages, make menus usable with a keyboard, write alternative text for meaningful images, and keep headings in logical order. None of that makes a site look worse; it usually makes it clearer. If you want an independent view of an existing site first, the UK accessibility audit page explains what that involves. We build to the guidelines; we do not certify compliance or give legal advice.

Speed gains: what a redesign should do for Core Web Vitals

A redesigned site should load noticeably faster on a phone than the old one, and you should see numbers, not adjectives. Google’s web.dev guidance treats Largest Contentful Paint within 2.5 seconds, Interaction to Next Paint of 200 milliseconds or less and Cumulative Layout Shift of 0.1 or less, measured at the 75th percentile of page loads, as good.

We record the old site’s scores before starting, so you have a baseline. Most gains come from removing things rather than adding tools: oversized hero images, sliders, several font families, chat widgets loading on every page, and third-party scripts nobody remembers adding. Builder platforms such as Wix and Squarespace limit how much of that you can control; that is one reason businesses move off them.

After launch, lab tests tell you the site is fast on a test device; the Core Web Vitals report in Search Console tells you whether real visitors agree, once enough data comes in. We check both during the free aftercare period.

Protecting enquiries during a website redesign

Rankings are only half of what a redesign can break; the other half is the path from visit to enquiry. Before launch, list every way customers contact you through the site and test each one on the new build.

That means forms (where do submissions go, and does the email arrive rather than land in spam?), click-to-call links, WhatsApp buttons, booking tools, live chat, quote calculators and newsletter sign-ups. It also means the tracking behind them: if you measure enquiries as analytics conversions or through call tracking numbers, those need recreating on the new pages, or you will think enquiries dropped when only the measurement did.

We keep a simple “enquiry routes” list alongside the redirect map, test each route on staging and again on the live site within an hour of launch, and send you a screenshot of each test submission arriving. It is dull work. It is also the difference between a redesign that quietly loses leads for a month and one that does not.

Website redesign launch-day checklist for UK sites

Launch day should be a checklist, not an event. Everything creative was finished on staging; launch is about switching over carefully and confirming that search engines and customers can reach the new pages.

We run the list below in order and tick each line in a shared document so you can follow along. Anything that fails is fixed before we move on to the next step.

• Remove staging password and any noindex tag or robots.txt block
• Point DNS during a UK weekday morning; confirm https works on all hostname variants
• Load the redirect map; test a sample of top pages plus every high-traffic URL
• Submit the new XML sitemap in Search Console; keep the old sitemap for a short period so Google sees the redirects
• Test every form, call link and booking route; confirm emails arrive
• Check cookie banner blocks non-essential scripts until consent
• Confirm analytics and any conversion tracking fire once per enquiry
• Spot-check titles, meta descriptions and structured data on key templates

If you are also changing domain, for example moving from a .com to a .co.uk, Search Console’s Change of Address tool applies; it only works for domain-level moves and needs a 301 from the old homepage to the new one.

Search Console monitoring after a website redesign

For the first few weeks after launch, Search Console is the early-warning system: it shows crawl errors, pages Google could not index and changes in clicks well before you would notice them in enquiries.

We look at four reports. The Pages report shows whether new URLs are being indexed and whether old ones are dropping out as redirects are processed. The Performance report, compared against the same weeks before launch, shows whether clicks and impressions for your main queries hold. The Sitemaps report confirms the new sitemap was read. And the Core Web Vitals report, once it has enough data, confirms real-user speed.

Expect some movement; Google says fluctuations are normal while it recrawls. What we watch for is a pattern: a group of queries that falls and stays down, usually pointing at a page that was merged too aggressively or a redirect that goes somewhere unhelpful. Because the inventory records what each old URL ranked for, we can trace a drop to a specific decision and fix it. This monitoring is included in the free two months after launch.

Who owns the redesigned site, domain and accounts?

You do. The domain, hosting, code, analytics and Search Console properties sit in your accounts; we work as added users and hand back access at the end.

Redesigns are often the moment businesses discover they never owned their site. The domain may be registered to a former designer, the hosting may be on someone else’s reseller account, or the Wix or Squarespace subscription may be under a personal email that nobody can reach. Sort this out first. For .uk domains, Nominet runs the registry, and your registrar can change the registrant details and move the domain to an account you control.

At handover you receive a short document listing every account, who pays for it, and how to remove our access. The code lives in a repository you own, so any developer can pick it up later. For the wider question of whether a freelancer or an agency suits your business better, the agency versus freelancer guide is a fair comparison.

Working with a remote redesign team in India from the UK

Redesign work suits remote delivery well because most of it happens in shared documents and on a staging site. You will not meet us in person, and we do not do site visits; everything runs on video calls, WhatsApp and a shared inventory spreadsheet.

India runs four and a half hours ahead of the UK during British Summer Time and five and a half hours ahead in winter. That means your late morning and early afternoon overlap our working day, so calls sit comfortably in UK working hours, and changes you request at lunchtime are often on staging by the time you finish work.

Quotes are in USD; you can pay from a GBP account through Wise, bank wire or PayPal, and invoices come from India. Nothing is billed before you approve the written quote, and our terms set out how changes are handled. One of us leads the build, another of us runs the crawl, redirects and Search Console, and the third of us keeps the plan and your decisions in one place.

Worked example: a hypothetical Bristol physio clinic leaving Wix

This is an illustrative scenario, not a client story. Say a two-room physiotherapy clinic in Bristol has a Wix site with about 40 pages: treatment pages, a team page, a blog of 25 posts written over several years, and a booking link to an external system. It wants a site staff can edit and that loads faster on phones.

The inventory shows that a handful of blog posts about common injuries bring a large share of search visits, while most treatment pages bring few clicks. That changes the plan: the popular posts keep their content almost untouched, with better internal links to the matching treatment pages; weak treatment pages are merged into stronger ones and redirected. Wix blog URLs follow a fixed pattern, so every post gets its own redirect to a cleaner address.

Build is a WordPress block theme on hosting in the clinic’s own account, with the booking link kept, a privacy notice covering the contact form, and a cookie banner that holds back analytics until consent. At launch the redirect map covers every old URL. For the next few weeks the clinic receives short updates on indexing and clicks for the injury queries. In a case like this the quote would start from US$150; the final figure would depend on how much copy the clinic wants rewritten.

Red flags when comparing website redesign services in the UK

The biggest red flag is a proposal that talks only about design. If a supplier cannot tell you how many URLs your site has, they have not planned how to move them.

Other warning signs: a plan to redirect everything to the homepage; no mention of Search Console; hosting that will sit in the designer’s account with no exit route; a promise of first-page or guaranteed rankings (nobody can honestly promise that); and a launch date set before content is agreed. Ask, too, what happens if traffic drops after launch; the answer tells you whether monitoring is part of the job.

A good proposal for website redesign services names the platform and why, lists what is being migrated and what is being rebuilt, includes a redirect map as a deliverable, sets out accessibility and speed checks, and explains support after launch. If you want a second opinion on a quote you have already received, send it over; we will tell you honestly whether it looks complete.