Sooner or later every company has to rebuild its website. WordPress slows down, plugins multiply, security updates never end and the design no longer reflects the business. The most common fear is losing, in a matter of weeks, traffic that took years to build. It does happen — but almost always because of avoidable mistakes. This is the process we follow, for example, when migrating sites from WordPress to modern technologies.
1. Take stock of what already works
Before designing a single page, you need to know what is delivering results today:
- a complete list of the current site’s URLs, gathered with a crawler;
- the pages that earn clicks and impressions, from Google Search Console;
- the pages that receive links from other websites.
These pages are the assets to protect. The rest can be merged or removed — but with care.
2. A one-to-one redirect map
Every old URL should point to the closest new URL with a 301 redirect, meaning permanent. Three mistakes to avoid:
- redirecting everything to the home page: to Google this is the same as a missing page;
- using 302 (temporary) redirects instead of 301s;
- creating redirect chains — A to B, then B to C. Every hop loses value.
You also need to settle on a single version of the domain: HTTPS, with or without "www", with or without the trailing slash. Every variant should reach the chosen one in a single step.
3. Keep what Google already knows
The new site can look completely different, but on key pages it pays to keep what rankings rely on: titles, meta descriptions, the main page heading (H1) and the core of the content. Drastically cutting copy for a "cleaner" design is one of the most common causes of traffic drops.
4. Be careful with modern technologies
Many new websites are built with frameworks such as React. If content is generated only in the visitor's browser, search engines may see an empty page or read it late. The solution is pre-rendering: every page is generated in advance with the text already in the code. A simple check: open "view page source" and make sure the text is there.
5. Keep the staging site out of Google
The new site is built on a staging address. That environment must be protected with a password or a "noindex" directive, otherwise Google will index it and treat it as a duplicate. At launch, do the opposite check: remove the noindex from the live site. It is a classic mistake and can wipe out your visibility.
6. Launch day
A minimum checklist:
- redirects live and tested on a sample of old URLs;
- new sitemap.xml submitted to Search Console;
- correct robots.txt file;
- canonical tags and, for multilingual sites, hreflang verified;
- analytics running on the new site.
7. The weeks that follow
Some ranking fluctuation is normal in the first 4–8 weeks while Google reprocesses the site. During this period, check the Search Console reports every week: unindexed pages, 404 errors and failed redirects. Mistakes fixed early leave no trace; those ignored for months do.
In short
A well-run migration does not cost you rankings — it often improves them, because the new site is faster and better organised. It takes method: an inventory, one-to-one 301 redirects, preserved content, pre-rendering and post-launch checks. If you are thinking about rebuilding your company website, explore our web design for companies.
Planning a new website for your company?