Website Migration Monitoring: How to Avoid Traffic Losses During a Relaunch

Why Migrations Are So Risky

During a website migration, numerous technical parameters change simultaneously: URLs, server configuration, DNS settings, SSL certificates, content structure, and often the frontend as well. Each of these changes can have unexpected side effects. A forgotten redirect leaves a page that has ranked well for years pointing to nothing. A misconfigured server responds with 500 errors. An expired SSL certificate blocks access completely. And all of this potentially goes unnoticed if no monitoring is active.

Google's John Mueller has repeatedly emphasised that migrations inherently involve temporary ranking fluctuations, even when everything is technically implemented correctly (Google Search Central Blog). Googlebot needs to crawl the new URLs, process the redirects, and update the links in the index. This process takes weeks to months. Technical errors extend it significantly. Professional monitoring shortens the reaction time to problems and thus minimises the impact.

Before the Migration: Capture Baseline and Prepare

Document the Performance Baseline

Before changing anything, fully document your website's current state. This baseline is your reference point for everything that happens after the migration. Capture the following: uptime statistics for the last 30 days, Core Web Vitals (LCP, INP, CLS) for the most important pages, Lighthouse scores for Performance, Accessibility, Best Practices, and SEO, current rankings for your most important keywords, organic traffic from Google Search Console, all existing 301 redirects, and response times for the most important endpoints. XICTRAQ captures this data automatically through performance monitoring and stores historical values that you can use as a comparison basis after the migration.

Set Up Monitoring Before the Migration

Do not set up monitoring during the migration but at least two weeks beforehand. This gives you a stable data foundation and allows you to compare immediately after the migration. Configure the following checks in XICTRAQ: uptime monitoring at 30-second intervals for the most critical pages, SSL monitoring for all domains and subdomains, DNS monitoring to track DNS propagation after the migration, Lighthouse checks for the top 10 pages by traffic, and security header checks to verify server configuration.

Prepare the Redirect Map

The most common mistake during migrations is missing or faulty redirects. Create a complete redirect map that maps every old URL to its corresponding new URL. Use exclusively 301 redirects (permanent), not 302 (temporary), so search engines understand the redirect as a permanent change. Check the redirect map for common errors: redirect chains (A redirects to B, B to C), redirect loops, unreachable destination URLs, and missing redirects for high-traffic pages. According to Screaming Frog, forgetting even a handful of redirects means permanently losing traffic and rankings, which is why every old URL should be checked against the redirect map (Screaming Frog Migration Guide).

During the Migration: Activate Real-Time Monitoring

The phase during the migration is the most critical. This is when most errors occur, and the consequences are most severe. Activate the tightest monitoring interval available. XICTRAQ offers check intervals from 30 seconds that you can temporarily enable for the migration phase. During a migration, you should monitor the following aspects in real time.

Verify HTTP Status Codes

After the DNS switch and the go-live of the new environment, every critical URL must return an HTTP 200 status. 5xx errors indicate server problems, 4xx errors indicate missing pages or faulty redirects. XICTRAQ checks the HTTP status code with every check and alerts immediately when a monitor returns an unexpected status. Pay particular attention to the homepage, the most important landing pages, the shop checkout (if applicable), the sitemap, and robots.txt.

Ensure SSL and HTTPS

When switching hosting, the SSL certificate is one of the most frequent sources of error. The old certificate is not valid on the new server, and Let's Encrypt can only issue once DNS propagation is complete. In the meantime, the browser shows a security warning that deters virtually all visitors. Plan the SSL switch carefully: issue the new certificate before the migration if possible, or use a DNS challenge mechanism. SSL monitoring from XICTRAQ detects certificate problems within seconds.

Monitor DNS Propagation

After a DNS change, full propagation takes between a few minutes and 48 hours depending on the TTL setting. During this phase, users at different locations may receive different server responses: some see the old website, others already see the new one. Multi-location monitoring from XICTRAQ checks from multiple European locations and shows you in real time where propagation is complete and where it is not.

After the Migration: Long-Term Monitoring and SEO Recovery

The First 48 Hours: Critical Monitoring Phase

The first two days after migration are decisive. This is when most problems that were overlooked during the migration surface. Maintain the tight monitoring interval and actively verify: that all main pages load correctly and display the expected content, that all forms and interactive elements work, that the checkout process runs smoothly, that tracking and analytics deliver correct data, and that robots.txt and the sitemap are served correctly. The screenshot changelog from XICTRAQ is particularly valuable during this phase: it visually shows how your pages have changed before and after the migration, helping identify unintended design changes or missing content.

Systematically Find 404 Errors

Even with careful redirect planning, 404 errors typically remain after a migration. Internal links point to old URLs not captured in the redirect map. External backlinks from other websites point to URLs that have changed. And search engines still have old URLs in their index that are not correctly redirected. Monitor Google Search Console for 404 errors and set up monitors in XICTRAQ for the most important entry pages. Every 404 error on a formerly well-ranking page represents a direct SEO loss that should be fixed with a correct redirect as quickly as possible.

Evaluate Post-Migration Performance

A migration is often an opportunity to improve performance, for instance through a faster server or a leaner CMS. Equally often, however, performance unintentionally deteriorates. Compare the Core Web Vitals and Lighthouse scores of the new environment with the baseline captured before migration. Pay particular attention to LCP degradation from unoptimised images on the new server, CLS issues from changed layouts or new fonts, higher server response times (TTFB) from a different server configuration, and new third-party scripts added during the relaunch.

Track SEO Recovery Long-Term

Even with a technically flawless migration, temporary ranking fluctuations are normal. Google needs to crawl the new URLs, process the redirect signals, and update the index. Experience shows this process takes a few weeks to several months, longer for larger websites (Moz Migration Study). Track the following metrics for at least 3 months after the migration: overall organic traffic and per page, positions for your most important keywords, the number of indexed pages in Google Search Console, and crawl statistics. If no recovery is visible after 4 weeks, there is likely a technical issue that requires a renewed analysis.

Migration Checklist for Different Scenarios

Hosting Switch

With a pure hosting switch, the domain and URLs remain identical. The main risks lie with DNS propagation, SSL certificates, and server configuration. Monitoring focus areas: uptime during the DNS switch (30-second interval), SSL validity on the new server, server response times compared to baseline, and security headers that must be correctly set on the new server.

CMS Switch and Relaunch

A CMS switch typically changes the URL structure, requiring a complete redirect map and significantly increasing SEO risk. Monitoring focus areas: redirect functionality for all migrated URLs, 404 errors in the first weeks, performance comparison with the baseline, visual verification via screenshots, and content completeness. For a WordPress project, additional security considerations apply.

Domain Change

A domain change is the riskiest form of migration. All external backlinks, all social media references, and all user bookmarks point to the old domain. You need a permanent 301 redirect from the entire old domain to the new one. Monitoring focus areas: redirects for all pages on the old domain, DNS configuration for both domains, SSL certificates for both domains, indexing of the new domain in Google Search Console, and domain expiry of the old domain, which you should renew for at least two more years.

Minimise Migration Risks with XICTRAQ

XICTRAQ provides an integrated monitoring solution covering all aspects of a website migration. Instead of running separate tools for uptime, SSL, performance, and SEO, you monitor everything in a single dashboard. This not only saves time but ensures no monitoring dimension is forgotten. For agencies that regularly perform migrations for clients, XICTRAQ additionally offers white-label monitoring to provide clients with professional migration reports under their own brand.

Start with a free demo and set up monitoring for your upcoming migration. The sooner you capture the baseline, the more meaningful the comparison data will be after go-live. XICTRAQ is the safety line that transforms your relaunch from a risk into a controlled project.