The redesign mistakes that cost traffic and enquiries

Changing URLs without redirecting them is the redesign mistake that loses ranking pages, because Google then treats those pages as gone. The others are starting with the look before agreeing a goal, launching without tracking, choosing a build your team can’t update, and testing too little before go-live.

Does a website redesign hurt SEO?

Only when it breaks what Google already knows. That happens when URLs change without redirects, when pages that ranked are cut, or when the new site hides content from crawlers.

Google’s guidance says a small to medium site can take a few weeks for most pages to move, and rankings can fluctuate while it recrawls. It says to keep redirects for at least a year (Google Search Central, site moves with URL changes, updated 20 August 2026).

Before anything is designed, export every URL that gets traffic or has links pointing to it. Search Console and your analytics will give you both. Map each one to its new address. Anything without a direct match gets a 301 redirect to the closest page. Our website redesign service starts with that audit of what already ranks and converts.

When should each check happen?

Two checks come before any design work. The rest run through discovery, build, launch and the weeks after.

Stage	Check	What happens if it’s skipped
Before design	Export every URL with traffic or links	Ranking pages return 404 at launch
Before design	Agree one goal and start tracking on the old site	Nobody can prove the redesign worked
Discovery	Scope content and every integration	The budget and launch date slip
Build	The person who’ll update the site tests the editor	Updates stop and the site goes stale
Before launch	Real devices, forms and redirects tested on staging	Enquiries lost in the first week
After launch	Search Console checked weekly, redirects kept	Slow traffic drops go unnoticed

What does a failed migration look like?

A failed migration keeps the design and loses the site’s history: old URLs, working redirects and the pages Google had indexed. Expat Living, a Singapore expat lifestyle publisher, asked us to look at its site in May 2017. Another team had moved it off a legacy publishing system onto WordPress.

Thousands of old-format URLs were still in circulation. Redirect chains looped back on themselves. An abandoned subdomain with more than 600 URLs sat in Google’s index, and expired events were being fed to Google through the sitemaps.

We crawled 10,000 URLs before proposing any design. Google was indexing around 9,000 near-empty tag pages, so the real articles were competing with years of junk. The first months went on clean-up: junk pages taken out of the index, redirect loops untangled, sitemaps rebuilt to offer only real content.

Then we rebuilt the site on the Genesis Framework and launched it in December 2017. After launch we rewrote old URL patterns across hundreds of posts, each with a redirect behind it, and deleted around 1,100 empty tag archives. Expat Living still publishes daily on that build, nearly nine years later.

For a publisher, the value sits in thousands of older articles that still pull search traffic. A smaller business has the same exposure in the service pages and posts that bring in enquiries each month.

Why does a redesign need a goal first?

Without one, nobody can say whether it worked. “A more modern look” can’t be measured. “Double enquiries from 10 to 20 a month within six months of launch” can. Our guide to setting SMART website goals shows how to write one.

Tracking has to start on the old site. If measurement begins on launch day, there’s nothing to compare against. Keep Google Analytics and Search Console running through the whole project.

What makes a redesign run over budget?

Work nobody counted at the start. Content is the usual one: pages to rewrite, images to replace, old posts to move. Integrations are the other. A CRM, a booking system or stock sync with a supplier each needs scoping before a price is agreed.

Most redesigns take 8 to 12 weeks. Longer projects are usually waiting on approvals. Discovery ends with a sitemap and a written scope, and design doesn’t start until both are agreed.

Can your team update the new site?

It should. Your team should be able to add a page, swap an image and publish a news item without a developer. The Pinnacle Foundation, an Australian LGBTQIA+ education charity, had a site another agency built on Visual Composer. It broke often, loaded slowly and cost a team of fewer than six people hours of admin.

We rebuilt it in 2020 on WordPress with Beaver Builder, a combination non-technical teams can run themselves. It’s still on our hosting and care plan, and a small staff publishes news and events without a developer (Pinnacle Foundation case study).

Before you sign off, ask the person who’ll update the site to try those three jobs without help. Check who owns the site, the domain and the hosting account. It should be you, from day one. Check the licences too. On a neglected site we took over this year, the page builder’s licence had lapsed, so it had stopped getting fixes.

What should you test before launch?

Test five things on the staging copy: devices, people, mobile speed, forms and redirects.

• Real devices. We test every page on real devices through BrowserStack, and the client signs off on a staging copy before anything goes live.
• Real people. Five is enough. Jakob Nielsen found that testing with five people finds almost as many usability problems as testing with many more (Nielsen Norman Group, June 2012).
• Speed on mobile. Run the key pages through PageSpeed Insights. Interaction to Next Paint replaced First Input Delay as a Core Web Vital on 12 March 2024 (web.dev). Google retired its Mobile-Friendly Test on 1 December 2023 (Search Engine Land, December 2023). A checklist that still mentions either is out of date.
• Forms and tracking. Submit every form. Check the email arrives and the conversion records.
• Redirects. Run the old URL list through a crawler. Every one should return a 301 to a live page.

What happens after launch?

Check Search Console every week for the first couple of months. The pages report shows any old URL that now returns a 404, and each one needs a redirect. Some ranking movement in the first weeks is normal, as Google’s own guidance says. A drop that’s still there after a month means something was missed. On the date you set, compare results against the goal.