Does changing web host affect SEO?

Short answer: moving hosts does not hurt SEO. Moving hosts badly does, and the damage comes from a small, predictable set of mistakes.

Google does not have a "changed hosting provider" penalty. What it has is a crawler that notices when URLs start returning different things.

What actually causes ranking drops after a migration

Staging settings shipped to production

The single most common cause. A staging site is usually blocked from indexing, either with Disallow: / in robots.txt or a site-wide noindex. Migrate the files without changing that setting and you have politely asked Google to remove your entire site.

Check both immediately after going live:

• yourdomain.com/robots.txt — should not contain Disallow: /
• WordPress: Settings → Reading → "Discourage search engines" must be unticked

URLs changed during the move

If /about-us/ becomes /about/, every link and every bit of accumulated authority pointing at the old URL now hits a 404 unless you redirect it.

Keep URLs identical if you possibly can. If you cannot, map every old URL to its closest equivalent with a 301 before launch.

Redirects lost with the old server config

Redirects often live in .htaccess or nginx config rather than the database. Copy the files and database, forget the server config, and years of accumulated redirects vanish silently.

Export your existing redirect rules before you migrate. Test a sample after.

Downtime during the DNS switch

A few minutes is irrelevant. Hours of the site returning 5xx errors while Googlebot is crawling is not ideal, though it is usually recoverable.

Avoid it by keeping the old host running until DNS has fully propagated, rather than cancelling it the moment the new one is live.

The new host is slower

This one is real but indirect. Page speed is a ranking factor and a large factor in user behaviour. Migrating from a good host to a cheap one can cost you, especially if the new server is on another continent from your audience.

Measure before and after with the speed test — specifically TTFB.

A migration checklist that avoids all of the above

Before

1. Full backup of files and database, downloaded and verified
2. Export the current redirect rules
3. Record current TTFB and a handful of key rankings so you can compare afterwards
4. Crawl the site and save the URL list
5. Lower your DNS TTL to 300 seconds a day ahead, so the switch propagates quickly

During

6. Copy files and database to the new host
7. Test on the new server using a hosts-file override or temporary URL, before touching DNS
8. Confirm robots.txt and indexing settings are production settings
9. Re-apply redirect rules
10. Check SSL is valid on the new host — use the SSL checker

After

11. Switch DNS, keep the old host live for at least 48 hours
12. Crawl the site again and compare against the saved URL list — look for new 404s
13. Check Search Console for crawl errors and a coverage drop
14. Re-test speed; if TTFB got worse, you have a problem worth solving now
15. Restore your DNS TTL to something sensible

What does not matter

• Changing IP address. Normal and expected.
• Changing nameservers. Provided DNS records resolve correctly.
• The host's brand. Google does not know or care who you pay.
• Shared vs dedicated IP. Not a ranking factor in any meaningful sense.

The realistic risk profile

A careful migration of a small site is close to zero risk. The failure cases are all human error, and all of them are catchable with a crawl before and after.

If you would rather not do it yourself, moving a site cleanly is one of the things we help with — see website help. And if you are migrating because your current host is slow, confirm that first with the health check; it is worth knowing whether you are moving for the right reason.