A Monday morning phone call we have taken more times than we would like. A company launched a new site on Friday afternoon. Over the weekend organic traffic dropped seventy per cent, enquiries stopped, and the server returns 404 for half the old URLs. The design is beautiful.
A redesign rarely damages a business because of the visuals. It damages it because of what sits underneath: URLs, redirects, content and measurement.
When a redesign is genuinely needed
Searches for website redesign in Bulgaria run at around 40 a month, but real projects are many times more numerous, because most of them start with "we want something more modern". That is not a sufficient reason.
Good reasons for a redesign are these. The site does not render properly on a phone. Speed is below acceptable and cannot be fixed with optimisation. The platform is no longer maintained and has security holes. The content no longer matches what the company sells today. Conversion is low and testing points to a structural problem rather than traffic quality.
Bad reasons: the owner saw a competitor's site he liked, or a new marketing hire wants something of their own.
Redesign, migration or both
A redesign changes the visuals and the structure. A migration changes the platform, the hosting or the domain. Doing both at once multiplies the risk, because when something breaks you cannot tell which change caused it. On complex sites we split the two into stages at least a month apart.
Audit before anything is touched
This stage takes two to five days and saves months of recovery.
A complete URL list
Export every indexed URL from Search Console, from the sitemap and from a crawl of the site. Merge them into one file. For a shop with thousands of products this list is the foundation of the entire migration.
Which pages carry value
Match the URLs to traffic and conversion data from GA4 for the last twelve months. You will find that twenty per cent of pages carry almost all the result. Those pages are untouchable: their content moves across, it is not rewritten from scratch.
External links
Check which pages have inbound links. If a page with twenty quality links disappears without a redirect, you lose authority built over years. There is more on link value in the article on link building.
A current baseline
Record the numbers before the change: organic sessions, positions for the main terms, speed, conversions. Without a baseline you cannot prove whether the redesign helped or hurt.
The redirect map
This is the most important document in the whole project and it lives in a spreadsheet with old URLs in one column and new ones in the other.
The rules are simple and allow no exceptions. Every old URL gets a redirect to the closest matching new URL. Not to the home page, because that counts as a soft error and destroys the value. The redirect is a 301, permanent, not a 302. Chains are avoided: old URL straight to new URL, no intermediate hops. If a page has no equivalent, redirect to the category, not to the home page.
| Migration situation | Correct handling | Common mistake |
|---|---|---|
| Same page, new URL | 301 to the new URL | 302 or nothing |
| Merged pages | 301 to the merged page | leaving a 404 |
| Removed product | 301 to the category | redirect to home |
| Domain change | 301 at server level | meta refresh only |
| Move to HTTPS | 301 from http to https | mixed content |
| New language structure | 301 plus hreflang | missing hreflang |
Test the map before launch. A script that walks the whole list and records the response code takes minutes and catches the errors that otherwise surface a week later.
Preparing the content
The most expensive mistake in a redesign is "we will write the copy at the end". The result is a new site with two hundred words per page instead of the previous thousand, and lost rankings.
Move the content of your winning pages across verbatim, then improve it. Keep the H1 and H2 headings if they work. Keep meta titles and descriptions unless they are obviously weak. Carry over the structured data too, including FAQ sections.
If the new design cannot fit the text, the problem is the design. Content is why people come.
Going live
Choose the day carefully. Tuesday or Wednesday morning, never Friday afternoon and never before a holiday. You need at least two working days with the team available.
The steps in the order we run them. Put the new site on a staging URL closed to indexing. Check every template, form and payment path. Take a full backup of the old site, including the database. Push live. Immediately check that robots.txt is not blocking the site, because a forgotten "Disallow: /" from staging is a classic. Check that the noindex meta tag is gone. Run the redirect checking script. Submit the new sitemap in Search Console. Confirm the SSL certificate covers all subdomains. Confirm tracking code is in place and events are recording.
Keep a rollback plan. If something breaks badly in the first hours, reverting to the old version is wiser than improvising under pressure.
The first thirty days after launch
Expect fluctuation. A drop of ten to twenty per cent in organic traffic over the first two weeks is normal after a large structural change. Google has to crawl and re-evaluate everything.
Monitor daily in week one: crawl errors, 404 pages, speed, conversions. Monitor weekly for the rest of the month.
Warning signs that need same-day intervention: a drop over forty per cent, a spike in 404 errors, important pages vanishing from the index, form conversions stopping.
If traffic has not returned to baseline after six to eight weeks, the problem is systemic rather than temporary. The usual causes are missing redirects, thinned content, and a new internal linking structure that cut important pages off.
Hosting and the technical base
A migration is a good moment to change hosting too, if the old one was a problem. A new site on a slow server stays a slow site. We covered the practical criteria in the piece on choosing hosting, and there are separate notes on speed in the article on PageSpeed.
When changing host, keep the old account active for at least thirty days. It costs little and once in ten projects it saves the day.
Frequently asked questions
Will I lose rankings during a redesign
Temporarily, almost certainly. Permanently, no, provided URLs are redirected correctly and content is preserved. Normal recovery takes three to eight weeks. Permanent loss comes from mass 404 errors, from redirecting everything to the home page, and from cutting text drastically.
Should I change my page URLs
Only with a concrete reason: an illogical structure, old URLs full of parameters, a change in the language scheme. If the current URLs are readable and working, keep them. Every URL change is a risk without a guaranteed gain.
How long does a redesign take
For a small business card site of up to fifteen pages, usually three to five weeks. For a corporate site with a blog and several services, six to ten weeks. For an online store with data migration, two to four months. The longest part is almost always the content, not the programming.
Can I launch the new site in stages
Yes, and it is often wiser. You launch a new design on one section, watch the data for two weeks and continue. The approach is slower, but the risk is spread and any problem is easy to trace. It works best on large sites with heavy traffic.
What should I do with the old blog
Move all of it across, including old posts that still get traffic. If some articles are outdated, update them at the new URL rather than deleting them. Deleting an archive with links and rankings is a pure loss, and an update usually brings the page back higher than it was.
Next step
A successful redesign looks boring from the outside: the same URLs or correct redirects, the same content in a better form, the same numbers that start climbing a month later. Drama only happens where the preparation was skipped.
If you are planning a new site or a migration, write to us through the contact page. We audit the current state and send an individual quote within 24 hours. See also how we approach website development.
