Why do website redesigns lose traffic?
Redesigns usually lose traffic for avoidable reasons: changed URLs without redirects, deleted pages that ranked well, rewritten titles and headings, a staging noindex tag left in place, or slower templates. A disciplined website redesign process treats search equity as something to protect, not something to rebuild after launch.
Not every redesign needs new URLs. If your current structure works, keeping it is the simplest way to protect rankings. Where the platform or domain is also changing, the work overlaps with a website migration, which needs extra planning.
Which benchmarks should you record before you start?
Record a baseline so you can prove whether the redesign worked. Export organic traffic and conversions by page from analytics, top queries and pages from Google Search Console, Core Web Vitals and PageSpeed results for key templates, and a list of pages earning external links. Save these exports; old data can become harder to access later.
- Organic sessions, enquiries, calls and sales over the last 12 months.
- Top landing pages by organic traffic and by conversions.
- Search Console queries, clicks and average positions for key pages.
- Core Web Vitals and PageSpeed results for homepage, service, product and blog templates.
- Pages with backlinks from other websites, from Search Console's links report.
How do you build a URL inventory and content audit?
Crawl the current site with a crawler tool and combine the results with URLs from your XML sitemap, analytics and Search Console. That gives a complete list, including forgotten pages. Then decide for each URL whether to keep, improve, merge or remove it, based on traffic, links, conversions and business relevance.
| Decision | When to use it | Redirect needed? |
|---|---|---|
| Keep | Performs well and is still accurate | Only if the URL changes |
| Improve | Valuable topic but thin or outdated copy | Only if the URL changes |
| Merge | Several pages compete for the same query | Yes, to the merged page |
| Remove | No traffic, links or business value | Yes if it has links or traffic; otherwise return 404 or 410 |
How do you create a 301 redirect map?
A 301 redirect map is a spreadsheet pairing every old URL with its closest equivalent new URL. Redirect one-to-one wherever possible, avoid sending everything to the homepage, avoid redirect chains, and include old images and PDFs that earn links. Implement redirects on the server and test the whole list before launch.
- List every old URL from the inventory, including variants with and without trailing slashes.
- Assign the most relevant new URL to each one.
- Update old redirects so they point straight to the final URL (no chains).
- Load the map onto the staging server and test each old URL returns a single 301 to a 200 page.
- Update internal links to point directly at new URLs rather than relying on redirects.
What should you check before launch?
On staging, check that every page has a unique title, meta description and H1, structured data validates, forms deliver to the right inbox, analytics and conversion tracking fire, pages pass Core Web Vitals targets, layouts work on phones, accessibility meets WCAG 2.2 AA, and legal pages are present.
- Titles, descriptions and headings carried over or improved for pages that ranked well.
- Company name, number, registered office and place of registration shown, as Companies Act rules require.
- Privacy notice updated and cookie consent configured under PECR for any non-essential cookies.
- Speed and responsive layout tested on real devices; see how to improve website speed.
- Content and on-page SEO checked against our SEO-friendly website checklist.
What needs to happen on launch day?
Launch early in the week, at a quiet time, with the developer available. Remove staging noindex tags and password protection, confirm robots.txt allows crawling, deploy redirects, check HTTPS and the canonical domain, submit the new XML sitemap in Search Console, and run a crawl of the live site to catch errors.
- Take a full backup of the old site and keep it accessible.
- Switch DNS or deploy, then confirm the live site loads on HTTPS with the correct domain.
- Remove noindex tags and check robots.txt.
- Spot-test redirects from the map, especially top landing pages.
- Submit the sitemap and request indexing for the most important pages.
- Submit a test enquiry and a test purchase, if relevant.
What should you monitor after launch?
Check Search Console daily for the first week, then weekly for at least two months. Watch for 404 errors, pages dropping out of the index, falling clicks on key queries, and conversion tracking gaps. Some ranking movement is normal after a redesign; sustained drops on specific pages usually point to a fixable problem.
- Compare organic traffic and conversions with the benchmarks, allowing for seasonality.
- Fix any 404s that have traffic or links with additional 301 redirects.
- Keep the redirects in place long term, not just for a few months.
- Re-check Core Web Vitals once enough field data has built up.
How much does a website redesign cost?
As a typical UK market guide, a redesign costs broadly 60% to 100% of an equivalent new build, excluding VAT, because most of the design and development work is new. Small business or brochure sites typically cost £1,500 to £5,000 to build new, so scale from there. Redirects and any migration work add cost.
A simple migration typically adds about £300–£1,500, and a complex or ecommerce migration £2,000–£10,000 or more. If you are comparing providers, see how to choose a web design agency.
These are indicative UK market ranges, not a Freehand HQ quote.