WEBSITE / OCTOBER 18, 2026
Website relaunch: preventing SEO losses before launch
A new look can be the right move. But for Google and for regular customers, it must remain clear where each important old page leads and whether the new answer still serves the same question.

A website relaunch often starts with a design draft. The riskiest questions, however, lie outside the design file: which existing pages bring suitable visitors? Which URL gets which job after the rebuild? Who checks whether the new website is actually accessible and indexable on the day of publication? Anyone who records these decisions before launch saves themselves hectic cause analysis later.
Securing the important pages before the website relaunch
First list the existing URLs. The navigation alone is not enough: guides, older service pages and image files may still be visited or linked even though they are missing from the current menu. For a move, Google recommends the sitemap, usage data, server logs and link data, among other things, as sources for a URL inventory. For a small business, it is especially important to mark the pages that deliver qualified enquiries, local visibility or recurring information.
Create a baseline note: URL, job of the page, important search queries, clicks and enquiries, as far as reliably recorded. A page with little traffic can still be decisive if it explains an expensive specialist offer. A frequently visited page can be less relevant commercially. This distinction belongs in the owner’s decision before the new structure is fixed.
Ask explicitly what changes in the relaunch. Do URLs, content and domain stay the same, and is it mainly the design that is revised? Then a large redirect matrix is not the focus. If paths, language, CMS or domain change, mapping old and new URLs becomes the core of the project. The word “relaunch” alone does not say how risky the intervention is.
For every important old URL, it must be decided: does it stay, does it get a genuinely matching new target page, or is it dropped for a reason? “Everything to the home page” is not a content mapping.
Mapping old and new URLs sensibly
If an address changes, the old URL needs a new target that offers the same or a clearly corresponding content. Redirecting a former “heat pump maintenance” page wholesale to the new home page takes away the answer visitors were looking for. If the offer continues, a matching new service page should be the target. If it is discontinued, the business has to decide which information is still honest and helpful for previous visitors.
Google recommends server-side permanent redirects, such as 301 or 308, for permanently moved URLs. At the same time, internal links should point to the new addresses. Also check canonical tags and the sitemap. A redirect can bring visitors to the right page; outdated internal links and contradictory canonicals still make the new system look unnecessarily unclear.
With a domain change, additional ownership and measurement questions arise: who manages the old domain and keeps it reachable? Are both properties accessible in Search Console? Can email addresses, forms and contact channels keep working? These points go beyond SEO but influence whether a prospect can actually reach the business after the change.
Checking indexing and content on launch day
A test environment is often deliberately shielded from search engines. Google reminds you to remove temporary `noindex` rules or crawl blocks when going live. Check a few representative pages: home page, most important service, location page, guide and contact. Does every new URL return the expected HTTP status? Do old URLs point to the matching target? Can the content be read without logging in?
Read the new page, not just the source code. A technically flawless 301 helps little if the target page no longer explains the previous service. Check the heading, scope of service, area, contact route and important images. Test a real enquiry from a mobile device all the way to the inbox. For a page that is not indexed, there is a separate diagnostic path; on launch day, the main thing is not to overlook an obvious staging blocker.
Important new pages still carry `noindex`.
Old service URLs land on a generic home page.
The contact form confirms but delivers no message.
Putting deviations into context after the relaunch
Google points out that with larger changes, temporary fluctuations are possible while old and new URLs are processed again. This is no guarantee that a sharp drop is “normal”. Compare suitable periods in Search Console and concentrate on important groups of pages. If individual moved URLs drop out, first check the redirects, indexing status, canonical and content of this group.
If only enquiries fall while search clicks stay stable, the suspicion lies more with the contact route, clarity of the offer or measurement. If clicks and impressions fall at the same time, a separate analysis of pages and search queries is needed; the article Fewer Google clicks explains this part. A rewritten title line alone does not explain every trend.
Record responsibilities after launch too. The developer can correct redirects and server responses; the editorial team checks content correspondence; the business confirms whether the enquiries fit. A short, regular comparison of these three perspectives is more useful than daily ranking panic. The relaunch is only complete when the most important old paths lead to understandable new answers and the business can reliably handle incoming contacts again.

