Short answer
Changing hosting does not directly affect SEO. Google does not lower rankings just because a website moves to another hosting provider, server, or CDN.
However, rankings can drop after a hosting migration if the move creates technical problems: downtime, slower server response, SSL errors, broken redirects, changed canonicals, blocked crawling, missing pages, or accidental content changes. The safest approach is to separate the infrastructure move from other website changes and monitor the site closely after launch.
Update note, June 2026: this article was originally based on a 2018 Google discussion, but the practical conclusion is still relevant. Hosting itself is not the ranking signal to worry about; accessibility, speed, crawlability, and migration quality are.
What happened
In December 2018, a user asked John Mueller from Google whether changing hosting affects search positions.
The question was triggered by a case where a webmaster moved a website to Cloudflare and then saw ranking drops. The conclusion in that case was direct: hosting migration caused the drop.
What Mueller said
Mueller disagreed with that conclusion:
Changing website hosting can lead to temporary slower crawling by Googlebot, but it does not affect rankings.
In other words, Google may intentionally reduce crawl frequency right after server migration to make sure the new environment can handle load. Then crawl speed returns to normal automatically.
This crawl slowdown should not be treated as a ranking penalty. It is Googlebot adapting to a changed server environment. If URLs actually fell out of the index after the move, work through the Search Console statuses instead — I covered them in a separate breakdown of why Google is not indexing your pages.
Why rankings may drop in reality
If rankings decline after migration, hosting itself is usually not the reason. Check the following:
| Likely reason | What to check |
|---|---|
| Temporary downtime | Uptime during DNS switch, maintenance windows, 5xx errors |
| DNS or SSL issues | HTTPS availability, certificate chain, mixed content, redirect logic |
| Redirect or canonical mistakes | 301 rules, canonical URLs, trailing slash behavior, HTTP to HTTPS redirects |
| Robots or noindex mistakes | robots.txt, meta robots, X-Robots-Tag headers, staging rules copied to production |
| Sitemap and indexing gaps | XML sitemap URLs, lastmod values, Search Console sitemap status |
| Slower server response | TTFB, PageSpeed Insights, server logs, CDN cache configuration |
| Core Web Vitals regression | LCP, INP, CLS, render-blocking assets, image delivery |
| Migration errors | 404s, broken internal links, missing assets, changed URL paths |
| Code or content changes | Before/after comparison, templates, headings, internal links, structured data |
Ranking drops often happen at the same time as hosting migration, but are caused by other changes done during the same period.
What to do before changing hosting
To avoid traffic loss, follow these steps:
- Make a full backup of files, database, media, and server configuration.
- Test the new environment on staging before switching DNS — and if the site came to you together with the domain, use the same window to check whether someone else's comments and submissions are still sitting there, because after launch you answer for them as the data controller (breakdown from my own case — the Data Protection Inspectorate precept).
- Lower DNS TTL before migration so rollback is faster if something breaks.
- Verify SSL certificates, HTTP to HTTPS redirects, and canonical URLs.
- Keep URL paths, page content, metadata, schema, and internal links unchanged during the move.
- Check robots.txt and noindex rules so the production site stays crawlable.
- Generate and validate the XML sitemap before launch.
- Avoid other major design, CMS, content, or URL changes during the hosting move.
What to monitor after migration
For the first 2-4 weeks, monitor the site like a technical SEO migration:
- Google Search Console indexing status and coverage issues.
- Crawl stats and unusual Googlebot drops or spikes.
- Server logs for 404, 403, 500, 502, 503, and timeout patterns.
- XML sitemap submission and discovered URLs.
- Redirect chains, canonical consistency, and unexpected soft 404s.
- PageSpeed Insights and Core Web Vitals for key landing pages — read the field data rather than the score, since whether site speed affects rankings depends on CrUX, not Lighthouse.
- Organic impressions, clicks, and average positions for important queries.
Short-term movement in the first days is normal. A persistent drop usually means there is a technical issue to diagnose.
If rankings dropped after migration and the cause is unclear, request an SEO audit before making more changes. A focused audit can separate crawl/indexing problems from speed, content, redirect, and tracking issues. If traffic has to come back faster than organic recovery allows, decide separately whether to start with Google Ads or SEO.
Google's conclusion
The official position remains the same: hosting is not a direct ranking factor as long as the website is technically accessible and fast enough. Moving to another provider, server, or CDN is an infrastructure decision, not a quality signal.
