A modern office interior showing a person at a desk engaged

When an SEO Migration Looks Successful but Old URLs Still Receive Traffic

An SEO migration can look successful while many visits still arrive through old URLs. Search rankings may stay steady, but visitors still pass through a redirect to reach the new pages. A post-migration SEO audit finds out why these new pages haven’t earned that traffic on their own.

Relying on redirects also creates risks. If a rule breaks or a plugin update removes the redirect file, visitors may no longer reach the right pages. At Motifo, our search engine optimisation team plans and audits site migrations for businesses. We treat steady legacy URL traffic as a sign the move is unfinished.

This guide explains why legacy URLs keep pulling visits and how to find them in Search Console and GA4. You’ll also learn how to audit each redirect chain and which follow-up tasks help the new site hold its own rankings.

Why Do Old URLs Still Get Traffic Months After a Website Migration?

A person seated at a bright office desk

Old URLs still get traffic after a website migration because search engines, linking sites and saved links haven’t caught up with the new addresses. Each source holds its own copy of the old link and updates on a different timetable.

Google search is usually the first source to check, since organic traffic is the main channel for many sites. Until Google recrawls the old address, follows its 301 (permanent) redirect and indexes the new page, searchers keep clicking the legacy result. Google’s site move guidance notes that a large site can need several months for this stage.

Backlinks update on each linking site’s schedule, because another site owner has to edit every link by hand. A listing on a Melbourne business directory can point at a retired path for years. Directory owners rarely edit old entries unless someone asks them. Meanwhile, bookmarks, saved emails and old social posts add a steady trickle of direct visits.

Now, a small amount of legacy URL traffic straight after launch is normal. Search visits to old URLs after website migration should fall steadily as Google swaps in the new pages. The warning sign is old-URL volume that stays flat or grows after the first few months. If those visits come from search, the cause is usually a redirect problem you can find and fix.

Legacy URL Traffic: Where to Find It in Google Search Console and GA4

Search and backlink traffic to old URLs after website migration only shows up when you filter for it. Many saved dashboards track the new URL structure, so old paths collect clicks without anyone noticing.

Google’s guidance on site moves says traffic on the old site should ideally fall while traffic on the new site climbs. To confirm that trend, filter your reports by the old URL structure as well as the new one. If you already use Google Search Console data for keyword work, add a page filter in the Performance report that matches your old folders. After a domain migration, keep the old property verified and submit a Change of Address request.

GA4 (Google Analytics 4) covers the visitor side, although it only records the page that finally loads. If an old path appears as a landing page, you will know the URL still serves content or a 404 error.

Search Console and GA4 cover most of the data, and three extra sources fill the gaps:

  • Search Console Performance Report: Filter the Pages tab by your old folder paths, or by the old domain after a domain change. The report shows which retired URLs still earn impressions and clicks from organic search. Sort by clicks so the busiest old URLs reach your audit first.
  • Search Console Pages Report: Check the “Page with redirect” and “Not found (404)” statuses for old addresses. URLs listed as 404 have lost their redirect or never had one. Export both lists and fix the 404s first.
  • GA4 Landing Page Report: Search the report for old path patterns, such as /blog/2019/ or .php endings. Any match means a visitor reached an old URL and no redirect fired. Note each match’s session count so you can rank the fixes.
  • Server Logs: Your hosting logs record every request to an old URL before the redirect fires. They also capture bookmark and email visits that GA4 only records by their final page. Ask your host for 30 days of logs filtered to 3xx and 404 responses.
  • Backlink and SEO Tools: Ahrefs and Semrush list external links that still point to old URLs. Bing Webmaster Tools adds a free backlink report and a Site Move tool for domain migration. Export each list of linking pages so you can plan outreach later.

Merge every export into one spreadsheet and delete duplicate URLs. The combined file becomes the crawl list for your redirect audit, so your crawl covers each old URL once.

An afternoon office scene where a person leans forward at their desk

Running a Website Redirect Chain Audit on Every Old URL

A website redirect chain audit tests every URL in your spreadsheet and shows where each one finally lands. The audit often uncovers one faulty server rule behind most of the leaked legacy traffic. In our audits, a single bad rule has sent an entire blog folder down the same broken path.

Work through the four checks below in order, since each one builds on the previous export.

1. Crawl the Full List of Old URLs in Screaming Frog

Screaming Frog is a desktop site audit tool, and its List mode crawls only the URLs you upload or paste in. Load your combined spreadsheet there, because a standard crawl of the live site can’t find pages that no longer exist. The free version handles up to 500 URLs, so larger sites need a paid licence.

Before you start, open Configuration > Spider > Advanced before running the crawl. From there, tick “Always Follow Redirects” so the crawler follows redirect paths automatically. With that setting on, the crawler traces every hop to the final page.

Once the crawl ends, export the Redirect Chains report from the Reports menu. The file lists each starting URL, every hop and the final status code for your technical SEO audit.

Spot Chains, Loops and Temporary Redirects

A chain is any old URL that hops twice or more before reaching a live page. Each extra hop adds load time, which can drag down Core Web Vitals scores such as Largest Contentful Paint (LCP). Extra hops also use crawl time Google could spend on your new pages, and Googlebot stops following after 10 hops.

Loops need fixing first, because the redirect cycles back to an earlier URL and the page never loads. MDN’s guide to HTTP redirections warns that loops break the user experience, and browsers stop with an error page.

Next, filter the export for 302 and 307 codes. Both codes tell Google the old URL may come back, so Google can keep showing it in search results. Switch each one to a 301, which Google’s redirect best practices recommend for permanent moves.

Check Each Old URL Lands on Its Closest Matching Page

Many old URLs land on the homepage because bulk rules send whole folders there. Google often treats these irrelevant redirects as soft 404s, which means the old page’s rankings disappear.

To check, compare each final URL with the old page title from your pre-migration crawl. The redirect export only shows URLs, so you’ll need that earlier crawl or an archived copy from the Wayback Machine. A product page should land on the same product, and a blog post should land on its updated version.

If no close match exists, point the old URL at the nearest category or topic page. When nothing relevant remains, a 410 (gone) status tells Google you removed the page on purpose.

Check Internal Links, Canonicals and Content for Old URLs

Your own site can keep sending visitors to old addresses too. Menus, footers and older blog content often still link to legacy paths, so each click sets off a redirect.

To find these internal links, crawl the new site and open Response Codes > Internal > Redirection (3xx) to see the affected URLs. The Inlinks tab shows every page linking to each redirected URL, so you can edit the source directly. When we run these crawls for clients, the footer is where stale links hide most often.

Canonical tags tell Google the main version of a page, so they need the same check. Point each canonical at its final URL so Google never follows a tag back to a retired address. Structured data needs a scan too, since breadcrumb and organisation markup often hard-codes full URLs

A Post-Migration SEO Audit Only Ends When Legacy Traffic Stops Arriving

Fixing redirect chains covers the internal half of the job. Backlinks and old sitemap entries still point at retired URLs until you update them. Add the three tasks below to your SEO migration checklist and work through them in the weeks after the redirect fixes go live:

  • Outreach for Top Backlinks: Your strongest backlinks still pass through a redirect, so they depend on that rule staying live. Email each site owner and ask them to swap in the new URL. Start with linking pages that already send referral visits, since those links bring traffic as well as authority.
  • Clean XML Sitemaps: Only new, indexable URLs belong in the XML sitemaps you submit to Search Console. Old entries ask Google to keep crawling retired pages, which wastes crawl time. Remove them, resubmit the sitemap and check the Sitemaps report for errors a few days later.
  • Monthly Legacy Traffic Checks: Rerun your old-path filter in Search Console once a month and log the clicks. A gradual traffic drop on old paths shows Google is moving rankings to the new pages. If an old URL holds its clicks for three months, retest its redirect and internal links.

Leave every redirect live while legacy clicks arrive, and for at least one year after launch, as Google’s site move guidance recommends. Removing a rule early creates broken links on sites you can’t control. Log each fix in your spreadsheet so the next monthly check starts from a clear baseline.

A home office desk where a person works at a laptop

Make the New Site Earn Its Own Traffic

Your post-migration SEO action plan can start this week with three steps. First, filter this month’s Search Console data for old paths and export the busiest URLs. Next, crawl that export in Screaming Frog and fix loops and long chains before anything else. Then book a monthly check so you can watch legacy clicks fall as the new pages take over.

Want a second pair of eyes on your migration? Talk to Motifo about a post-migration SEO audit that traces each old URL to its final page.