The new website is online, everyone is happy, and four weeks later a large portion of organic inquiries is missing. This pattern repeats itself with amazing reliability during website relaunches. It is almost never due to the design and almost always because during the move, addresses, content, and technical signals that Google built up over years have been lost.
A website relaunch without a loss of ranking is therefore not a stroke of luck, but the result of a manageable number of steps that must all happen before going live. This checklist goes through them in order: why rankings are lost in the first place, what needs to be determined before the redesign, what to do on the day of going live, and how to recognize in the weeks following whether everything went smoothly.
Before discussing measures, it is worth looking at the causes. A loss in ranking after a relaunch rarely has a single major cause. Usually, it is a combination of several small oversights that add up.
Addresses change without redirection
This is by far the most common mistake. The new page structure is better, which is why the pages now have different names. Every old address that is not redirected to its new equivalent becomes an error page. Everything that Google and other websites have contributed to this address is lost. With an established website, this quickly affects several hundred addresses, most of which no one has on their radar anymore.
Content is shortened or cut
A relaunch is a good opportunity to clean up, and that is precisely where the damage occurs. An old, visually unappealing block of text might be the very one that has kept the page ranking for years. Removing content without first checking which parts attract visitors means throwing away visibility just to make room.
Internal linking is redesigned
Which pages are accessible from the homepage and the navigation menu tells Google what is important on this website. If a service page that was previously prominently linked is now only accessible via the footer in the new design, it loses weight. This happens silently and is only noticed weeks later.
Technical signals are missing in the new system
Page titles, descriptions, heading structures, image alt texts, and structured data do not transfer on their own during a system change. In many projects, they are updated after the fact, and until then, the site is live and running without these details.
The test environment goes online
Almost every project is built on a staging address that is blocked for search engines. If this block is accidentally carried over during the move, the entire website disappears from the index. This is the most expensive mistake on this list and, at the same time, the easiest to avoid.
The redirect matrix is the most important table in the entire relaunch project
Most of the work for a clean relaunch happens before the first new page is even built. These four things should be set in stone while the old website is still running.
A complete directory of all addresses
Pull a list of every reachable address on the old website. Not just the pages from the navigation, but also blog posts, landing pages from old campaigns, PDF files, and pages that can only be reached via direct links. This list is the foundation for everything else. If you don't have it, you can't set up redirects.
A snapshot of rankings and traffic
Record which search terms currently find which pages and how many visitors they bring. Without this baseline, you won't be able to judge after the launch whether a change is normal or a problem. A screenshot of the most important key figures from the last three months is completely sufficient.
Evaluate content instead of adopting it across the board
Go through the list of addresses alongside the traffic numbers and decide for each page: stay, merge, or discard. Pages with traffic should stay or be merged, never deleted without replacement. Pages with zero traffic and no external links can go. This decision belongs before the design phase, not after.
Know who links to you
Links from other websites often point to a specific subpage rather than the homepage. These exact addresses must absolutely not lead to dead ends. A list of the most important backlinks should therefore be kept alongside the address list, so it is clear which redirects need to be checked with extra care.
Once the preliminary work is done, the launch itself can be planned. These five steps in this order cover the majority of the risk.
Step 1: Set up the redirection matrix
Each old address is assigned a new destination address, entered into a table with two columns. Redirection is permanent, i.e., with status code 301, and always to the content-appropriate page, not generally to the homepage. Google treats a blanket redirection to the homepage as a soft 404 error page and handles it accordingly. Redirection chains over multiple stages are resolved, so each old address points directly to its destination.
Step 2: Carry over page titles and headings
Enter the title, description, and heading structure for each page before it goes live. If a page has performed well so far, there is no reason to reinvent its title as part of the relaunch. Design may change, but content signals should only do so intentionally.
Step 3: Test the technology before anyone sees the page
Three things need to be checked before switching over: the search engine block from the staging environment has been removed, the sitemap contains the new addresses and no old ones, and the security certificate applies to all variants of the domain. This check takes ten minutes and prevents the greatest possible damage.
Step 4: Prepare the measurement
Analytics and Search Console should work on the day of the launch, not a week later. Reconfigure the goals, check whether the tracking code is on all page types, and submit the new sitemap. This is the only way to see immediately if something is wrong.
Step 5: Schedule the launch consciously
Not on Friday afternoon and not before going on vacation. The first two business days after switching over are when errors are noticed and must be fixed quickly. Plan for this time instead of hoping it won't be needed.
After the launch, control decides, not gut feeling
The first 72 hours
Manually access the most important old URLs and check if they land in the right place. Check the Search Console for new error pages and have the new sitemap crawled. If anything stands out here, it can still be corrected in this phase without permanent damage.
The first eight weeks
Some movement in the rankings is normal after a relaunch. Google first needs to fully grasp the new structure. A downward spike in the first two to three weeks is no reason to panic, as long as the curve goes back up afterwards. Anything that is still significantly below the baseline after eight weeks, however, is a real problem and needs to be looked at.
Conclusion
A relaunch doesn't lose rankings because the design changes. It loses them because connections that had existed for years are broken during the move. The list of measures is manageable: know which URLs exist, know which content performs, cleanly redirect every old URL, carry over the technical signals, and pay attention after the launch.
The difference between a relaunch that costs visibility and one that carries it along is not created on the day of going live. It is created in the weeks before, in a spreadsheet with two columns that no one sees and yet decides the outcome.
