11 Website Redesign Mistakes That Cost Traffic and Leads

A redesign is the riskiest thing most websites go through. The new pages look better, and a month later organic traffic has dropped and the sales team is asking where the inquiries went. The design is rarely the cause. Most website redesign mistakes are omissions: things the old site did quietly, that nobody wrote down, and that the new site therefore does not do.

These are the eleven we see most often, grouped by the stage of the project where they happen, each with what to do instead.

Before the design starts

1. Starting without a baseline

You cannot tell whether a redesign helped if you never recorded where you began. Before any design work, save four things:

• a crawl of every address on the site with its status code, title, meta description, main heading and canonical tag
• the top landing pages and search queries from Google Search Console
• conversions per page and per form from your analytics
• speed measurements for each main template

Every later step in this list uses those files.

2. Redesigning on taste instead of evidence

"The site looks dated" is a reason to restyle it, not to restructure it. Before the navigation moves or the home page is rewritten, look at what visitors do: which pages they arrive on, where they leave, what they type into the site search, and which questions the sales team answers every week. A plain page that converts is an asset. Keep what works and change what the evidence says is failing.

3. Leaving content until the end

Mockups filled with placeholder text get approved easily, and then the real content does not fit. Headlines run three times longer, there are forty services where the design showed six, and nobody has photographs. Content is also the slowest part of almost every redesign. Start an inventory in the first week, with every page marked keep, rewrite, merge or remove and given an owner, and design the key templates around real copy.

While the site is being rebuilt

4. Changing addresses without a redirect map

Every address that changes needs a permanent (301) redirect from the old page to its closest new equivalent. The safest map is a short one, so keep the addresses that already work and change one only for a reason. Build the map from the baseline crawl as a two-column sheet. Do not point everything at the home page: Google's guidance on site moves warns that sending many old addresses to one irrelevant destination can be treated as a soft 404. Avoid chains of redirects, and keep the redirects in place for at least a year. Our website migration SEO checklist covers the full procedure.

5. Pruning pages that still earn traffic

Tidying up is healthy. Deleting blind is not. Before a page is removed, look it up in the baseline: does it bring visitors from search, does it convert, do other sites link to it? An old article that draws readers every month is worth more than its layout suggests. You have three options for each page: keep and refresh it, merge several weak pages into one strong page and redirect the others, or remove a truly dead page and let it return a 404 or 410.

6. Dropping the invisible SEO work

An established site carries years of work that nobody sees: tuned titles and meta descriptions, a sensible heading structure, image alt text, structured data, canonical tags, links between related pages in the body text, an XML sitemap, and language annotations on multilingual sites. A new theme or a new CMS starts with none of it unless someone moves it across. Before launch, crawl the new site and compare it with the baseline field by field.

7. Designing for the desktop mockup

Sign-off happens on a large monitor, while much of the audience arrives on a phone. Google does too: it indexes and ranks from the mobile version of a page. Content that is cut from the phone layout to make it cleaner has, in effect, been cut for search as well. Review every template on real phones: the same content as on desktop, tap targets large enough for a thumb, a menu that can be used one-handed, forms that bring up the right keyboard, and nothing wider than the screen.

8. Shipping a heavier site than the one you replaced

Redesigns add weight: video headers, carousels, several font families, animation libraries, page-builder markup. Set a budget while the design is still on paper. The Core Web Vitals thresholds are a reasonable one: the largest element painted within 2.5 seconds, interactions answered within 200 milliseconds, and a layout shift score of 0.1 or less, measured on a mid-range phone for each main template. Compare against the baseline before launch. A new home page that is slower than the old one is not ready, and performance optimization is cheaper before launch than after.

At launch and after

9. Forgetting forms, tracking and integrations

A redesign replaces every form, and with each form its connections: the notification email, the CRM or mailing list integration, the thank-you page that analytics counted as a conversion, the spam protection. The same goes for tags: analytics, the tag manager container, advertising pixels, the consent banner, call tracking and live chat. List them all from the old site, then test each one on the new site with a real submission and confirm that the lead reaches the inbox and the CRM and that the conversion is recorded. A broken form does not show an error. It produces silence.

10. Carrying staging settings into production

A staging site should be hidden from search engines, and the settings that hide it must not ship. On launch day, check that:

• the page source has no noindex robots meta tag;
• robots.txt does not contain Disallow: /;
• in WordPress, Settings > Reading > Discourage search engines from indexing this site is unticked;
• password protection has been removed;
• canonical tags, internal links and image addresses point to the live domain, not to staging;
• outgoing email is no longer in test mode.

11. Launching and walking away

Launch on a day when the team is at work for the two days that follow, which rules out Friday afternoon. Then run the old address list through a crawler and confirm that each one redirects to a page that loads. Submit the new sitemap in Search Console, watch for 404 errors in the server log, and test the forms again on the live domain. Compare traffic, rankings and conversions with the baseline every week for the first two months. Some movement is normal while Google recrawls the site. A steady fall on particular pages is a signal to check their redirects and their content. Keep a backup of the old site, so a single page can be brought back if needed.

Avoiding these website redesign mistakes on your own project

A site of twenty pages that stays on the same CMS with the same addresses can be redesigned in-house with this list and some discipline. Give one person ownership of the baseline, the redirect map and the launch checks, because these jobs fall between design and development and are dropped when they belong to nobody.

The risk grows with the number of addresses, with a change of platform, with a store attached, and with how much of your revenue starts in organic search. In those cases it helps to have the design, the build and the migration planned as one piece of work. That is how we run UI/UX and website design projects, including the custom WordPress theme development that often follows. A redesign is also the cheapest moment to fix contrast, focus states and form labels, and our WCAG starter guide explains what to ask for.

Frequently asked questions

Will a redesign hurt my search rankings?

It does not have to. Rankings suffer when addresses change without redirects, when content is removed or thinned, or when technical elements such as titles and structured data are lost. If those carry over, a redesign that also improves speed and mobile usability tends to help. Expect some short-term movement either way.

Should I change my URL structure during a redesign?

Only when there is a concrete reason, such as a new site structure that the old addresses contradict, or addresses full of parameters and file extensions. Tidier addresses alone do not justify the risk. Every change needs a redirect, and every redirect is one more thing that can be wrong on launch day.

Is a visual refresh safer than a full redesign?

Yes, considerably. A refresh applies new styling and templates to the same pages, addresses and content, so most of the risks in this list never arise. If the baseline shows that the structure and content perform well and only the look is dated, a refresh is the better project.

How soon should I compare results with the old site?

Check the technical items on the first day: redirects, indexing settings, forms and tracking. Look at traffic and conversions weekly from then on, and judge the redesign on a period long enough to smooth out seasonal swings, set against the same period before launch.