Traffic dropped after a website migration: First 48-hour checklist and a lasting solution

How are old URLs mapped to new addresses with 301 redirects?

Every old URL is connected to the new URL with the closest matching content using a server-side permanent redirect (301 or 308). Google’s migration documentation recommends preparing this mapping as a list in advance and collecting old addresses from the content management system, server logs, analytics data, and sitemaps.

According to Google’s redirect documentation , Google treats permanent redirects such as 301 and 308 as a signal that the redirect target should be accepted as the canonical address. With temporary redirects such as 302 and 307, Google follows the redirect but does not use that signal to make the target the canonical page. Using temporary redirects during migration can leave old addresses in the index. Redirect types and how to configure them in WordPress are also explained in the 301 redirect guide .

The migration documentation recommends keeping redirects for as long as possible, generally at least 1 year; this gives Google time to transfer all signals to the new addresses. This is also why it is important not to let the old domain expire.

Redirect chains and mass redirects to the homepage

An old address should go directly to the final address. Adding new redirects on top of those left from an earlier redesign creates chains from A to B and B to C. Google’s documentation recommends keeping chains short, ideally no more than 3 and fewer than 5; every additional step adds a delay.

The second warning in the documentation is to avoid redirecting many old URLs to a single unrelated address such as the new website’s homepage. Google considers this confusing for users and may treat it as a soft 404. For an old page without a direct equivalent, choose the closest category or service page; if there truly is no equivalent, leaving a 404 is an honest response.

SEO for domain changes: When is the Change of Address tool used?

The Change of Address tool in Search Console is used only when moving from one domain to another domain (or subdomain). It is not used when moving from HTTP to HTTPS, changing between www and non-www versions, changing paths on the same domain, or moving hosting without changing URLs.

According to Google’s Change of Address tool help page, using the tool requires being a verified owner of both the old and new properties in Search Console and configuring a 301 redirect from the old homepage to the new homepage. The tool’s effect lasts 180 days; during that time, Google transfers signals from the old website to the new one and prioritizes indexing the new address.

The tool does not perform a migration on its own; it does not replace page-level 301 redirects, but adds a notification on top of them. During a domain change, also check for a staging copy left accessible on the old domain or a subdomain that has not been redirected.

Google rankings dropped after the new website: Content and heading loss

If Google rankings dropped after the new website launched, examine the content itself as well as technical settings: if the text, headings, and page titles that the page ranked for changed in the new design, Google may assess it as a different page. “Simplifying” content during a visual redesign is a common source of loss.

The following content changes are most frequently seen in redesigns:

• Reducing long service descriptions to a few lines or hiding them inside tabs or sliders
• Losing H1 and H2 headings and adding text as lettering on images
• Failing to migrate blog posts or regional pages that brought traffic on the old website
• Failing to transfer page titles and meta descriptions from the SEO plugin, so every page displays the same title
• Combining multiple pages into a single page and removing the focus keyword from the text

To check, list the old website’s highest-traffic pages and compare each with its new equivalent in terms of text, headings, and page title. An archived copy or backup taken before migration makes this comparison easier. The general framework for the timing and scope of a redesign is in the corporate website redesign guide .

Do internal links, images, and structured data still point to old addresses?

If internal links, image addresses, and URLs in structured data have not been updated to the new addresses, the website itself continues to show Google the old addresses. Pages open if redirects exist, but every click and crawl passes through an unnecessary redirect.

Google’s migration documentation recommends updating internal links to new URLs and including the addresses of embedded content such as videos, images, JavaScript, and CSS in the migration plan. If old addresses in the WordPress database are not replaced in bulk when the domain changes, menus, in-post links, and image paths continue pointing to the old domain.

Other overlooked points include:

• Structured data: The url, logo, and image fields in Organization, LocalBusiness, or Article markup
• Multilingual websites: Addresses in hreflang tags
• External profiles: The website link in Google Business Profile, social media accounts, and directories
• Advertisements: Landing page addresses in Google Ads and other campaigns

Hosting migration and speed: Why does traffic drop without URL changes?

When only the hosting moves and addresses remain unchanged, a short-term crawl decrease is normal; a persistent decline usually indicates server slowness, timeouts, or a setting blocking Googlebot. In that case, the problem is in the infrastructure rather than the content.

Google’s site moves without URL changes documentation states that a temporary decrease in Googlebot’s crawl rate immediately after launch is normal when hosting changes, followed by a steady increase over the next few days. The same document recommends lowering the DNS TTL to a low value such as a few hours at least a week before migration, and keeping the old hosting running until server logs show no remaining traffic.

Check the following on the new server: page load times, whether the PHP version and cache settings have been transferred, whether the firewall or bot protection settings block Googlebot, and whether the SSL certificate is valid for all versions (www and non-www). Crawl statistics in Search Console are the first place to look because they show the server’s responses to Googlebot.

How long does traffic loss after a website redesign last?

Google states that on a medium-sized website, replacing old URLs with new ones can take a few weeks or more, and that the process can take longer on larger websites. Ranking fluctuations are expected during this period; Google’s documentation does not provide a specific recovery date.

Time alone is not enough to determine whether traffic loss after a redesign is temporary or persistent; examine the trend. If the number of old URLs in the index is decreasing while new URLs are increasing and new pages are starting to receive impressions, the process is progressing correctly. If new pages are not being indexed, impressions stay at zero, or “noindex”, “404”, and “redirect error” warnings increase, waiting will not solve the problem.

The migration documentation recommends moving all URLs at once for small and medium-sized websites; this helps Google recognize the migration faster. Moving large websites in sections is also possible. If the website does not appear on Google at all, the problem is different from fluctuation; its causes are covered in the website not appearing on Google guide .

What should be monitored in Search Console?

After migration, monitor three Search Console reports regularly: Page indexing, Sitemaps, and Performance. Together, they show whether old addresses are leaving the index and new ones are taking their place.

• Page indexing: Among the reasons in Google’s Page indexing report documentation, monitor increases in “Not found (404)”, “Excluded by ‘noindex’ tag”, “Blocked by robots.txt”, “Redirect error”, and “Duplicate, Google chose different canonical than user”.
• Sitemaps: The migration documentation states that old and new sitemaps should be submitted together for a while, monitoring whether the indexed count from the old sitemap falls while the new one rises, after which the old sitemap can be removed.
• Performance: Compare periods before and after migration using the date filter; the pages tab shows which URLs lost clicks and impressions and which new URLs started receiving impressions.
• URL Inspection tool: Inspect important pages individually; this shows Google’s selected canonical URL and whether the page can be indexed.

How to read these reports is explained step by step in the Google Search Console usage guide . If the domain changed, a separate property must be created and verified for the new domain; keep the old property for comparison.

A preventive plan before migration

Much of the traffic loss can be prevented with a plan prepared before migration. In our migration process, the following steps are completed before launch day:

1. List all old website URLs and traffic-generating pages; export and retain Search Console and analytics data.
2. Prepare an old URL → new URL mapping table; decide what to do with pages lacking equivalents.
3. Keep the staging website blocked with robots.txt or noindex, and note the barriers to remove on launch day.
4. Transfer the text, headings, page titles, and meta descriptions of important pages to the new website in full.
5. Back up files and the database; lower the DNS TTL in advance.
6. Test redirects on launch day, check for chains, and submit the new sitemap.
7. If the domain changed, use the Change of Address tool and update links on external profiles.
8. Monitor Search Console reports regularly during the first weeks; retain the old domain and redirects for at least a year.

When should you consult a specialist if traffic dropped after a website migration?

Specialist support saves time if noindex, robots.txt, and canonicals appear clear after the first 48-hour checks, but new pages remain unindexed as weeks pass, or 404 and redirect errors increase. The process should be systematic, particularly when hundreds of old URLs need mapping, the domain also changed, or no backup of the old website is available.

If migration has not happened yet or remains incomplete, the WordPress website migration service covers the redirect list, backup, DNS, and Search Console steps together. If migration is complete but the loss continues, the technical SEO service examines crawling, indexing, and content losses in detail. At Onur Freelance, monthly SEO starts at 9,000 TL, while a new corporate website starts at 15,000 TL.

The required approach depends on the website’s size, the migration type, and the data still available. Diagnosis is much faster if Search Console and analytics data from before migration have been retained.