Rankings dropped after a website migration: how to diagnose it and fix it, step by step
Short answer: A drop in rankings after a website migration (moving your site to a new platform, host or design) usually comes from a short list of causes: search engines blocked by a leftover setting, old addresses that do not forward to the right new pages, or content and addresses that changed. Check those in order, and fix the cheapest causes first. Some fluctuation is normal: Google says a small to medium-sized site can take a few weeks for most pages to move, and nobody can promise a recovery date.
Your search traffic dropped after you launched a new site, and you want an ordered list of what to check and what to fix first.
I'm Ranjit, and I run Blur Studio: 15+ years building software, 120 apps taken live, and clients who have gone on to raise $10M+. I build AI systems and processes that help businesses do a lot more with a lot less time. I also work differently from most of what else is out there, more on that further down this page. Say hello.
Work through this in order: first confirm the drop is real and tied to the move, then check whether Google is allowed to read the new site, then check that every old address forwards to the right new page, then look at content and speed. Most small-business sites (50 pages, not 50,000) can finish steps 1 to 5 in an afternoon with free tools. This page gives the steps, the commands to test them, a way to decide whether to roll back, and what to expect afterwards.
One note on tools: if you moved to Ploy, an AI platform that builds and hosts websites from a chat, I mention the places where its docs apply, such as its redirect rules and sitemap behaviour. I earn a commission if you sign up through that link. Every step below works on any platform.
This page may contain affiliate links from which Blur Studio earns commissions.
What to expect, and what no one can promise
Google's site move guide says to expect temporary ranking fluctuation. For a small to medium-sized site it says it can take a few weeks for most pages to move to their new addresses in Google, and longer for large sites. It gives no recovery date and neither can I.
Published studies measure a harder case: moves to a different domain name. SALT.agency, an SEO agency, analysed 1,052 moves from one domain name to another (published 26 June 2026), drawn from its own projects and from migrations crowdsourced from the SEO community. It reports a median of 304 days and a mean of 489 days for monthly traffic on the new domain to match the old domain's pre-move level, with about 30 days of precision because the data is monthly. About 42% took more than 12 months by its text (its table implies about 40%), and about 14% had not fully recovered after three years. It only counted moves where traffic fell 60% or more, so it measures bad moves, it inferred move dates from traffic history, and it did not model the quality of the work. I know of no comparable dataset for a same-domain platform change with the same addresses and content, so do not read those numbers as a forecast for yours. Treat them as a reminder that a sloppy move can cost months.
Two other facts to keep in mind. Google advises making changes one after another, not everything at the same time, for example moving domains first and changing the layout later. And only the Manual actions report in Google Search Console (Google's free tool for site owners) shows a penalty. A drop after a move is not a penalty.
Step 1: confirm it is the migration
- Open Search Console, then Performance, then Search results. Set the date range to the 28 days after launch and compare it with the 28 days before. Keep the same days of the week.
- Switch to the Pages tab and sort by clicks. Note your top 10 pages before and after.
- Check for a Google update in the same dates on Google's Search Status Dashboard. If the drop begins the day of launch, suspect the move. If it begins a week later, suspect an update or a slow problem.
- Compare against a control: look at search terms that bring in clicks to pages that did not change, such as your brand name. If brand clicks are stable and non-brand clicks fell, the pages are the issue.
- Write down the numbers. You need them to prove a fix worked.
Step 2: make sure Google is allowed in
This is the most common cause of a sudden, large drop, and the easiest to fix. A staging site is often set to block search engines, and the setting can survive launch.
- Open
yourdomain.com/robots.txt. Look forDisallow: /underUser-agent: *. If it is there, remove it. Google says robots.txt manages crawl traffic and a blocked page can still be listed, so check noindex separately. - In Search Console, paste your top 5 addresses into URL Inspection, then press Test live URL. It shows whether crawling and indexing are allowed and which canonical Google chose.
- View source on a top page and search for
noindex. Remove any migration-only noindex tag. - If the platform has a "discourage search engines" or "hide from search" toggle, check it is off.
On Ploy, Ploy's migration guide says to confirm the production robots.txt has no Disallow: / and that its Sitemap line points to your own domain.
Step 3: check every old address forwards to the right new page
A redirect is an automatic forward from an old address to a new one. A permanent redirect (301 or 308) tells Google the page has moved. Google's guide says to redirect each old address to its matching new address, to avoid forwarding many pages to one unrelated page such as the home page, and to avoid chains.
- Build the list of old addresses. Use the old sitemap, Search Console's Performance Pages list, your analytics landing pages, and a crawl if you can. Include blog posts, images and PDFs that earned traffic.
- Test the top ones. In a terminal:
You wantcurl -sIL -o /dev/null -w "%{http_code} %{num_redirects} %{url_effective}\n" https://yourdomain.com/old-page200 1and the correct final address, or200 0if the address did not change. A404means a missing redirect. A count of 2 or more means a chain. - Look for chains and loops. Google says Googlebot can follow up to 10 hops, but advises sending each old address straight to its final destination. If you cannot, keep chains to no more than 3 and fewer than 5.
- Look for redirects that go to the home page or a category page instead of the matching page. Fix each one.
- Check that redirects are permanent, not 302 (temporary).
- Check that the old homepage, www and non-www, and http and https versions all land on one final address.
Platform limits matter. Ploy's guide says to contact support before migration day if you need more than 20 redirect rules, and that one pattern, such as /blog/post-name to /articles/post-name, can share a rule. For other platforms, check the redirect limits in their help pages.
Also check trailing slashes. Ploy's guide says published prerendered pages drop the trailing slash by default, so /about/ redirects to /about, and you can keep the slash with a setting in the site's config file. Whatever platform you use, make sure the canonical address and the sitemap use the same form.
Step 4: canonicals, sitemap and internal links
- Canonical tags. Each page should name its own new address as the preferred one. A canonical pointing to the old address tells Google to keep the old page.
- Sitemap. Submit a new sitemap that lists only new addresses and returns 200 for each. Remove the old one. Google says warnings on an old-address sitemap about redirects can be ignored. Ploy generates a new sitemap-index.xml, and its guide says the old sitemap does not carry over.
- Internal links. Crawl the new site with a free crawler or Search Console's Links report and fix links that still point to old addresses or 404s. Check the footer, menu and blog posts.
- Orphan pages. Pages that exist but have no links to them can fall out of the index. Link each from a relevant page.
- Back-links. Update your own profiles, partner pages, directories and ad campaign addresses to the new ones.
Step 5: lost or changed content
A rebuild often rewrites titles, headings and copy. If a page ranked for a phrase and the new version no longer mentions it, the redirect will not save it. Compare each top page before and after:
- Title tag and meta description: same topic and main phrase?
- Headings and body: did a long, useful page become a short one?
- Schema markup (structured data), images with alt text, FAQs and tables: still there?
- Pages merged or deleted: did a ranking page disappear with no 301 to a close match? Google says to return 404 or 410 for content that is truly gone.
If you used an AI builder that regenerated page addresses (slugs), that is a common hidden cause: the same page now sits at a new address with no redirect. Compare the old sitemap with the new one and redirect each changed address. If the move rebuilt pages with AI, remember that Ploy's own docs call a migration a rebuild, not an identical copy, so review every top page by hand. See Ploy site migration for what its docs say may need separate work: forms, plugins, custom code and embeds.
If rewriting cut text, restore the old wording on your top pages first. That is usually a faster fix than waiting.
Step 6: speed, mobile and tracking
- Run a speed test on your top pages. Google's Core Web Vitals targets, measured at the 75th percentile, are LCP (loading) under 2.5 seconds, INP (response to taps) under 200 milliseconds and CLS (layout shift) under 0.1. If the new site is slower, see page speed problems on marketing sites.
- Open the site on a phone. Google indexes the mobile version, so hidden text or missing menus on mobile can cost rankings.
- Check that forms still send. Many forms do not survive a platform change. Use the form fix checklist.
- Check your analytics and ad tags fire. A tracking gap can look like a traffic drop when clicks are really fine. Compare Search Console clicks with analytics visits.
- If you changed domain name or host, review the domain steps in custom domain, DNS and SSL setup.
Diagnosis table
| What you see | Likely cause | First fix |
|---|---|---|
| Everything drops on launch day, impressions near zero | Robots block or noindex left on | Step 2 |
| Top pages gone, others fine | Missing or wrong redirects | Step 3 |
| Old addresses still showing in Google after several weeks | Redirects missing, or canonicals point to old | Steps 3 and 4 |
| Pages indexed but ranking lower | Content, titles or speed changed | Steps 5 and 6 |
| Clicks fine, analytics down | Tracking tag not firing | Step 6 |
| Drop starts a week or more after launch | Possibly a Google update or slow-burn issue | Step 1, then 5 |
Roll back or fix forward? A decision rule
This rule is my judgment, not Google's guidance. Roll back if all three are true: the old site is still available, you cannot find a fixable cause within a few days, and the drop affects pages that earn most of your leads. Keep the old host live and keep your DNS changes reversible so this stays possible. If you changed domain name and used Google's Change of Address tool, you can cancel within 180 days, but only by removing the old redirects, adding redirects from new to old and pressing Cancel Move. Do not chain site moves.
Fix forward in every other case. Most causes above are fixes, not reasons to undo the move.
How long to keep redirects, and a conflict to know about
Google's site move guide says to keep the redirects for as long as possible, generally at least 1 year. Its Change of Address page says at least 180 days, longer if you still see traffic to the old addresses, and to keep the old domain for at least a year. These are two Google pages with two numbers. Use the longer one: at least a year.
How to monitor for the next eight weeks
- Weekly: compare Search Console clicks and impressions for your top 10 pages against the week before launch.
- Weekly: check Page indexing for new errors and the Sitemaps report for the new sitemap.
- After each fix: use URL Inspection on the page and press Request indexing if the live test passes. There are daily limits, so start with your top pages.
- Keep a change log with dates, so you can tell which fix helped.
Fixing the cause does not bring traffic back the next day. Google needs to recrawl the pages. Watch for the trend over weeks.
When to call for help
- You find robots, noindex or redirect problems you cannot edit on your platform.
- Your site has hundreds of changed addresses and no spreadsheet of old to new.
- Your drop is more than half of clicks and a week of fixes has not moved the trend.
- A Manual actions report shows a penalty.
Hire an SEO consultant for the diagnosis, not for a promise of rankings. Be careful of anyone who guarantees a date. If the move was to a new platform and the host or builder supports it, send support the list of old addresses and ask them to confirm the redirects.
How I'd approach this
I would treat this as a checklist, not a mystery. Most small-site drops come from steps 2 to 4, so I would not touch the content until the blocks and redirects are verified. Take your top 20 old addresses, test each with the command above, and record the result in a sheet with three columns: old address, final address, status. That one sheet usually shows the problem.
If you are still choosing a platform, ask what it allows before you commit: how many redirect rules, whether you can edit robots.txt, whether you can keep your addresses and export your content. Ploy documents redirect rules, a Preview check and a sitemap, which helps on a rebuild, but it still rebuilds your pages, so review them. I would never launch on a Friday, and I would keep the old site running until the new one passes every step. If a custom connection or process sits behind your site, such as a form feeding your CRM, Blur Studio builds those; see what that includes. For planning a move before it happens, read keeping SEO rankings when you rebuild.
First-week plan:
- Day 1: Step 1. Write down before and after clicks for your top 10 pages.
- Day 2: Step 2. Check robots.txt, noindex and URL Inspection on the top 5 pages.
- Day 3: Step 3. Test the redirects for the top 20 old addresses and fix the wrong ones.
- Day 4: Steps 4 and 5. Fix canonicals, sitemap and internal links, then compare top-page content.
- Day 5: Step 6. Check speed, mobile, forms and tracking. Submit the sitemap and request indexing for the top pages. Set a weekly review.
Questions people ask
How long does it take for rankings to recover after a website migration?
Nobody can promise a date. Google says a small to medium-sized site can take a few weeks for most pages to move, and longer for large ones. Studies of domain-name moves show a much wider spread, with a median of 304 days in one 1,052-move study, and no same-domain dataset exists.
Why did my traffic drop after a redesign?
Common causes are a leftover noindex or robots block, old addresses with missing or wrong redirects, canonicals pointing to old addresses, changed titles and content, and a slower site. Use the diagnosis table above to match what you see to a step.
Do 301 redirects fix the drop?
Correct permanent redirects are required, but they only help if each old address goes to a close match, without chains. Google says not to send many pages to one unrelated page. If the new page does not cover the topic, the redirect will not rescue the ranking.
How can I check if my redirects work?
Use a command such as curl with the -sIL flags on each old address and read the final status and the number of redirects, or use URL Inspection in Google Search Console. You want a single permanent redirect that ends on the right page with status 200.
Should I use Google's Change of Address tool?
Only if the domain name or subdomain changed. Google says it does not apply to http to https, www to non-www or path changes. Both old and new domains must be verified in the same Search Console account.
Should I roll back my migration?
Only if the old site is still live, you cannot find a fixable cause within a few days and the drop hits the pages that earn most of your leads. That rule is my judgment, not Google's. Most causes can be fixed forward.
Did Ploy or another AI builder cause my drop?
The platform itself is rarely the cause. Rebuilds can change addresses, titles and content, and those are the usual culprits. Ploy documents redirect rules and a sitemap, but it calls a migration a rebuild, so review each top page. See Ploy site not showing on Google.
How long should I keep my redirects?
At least a year. Google's site move guide says generally at least 1 year, while its Change of Address page says at least 180 days and longer if traffic still arrives at old addresses. Use the longer figure.
More in this topic: Websites: fixing migration, DNS, forms, speed and CRM problems (6 guides) →
Sources
- Google Search Central: Site move with URL changes
- Google Search Central: Site move without URL changes
- Google Search Console Help: Change of Address tool
- Google Search Console Help: URL Inspection tool
- Google Search Central: Introduction to robots.txt
- Ploy docs: Migration readiness
- SALT.agency: How long a domain migration takes to recover