Website Relaunch Without Losing Rankings: Guide and Checklist

You can relaunch a website without losing rankings if SEO is planned from the concept phase: you record the old pages and their value, redirect every old URL with a 301 to the matching new page, carry over content and structure, check the technology before go-live and monitor the numbers closely afterwards. Most drops are not caused by the new design but by avoidable mistakes in URLs, content and indexing.

Search engines have known your website for years: which pages exist, what they are relevant for and how they are linked. A relaunch – whether a new design, a new CMS, a store migration or a domain change – calls all of that into question at once. AI-assisted search also draws on your content; if you lose pages or weaken content, you are often missing there too. The following guide takes you through the project in six phases and ends with a list of typical mistakes.

Where rankings get lost in a relaunch

Cause	Typical consequence	Countermeasure
Changed URLs without redirects	Well-ranking pages return error pages, links from other websites lead nowhere	Redirect plan with one-to-one mapping
Blanket redirect to the homepage	Google may treat it as a soft 404, and visitors do not find their topic	Thematically matching target, otherwise a deliberate 404 or 410
Deleted or shortened content	Pages lose the search terms they were previously found for	Content comparison for all prioritized pages
Changed internal linking	Important pages slip deeper into the structure and lose weight	Plan navigation and linking in advance
Indexing blocks from the test environment	The website gradually disappears from the index	Go-live check for noindex, robots.txt and canonical tags
Content visible only after scripts load, long load times	Pages are captured less reliably and users bounce	Key content in the delivered HTML, measure load times

Preparing: inventory, redirect plan and content

Phase 1: Inventory and prioritiza­tion

Before you change anything, you need a complete picture of the current state – as a file, not in your head. Secure this data before the first change:

• Crawl of the old website: all reachable URLs with status code, page title, headings and canonical tag
• XML sitemap and log files: a comparison of which pages Google actually requests
• Google Search Console: clicks, impressions and queries per page – export them, because the interface only shows about 16 months
• Web analytics: landing pages and conversions, so you can separate revenue pages from pure traffic pages
• Backlinks: which pages other websites link to

The result is a priority list. Pages with a lot of visibility, backlinks or conversions – the A pages – get the highest level of care in the relaunch. Also archive a complete snapshot of the old website, including titles, meta descriptions and copy; it helps later with comparisons and troubleshooting.

Phase 2: The redirect plan

The heart of every relaunch is the mapping of old to new URLs. Every old address gets a permanent 301 redirect to the most relevant new page. Maintain the plan as a table so it can be checked automatically before go-live:

Old URL	New URL	Rule
/service/webdesign.php	/services/web-design/	One-to-one, A page with backlinks
/produkte.php?kat=12	/products/pumps/	Pattern for product categories
/blog/2019/old-post	/guides/current-article/	Thematically matching successor
/promotions/summer-2021	410 Gone	Deliberately removed, no alternative

• Direct instead of chained: every redirect reaches its target in one step – including http to https, www and trailing slashes.
• Patterns plus manual work: solve large inventories with rules, for example for product paths; map the A pages individually.
• Miss nothing: PDFs, images, and category and filter pages can bring visitors and links.
• Link internally to the new URLs: internal links point to the new URLs, not to redirects.
• Lifetime: keep the redirects for at least a year, ideally permanently.

Phase 3: Carrying over content, structure and data

A relaunch is a good opportunity to improve content – but no reason to delete proven content. For every A page, check that core statements, headings and relevant terms are kept; carry over page titles and meta descriptions or improve them deliberately. Google primarily evaluates the mobile version: it must contain the same content, structured data and meta information as the desktop version.

Important pages should be reachable from the homepage and navigation in a few clicks. Structured data – for example on organization, articles, breadcrumbs or products – and, on multilingual websites, language annotations (hreflang) belong on the new website as well. Also ask one question of every page: does it directly answer what your customers are looking for? Clear answers help in Google and in AI search; read more under Generative Engine Optimization.

Executing: technical check, go-live and domain change

Phase 4: Technical check on the test environment

The new website is built on a staging environment protected by a password. Password protection is safer than a robots.txt block alone, because blocked URLs can still appear in the index if other pages link to them. Before go-live, check the following:

Check	Target state
Indexing	No noindex or Disallow on the live version; the test environment's password protection is not carried over
Canonical tags	Point to the live URL, not to the test domain
Status codes	Key pages return 200, old URLs return exactly one 301, no chains
XML sitemap	Contains only indexable pages with status code 200 and the live domain
HTTPS	Valid certificate, redirect from http to https, also for the old domain
Load time	Core Web Vitals at least at the old level; good values are LCP up to 2.5 seconds, INP up to 200 milliseconds, CLS up to 0.1
Mobile view	Same content and functions as on desktop
Tracking	Web analytics, consent and conversion measurement work

How to measure and improve these values is covered in our article on Core Web Vitals in practice. Also check whether key content sits directly in the HTML: pages whose text only appears after heavy scripts are sometimes captured less reliably or with delay by search engines and AI crawlers.

Phase 5: Go-live day

1. Switch the website to the live environment and remove password protection and test blocks
2. Check indexing blocks and canonical tags on the live version
3. Crawl the old website's URL list against the redirect plan: status code, target, chains
4. Submit the sitemap in Search Console
5. Test forms, tracking and conversion measurement

Do not schedule go-live for a Friday afternoon, before a vacation or in your peak-revenue week. Freeze content changes on the old website shortly beforehand, and keep someone available in the first days who can adjust quickly.

Special case: domain change

If the domain changes as well, complexity increases. All addresses on the old domain redirect permanently to the corresponding new address, and in Search Console you report the move with the change-of-address tool. Keep the old domain for the long term so that redirects and links do not lead nowhere. Also update your Google Business Profile, ad accounts, social media profiles and email signatures, and ask key partners to update their links.

Phase 6: Monitoring after go-live

Slight fluctuations are normal in the first weeks because search engines need time to process the new structure. What matters is finding errors quickly:

• First week, daily: page indexing and crawl errors in Search Console, server errors, 404 reports
• Weekly after that: clicks, impressions and positions of the A pages, compared with the period before the relaunch and – because of seasonal effects – with the previous year
• Ongoing: inquiries, orders and conversions in web analytics
• Missing redirects: analyze 404 reports and close gaps in the redirect plan

After a few weeks, take stock: which pages gained, which lost? Where losses persist, check the affected page in this order: technology (status code, indexing, canonical), redirect, content and internal linking.

Practical example: a specialist wholesaler switches its CMS

Suppose a specialist wholesaler moves from an outdated system to a new CMS, and the product pages get new paths. The crawl returns several hundred URLs. The Search Console analysis shows that a small share of the pages – homepage, main categories, a few guides – brings most of the clicks. These A pages are mapped individually and their content is carried over one to one. A rule handles the product paths, and discontinued items get a 410 and a pointer to the category. After go-live, the team crawls the old URL list again, closes the gaps it finds and compares the clicks of the A pages every week. This keeps the effort manageable and protects the pages that matter.

Common relaunch mistakes

• SEO is only considered after go-live, when structural decisions have long been made.
• All old URLs are redirected to the homepage across the board.
• Noindex, a robots.txt block or canonical tags of the test domain are carried over to the live website.
• Domain, URL structure, design and copy are changed all at once; if losses occur, the cause is hard to find. Better in stages, if the project allows it.
• There is no measurement before the relaunch, so gains and losses cannot be proven.
• Redirects are removed again after a few months.

How Nano Concepts can help

We support your technical SEO relaunch from the inventory and redirect plan through to monitoring after go-live. Together with our partner agency LOMA DESIGN, we can also take on web design and web development for the new website. We clarify the right framework – Starter from €2,500, Professional from €8,000, Enterprise individual – in a free initial consultation, as well as which pages of your website need particular protection.