Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Google can keep showing old-domain URLs for months after a move while it discovers and processes the new URLs. Four months alone does not prove that a migration is healthy or broken: Google says most pages on a small-to-medium-sized site may move in a few weeks, while larger sites can take longer, depending partly on URL volume and server speed. Check redirects, new-page indexing signals, and both Search Console properties to find out whether your migration is progressing.
Why old-domain results can persist
A domain migration is processed URL by URL, not as one instant switch in Google’s results. Google says the time required to discover and process moved URLs depends on how many URLs are involved and how quickly the servers respond. Its general guidance is that most pages on a small-to-medium-sized site may move in a few weeks; larger sites can take longer. That is an estimate, not a guarantee or a four-month failure threshold. Google’s site-move guidance does not set a universal cutoff at which old results mean a migration has failed.
Whether your particular move is on track depends on details such as the old-to-new URL mapping, redirect responses, crawl access, canonical tags, and Search Console data. A hosting change alone is also different from a change to the domain or URL structure.
Diagnose the migration in this order
1. Identify what changed
Determine whether you moved to another domain or subdomain, changed HTTP to HTTPS, changed the www/non-www version, changed URL paths, or only changed hosting. Google’s Change of Address tool is for a move between domains or subdomains. It is not required for HTTP-to-HTTPS, www/non-www, or path changes on the same domain. Google’s URL-change migration instructions distinguish these cases.
#1 Best Overall
2. Test old URLs and their destinations
Choose important pages across the old site—not just the homepage—and check that each old URL redirects permanently to its relevant new equivalent. The final destination should load as a usable page. A permanent server-side redirect is the appropriate signal when a URL has changed; temporary redirects do not provide the same canonicalization signal. Google’s redirect guidance explains the distinction.
Avoid sending many unrelated old URLs to one destination, such as the new homepage. Google warns that such redirects can confuse users or be treated as soft 404s. For a large migration, crawl the old URL set and review the destination and response for each URL; this helps reveal missing mappings, redirect chains, loops, and errors.
3. Inspect representative new pages
In Search Console, use URL Inspection on a sample of important new URLs. Check that each page is accessible to Google, is not blocked by a migration-only robots.txt rule or noindex directive, and has a canonical annotation pointing to the intended new URL. A redirect that reaches a missing or irrelevant destination, or a new page that cannot be crawled, can prevent the move from progressing as expected. Google lists these among the migration checks in its site-move documentation.
4. Compare old and new Search Console properties
Verify both the old and new properties, then compare their sitemap status, indexed URL trends, search queries, and crawl errors over time. During a move, Google says indexed counts for the old sitemap should fall as counts for the new sitemap rise. Redirect warnings on the old sitemap can be normal during this transition; they are not, by themselves, proof that the redirects are wrong. See Google’s site-move guidance.
Submit a sitemap containing the new URLs. Also review server access and error logs for Googlebot visits and unexpected HTTP errors. Search Console’s crawl-error troubleshooting guidance can help interpret access and response problems: Troubleshoot Google Search crawling errors.
5. Confirm the move was administered correctly
For a domain or subdomain move, check that Change of Address was submitted from the old property and that applicable verified variants were covered. Keep redirects in place for as long as possible; Google recommends generally keeping them for at least one year to allow recrawling and signal transfer. These steps do not replace correct redirects or accessible new pages.
What the evidence means
- New indexed URLs are rising while old ones decline: that is consistent with the expected transition, even if some old results remain visible.
- Old sitemap entries show redirect warnings: Google says this can be normal during a move; check actual redirect destinations rather than treating the warning alone as a failure.
- New URLs are blocked, carry noindex, or canonicalize to the old domain: fix those signals so Google can crawl and recognize the intended destination URLs.
- Old URLs fail, redirect to unrelated pages, or produce server errors: correct the URL mapping and response behavior, then monitor crawl and indexing trends again.
- Neither property shows a clear transition: inspect representative URLs, sitemap processing, crawl errors, and server logs. The cause cannot be identified from the age of the move alone.
What to gather before asking for a site-specific diagnosis
To narrow down why old-domain results remain, collect the move date and type, examples of old URLs and their intended new URLs, the HTTP responses and final destinations for those examples, Search Console status for both properties, and any robots.txt, noindex, or canonical directives on the new pages. Without those details, four months is not enough to identify a specific fault.
Free tools Windows power users keep installed
One-click scans. No signup required.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
