A new website goes live, everyone is pleased, and a month later enquiries have halved. The site looks better and can no longer be found. Addresses changed without redirects, pages that brought visitors were quietly dropped, and the text that search engines ranked was replaced with something shorter and prettier.
All of it is avoidable with a list made before the design starts.
01Before the redesign: take an inventory
- Export every address on the current site.
- Mark the ones that bring search visits, links from other sites or enquiries.
- Note which searches each of those pages is found for.
- Save the current titles, descriptions and headings.
- Record current speed and search position, so there is something to compare with.
02During: protect what works
- Keep the address of every page that performs, where you can.
- Where an address must change, set a permanent redirect from the old one to its closest new equivalent, page by page.
- Never redirect everything to the home page.
- Keep the substance of the text that ranks. Rewrite for clarity, not for brevity alone.
- Carry over titles, headings, image descriptions and structured data.
03Technical checks before launch
- The test site is blocked from search engines, and that block is removed on launch day.
- Every old address returns either the same page or a redirect.
- No page is reachable only through a script that search engines cannot follow.
- Pages load fast on a phone on a slow connection.
- The sitemap lists the new addresses and nothing else.
The single most common disaster is launching with the instruction that tells search engines to stay away still switched on.
04After launch: watch for four weeks
- Submit the new sitemap to the search consoles.
- Check daily for addresses reported as not found, and redirect them.
- Compare visits to the pages you marked as important.
- Expect some movement in the first weeks; investigate anything that keeps falling.
05What a redesign can improve
Done with this care, a redesign usually raises search visits: faster pages, clearer structure, better text and working structured data all help. The loss comes from what is forgotten, not from the change itself.
In short
- Redesigns lose traffic through changed addresses, dropped pages and thinned text.
- Inventory what performs before any design work.
- Redirect each old address to its closest equivalent, never all to the home page.
- Check the test-site block is removed at launch, and watch errors daily for a month.
Questions
How long does it take search position to settle after a redesign?
Usually a few weeks, sometimes longer for large sites. With addresses kept or properly redirected, the change is small.
Do we have to keep the old text?
Keep what it says, not necessarily how it says it. Pages rank for the questions they answer. Remove the answer and the ranking goes with it.
Can lost traffic be recovered?
Often, if you still have a record of the old addresses and content. Restore the redirects and the missing pages quickly; the longer it is left, the less comes back.
Does Quantum Beetle handle this as part of a rebuild?
Yes. The inventory, redirects and technical checks are part of the build, not an extra.
Sounds like your problem?
Tell us about it. We'll say honestly whether the swarm can help, and what it would take.
Read next
- Website, web app, mobile app or custom software: how to choose what to buildSoftware development
- What a web application security test covers, and what to ask forSecurity testing
- How to get your company cited by ChatGPT, Perplexity and Google AI OverviewsAI marketing · GEO
- What a website costs: the eight things that decide the priceWebsites
- How to brief a software development company so you get what you meantCustom software
- Custom software or an off-the-shelf product: which one fits your businessCustom software