If your WordPress migration is finished but some visitors still see the old site, stale DNS records and cached copies are the usual causes. DNS, the Domain Name System that maps your domain name to a server address, plus browser, plugin, and network caches can keep sending or showing old pages for a while. The fix is a checklist, not a guess. Confirm the domain points to the new server everywhere, then clear each cache layer in order until every visitor lands on the new site.
Table of Contents
- Why do only some visitors see the old site?
- Is your DNS pointing to the new host?
- Which caches can still show the old pages?
- Is WordPress itself sending visitors to the old address?
- How do you confirm the move is complete?
- Frequently Asked Questions
Why do only some visitors see the old site?
Different visitors use different lookup paths. One internet provider may pick up your new address quickly, while another keeps the old address until its stored record expires.
A visitor who opened the site recently may also load it from a local copy. This split view is normal right after a move. It does not by itself mean files are missing or the migration failed.
Is your DNS pointing to the new host?
Start with the domain settings at your registrar or DNS host. Check that the main A record, which points the domain to a server address, and the www record use the new hosting address.
Remove or update any old address left active. Then check timing. DNS changes spread gradually, and the TTL value, the time a record is allowed to be reused before checking again, controls how long old answers linger.
- Lower TTL to a short value before future moves, then raise it after traffic stabilizes
- Look up your domain from several locations using independent DNS check tools
- Ask affected visitors for their city or provider to spot a regional lag
- Keep the old hosting plan active until checks show the new address everywhere
Which caches can still show the old pages?
Caching means saving a copy to serve faster next time. After migration, several layers may still hold old copies even when DNS is correct. Clear them from visitor to server.
Start closest to the visitor, then move outward. Ask the affected person to hard-refresh and clear that page from the browser cache. Then purge the WordPress caching plugin, the theme or host cache, any CDN cache such as a proxy that stores copies worldwide, and the local resolver cache on office networks.
- Purge WordPress cache plugin and server or object cache on the new host
- Purge CDN cache for the domain and key pages
- Clear router, office, or school network cache if reports cluster in one place
- Test in a private window to separate a browser copy from a server problem
Is WordPress itself sending visitors to the old address?
WordPress stores the site address in its settings and inside page content. If those still point to the old host, staging name, or temporary address, some links, images, and redirects will pull visitors back. Update the Site Address and Home settings to the final domain.
Search the database for leftover staging URLs and replace them carefully with the live domain. Check redirects, canonical tags used to name the preferred page address, and HTTPS rules. A redirect left pointing to the old server can recreate the old-site effect after DNS looks correct.
How do you confirm the move is complete?
Test like an outside visitor. Load the homepage, a post, a search page, and a form or checkout on a fresh network, such as mobile data with Wi-Fi off.
Submit a test comment or order and confirm it appears only in the new dashboard. Leave both hosts observable for a few days. Watch new-site logs for rising traffic and old-host logs for fading traffic, then close the old plan only when the old log stays quiet.
Frequently Asked Questions
How long should I expect mixed old and new views?
Most cases clear as stored DNS records expire and caches are purged, often within hours to a day, with some networks taking longer.
Should I cancel old hosting right after migration?
No. Keep it online until DNS checks and traffic logs show visitors have stopped using it, so no one hits a dead page.
