2025-09-24 · Baduno Editorial Team · 7 blog.readMin · Blog & Knowledge
Website Relaunch Without Visibility Loss: The Checklist
The classic relaunch accident: beautiful new website, halved traffic. Avoidable – with discipline in redirects and timing.
Before the Move: Inventory
Capture all indexed URLs (sitemap, Search Console, crawler) and document their rankings. What you don't know, you can't redirect – that's where most losses occur.
The Core: 301 Mapping
Each old URL receives a permanent redirect to its best new equivalent – individually, not blanket to the homepage. For multilingual sites, this applies per language version; the hreflang matrix must move to the new URLs.
Move Day
Test redirects before going live, submit new sitemap immediately, keep old sitemap temporarily accessible, sharpen monitoring. The first week in Search Console shows whether Google understands the move.
What is Fluctuation and What is Alarm
A few weeks of unrest are normal. Alarm signs are mountains of 404s in the coverage report and ranking losses on money pages – then redirects are missing, and every week of waiting costs permanent positions.
Structural SEO: page architecture and URL hierarchy
A relaunch is the opportunity to optimize the page structure. Flat hierarchies (max three clicks to the target page) improve crawl efficiency. Make sure your most important content does not get lost in navigation. Avoid deep folder structures (e.g., /de/produkte/kategorie/unterkategorie/produkt.html); better: /de/produkt/produktname. Maintain meaningful breadcrumbs that provide context for both users and search engines. Example: An online shop with a thousand products restructures them by product categories instead of brands, which strengthens internal linking and distributes PageRank more evenly. A flat URL model also facilitates hreflang linking in multilingual projects. Plan the new page architecture before mapping, otherwise you'll have to adjust dozens of URLs afterwards – time you don't have.
Crawl budget and indexing: Priorities for Google
With every relaunch, the number of new URLs to be crawled increases. At the same time, Google loses track of old paths. Use robots.txt to exclude unimportant resources (e.g., dynamic filters, internal search results). Use canonical tags only for truly identical content – not as a crutch for poor mapping. Check crawl statistics in Search Console: if the number of crawled pages drops, you may be blocking too much. Example: A news portal builds a new CMS and suddenly links thousands of archive pages without added value – that wastes crawl budget. Better: only mark archives with noindex or limit to yearly archives. Use the 'last modified' indication in the sitemap to signal to Google which pages are truly new. That way you won't drown in the crawl delta.
Content migration: texts, metadata, and duplicates
Not only URLs change – content is often editorially revised as well. A relaunch is the ideal time to update outdated texts. But this carries risks: if the content changes significantly, Google may reassess relevance. Keep core pages (with high rankings) as close to the original as possible until the new URLs are established. Adjust metadata (title, description) only if they no longer fit – and then one-to-one. Example: A B2B service provider changes the claim on the homepage from "fast" to "sustainable". Google interprets this as a topic shift and rankings collapse. Better: roll out the new claims four weeks after the move, when redirects are stable. Watch out for duplicates: if two old URLs land on the same new one (e.g., due to merging), set a canonical to the desired one. Otherwise conflicts arise.
The classic relaunch accident: beautiful new website, halved traffic. Avoidable – with discipline in redirects and timing.
Monitoring and rollback: The emergency plan
Even with the best planning, something can go wrong. Before the relaunch, define which KPIs to check daily: impressions in Search Console, position changes of top 20 pages, crawl errors (404/500). Use a tool that automatically alerts you if traffic drops more than 20%. Have a rollback scenario ready: a backup of the old website including all redirects. If no improvement occurs within 48 hours – for instance, a mountain of over 100 404s – you should be able to flip the switch. Example: An e-commerce shop launches a new product search that suddenly redirects all filter URLs to the homepage. The rollback restores the old redirect mask until the issue is resolved. Communicate the plan with the development team; a relaunch is not a sprint but a finely tuned gearbox.
International orientation: migrating hreflang tags and language versions
For multilingual websites, the correct migration of hreflang tags is one of the biggest challenges when relaunching. Every old URL that redirects to a new one must be updated in the hreflang matrix of all language versions. A common mistake: adopting the old hreflang annotations on the new URLs without checking whether the target pages are actually equivalent. Therefore, before the migration, create a complete hreflang mapping table in which you record the equivalence for each page in all languages. Use the x-default annotation for non-language-specific content. Ensure that hreflang tags are self-referential – each page must reference itself. For large projects, AI can suggest the linking, but manual verification is essential: a German-language product text that is incorrectly marked as a duplicate with the French variant will lead to massive drops in visibility. Use the hreflang sitemap as an additional control. Validate the tags before launch with online tools. Leave the old hreflang tags temporarily until Google has crawled the new ones. This prevents language versions from suddenly being considered orphaned and falling out of the index.
Quality Assurance: Manual Review as a Crucial Step
As much as AI and automation accelerate the relaunch, manual quality assurance remains indispensable. Before going live, schedule a systematic spot-check: randomly select 50 to 100 old URLs from different areas (homepage, categories, products, blog) and verify that the redirect leads to the correct new page. This involves not only the technical redirect but also content alignment: Is the text complete? Are images, videos, and downloads accessible? Is tracking working? Particularly critical are pages with high rankings or revenue – here, every single URL should be checked manually. Involve editors and QA testers who are not familiar with the mapping: they often uncover usability issues that developers overlook. Example: An old product page technically redirects correctly to the new one, but the description is missing – the customer leaves. Use a checklist with criteria: redirect type (301 instead of 302), loading time, consistency of navigation, functionality of forms and search fields. Perform the review on a staging server that mirrors the exact live environment. Document all discrepancies and have them fixed before flipping the switch. After launch, repeat the spot-check – the error rate decreases with each pass.
Backlink Migration and External References
Backlinks are trust signals pointing to your old URLs. During a relaunch, you must ensure these links do not end up dead. Before the migration, identify the most important backlink sources (e.g., via Google Search Console or specialized tools). Document the referring domains and linked URLs. After the relaunch, contact the webmasters of the referring pages and ask them to update the links to the new URLs – especially for editorial articles, press releases, or partner pages. Alternatively, ensure your 301 redirects remain permanent; Google passes link juice through the redirect as long as it is stable. Ensure that redirects are not chained (e.g., from old to intermediate to new), as this can dilute link equity. Example: An industry portal links to your old study. If the 301 is correctly set, the new URL benefits from the link value. Check after four to six weeks in Search Console whether the referring links point to the new targets. Also use your own internal linking: replace all old internal links in your content management systems with new ones, otherwise dead ends will occur. A thorough backlink audit before the relaunch prevents later ranking losses. Migrating external references is time-consuming but essential for your brand's visibility.
Performance and Core Web Vitals during the Relaunch
A new website often means a changed frontend – and with it, potentially new performance issues. Before the relaunch, measure the Core Web Vitals of your current site (LCP, FID/INP, CLS) and define target values for the new site. Largest Contentful Paint (LCP) is particularly critical: it should be under 2.5 seconds. Optimize images, use lazy loading for off-screen elements, and avoid render-blocking JavaScript libraries on key pages. Cumulative Layout Shift (CLS) is often caused by late-loading fonts or dynamically inserted banners – reserve space in the layout. A relaunch is the ideal time to switch to a leaner CMS or implement server-side caching. Example: An online magazine with many images switches to a new theme and doubles its load time. The result: higher bounce rate and worse rankings. Test all core pages with Lighthouse and PageSpeed Insights, including on mobile devices. Ensure that the new page's load time is not worse than the old one – otherwise you risk ranking losses and a poorer user experience. Document performance values before and after the go-live and cross-reference them with Search Console. Improved load times can positively impact indexing, as Google preferentially crawls fast pages.
blog.faqT
How long does it take for Google to fully index the new URLs?
After a relaunch, it can take two to six weeks for Google to discover and index all new URLs. The duration depends on the number of pages, crawl frequency, and the quality of the new sitemap. Submit the sitemap immediately and ensure the old URLs redirect cleanly. Monitor the coverage report in Search Console; if many 'Not indexed' pages appear after four weeks, check crawlability.
What can be done if rankings drop after the relaunch but no 404 errors occur?
A ranking loss without 404 errors often indicates quality issues: changed content, incorrect canonical tags, or internal link structure. Compare the current page version with the old one in the cache (Wayback Machine). Check whether important internal links point to the new URLs or to old (redirected) ones. Loading speed may also have deteriorated. Analyze Search Console for manual actions or algorithm updates. Usually, a gradual reversal of changes on the affected pages helps.
