Website Redesign Mistakes That Cost You Customers
By Gianna Stead | SEO Manager, Maisona | 4 min read
A new website almost never fails on launch day. It fails three weeks later, when a director asks why enquiry volume has dropped. The cause is usually one of a handful of avoidable website redesign mistakes. Nobody can say which of the forty things that changed is responsible. Businesses judge redesign projects on how the site looks in the demo. What matters more is what still works the Monday after it goes live.
Most of the damage comes from a small set of avoidable mistakes. Nearly all of them share one cause. Businesses treat a redesign like a fresh coat of paint, not like moving house.
Launching Without a Redirect Map
The single most common cause of a post-launch traffic drop is old URLs that simply stop existing. It’s the same discovery failure that shows up in why your website isn’t ranking. That happens when someone merges two pages and neither one redirects properly. Redesigns usually change the site structure. That’s often the whole point. But every page that earned rankings, backlinks, and bookmarks needs a permanent redirect to its new address.
Google’s own guidance on site moves is specific about this. Use server-side permanent redirects wherever a URL changes. Google treats a 301 redirect as a strong signal to index and rank the new address, not the old one. Skip this step, and you lose it all. Every incoming link, bookmark, and ranking you’ve built over years ends up pointing at a page that no longer exists.
The mapping work has to happen before development starts, not after launch when someone notices the drop. That means matching every current URL one-to-one against its new destination, including pages that seem minor. Google’s migration documentation sets a clear expectation on timing, one most launch plans ignore. Keep redirects in place for at least a year. Even a well-executed move can take several weeks for rankings to fully transfer on a medium-sized site. A redesign brief that budgets zero time for this is budgeting for a traffic dip it never had to have.
Treating Design as the Whole Project
People who’ll judge the result by looking at it write most redesign briefs. That means the brief specifies colours, layout, and photography first. It specifies what a visitor should do on each page last, if at all. The result is a website that looks sharper than the old one but converts at the same rate, or worse.
This mistake shows up in the handover between whoever approves the design and whoever built the old site’s conversion paths. Ask the person signing off on the new homepage what happens when someone clicks the primary button. If they can’t answer, the project has optimised for the wrong thing. Looks the part, misses the brief covers the deeper version of this problem. The redesign-specific risk is narrower. A relaunch is the one moment a business has full permission to rebuild its conversion architecture from scratch. It’s also exactly the moment most businesses spend that permission on a new logo treatment instead.
Losing Content That Was Working
Migrations tend to shrink content. Nobody decides to cut it outright, but rebuilding fifty pages by hand invites shortcuts. Older blog posts fall off the new site’s navigation. Someone merges location pages “for simplicity.” Someone replaces a capability statement PDF that was ranking, badly, but ranking, with a single generic services page.
Three checks catch most of this before it becomes a problem:
- Every page earning real traffic needs a confirmed home and internal links on the new site, not just a redirect.
- A page consolidating several old pages still covers everything they did, not a lighter summary.
- Nothing that used to convert, an old form, phone number, or proof point, disappears just because nobody asked about it.
When Your Tracking Breaks and Nobody Notices
A redesign is also, quietly, an analytics migration. Someone swaps the tracking codes, and form structures change along with them. Event tracking that fired on the old contact form often doesn’t fire on the new one. Someone has to rebuild it on purpose. You find this out a month later, staring at a lead-volume chart with a gap you can’t explain. Nobody was collecting the data.
The fix is unglamorous. Test every event, form submission, and conversion goal on a staging version of the new site before it goes live. Use the same dashboard the business already relies on. If leadership can’t see whether the new site is working within the first week, they’ll judge it on gut feeling. Gut feeling after a redesign is almost always wrong, in one direction or the other.
Skipping the Boring Testing Pass
The last mistake is the least visible one, until it isn’t. It means launching without testing the site the way a real visitor will use it. That means a mobile connection, an older device, arriving from a search result rather than a bookmark. Broken forms, slow-loading pages, and dead internal links are common on relaunch day. That’s because everyone involved has been testing from a fast office connection, clicking the same three pages they know work.
It’s the same crawl-directive mistake behind most of the indexing issues we find in audits. A site-wide noindex tag left on from staging can sit invisible to Google for months. So can a page nobody linked into the new navigation. A redesign is the highest-risk moment for this kind of error, because the whole site’s technical configuration changes at once.
None of this is complicated once someone owns it. It just has to be someone’s job before launch day, not a discovery made three weeks after. If your last redesign quietly cost you enquiry volume, Maisona can review what changed. We’ll help fix what’s still costing you leads.
FAQs
Will a website redesign always cause a temporary drop in traffic?
Not always, but some fluctuation is normal even with a well-executed move. Google’s own documentation notes it can take a few weeks or more for rankings to fully transfer to new URLs. That’s true even on a medium-sized site. A drop that doesn’t recover within that window usually means a missing redirect or a lost page.
How long should redirects from the old site stay active?
At least a year, based on Google’s own guidance for site moves. Removing redirects early is one of the most common causes of a delayed traffic drop. It catches businesses off guard months after launch.
What is the most overlooked step in a website redesign?
Testing analytics and conversion tracking on the new site before launch. Businesses frequently discover weeks later that the new site stopped recording form submissions or key events on launch day.
Does every old page need a home on the new site?
Not necessarily, but every page earning organic traffic needs a deliberate decision. That decision is either a genuine equivalent on the new site or a redirect to the closest relevant page. Cutting pages without checking their traffic first is how businesses lose rankings they didn’t know they had.
How far in advance should redirect mapping start?
Before development begins, not after. Mapping every current URL to its new destination is scoping work. It should happen at the same stage as the sitemap and page list. It’s not a fix you apply after launch.