A slow host, a rising bill, or a support team that never answers is a good reason to move, but a careless move can wipe out years of search rankings in a weekend. The question of how to move a website to a new host without losing seo comes down to order, and this guide gives the order that keeps every page, link, and ranking intact.
The risk is not the new host. It is the gaps between the steps, like a page that loads on the old host but not the new one, a redirect that points nowhere, or a DNS change made before the new site is ready. Each gap is small on its own and costly together.
This guide walks through eight steps, from auditing the current site to monitoring the new one after the switch. Read the table first, then work the steps in order, and do not skip the testing step. The pick at the end names the single step that matters most.
Quick jump
- How to Move a Website to a New Host Without Losing SEO, Step by Step
- What a Website Move Costs in Time and Effort
- The 8 Steps to Move a Website Without Losing SEO, One by One
- Best Pick by Job
- How to Choose the Right Moment for a Website Move
- Mistakes That Cost Rankings During a Host Move
- Your First Week After Moving a Website to a New Host
- How to Keep a Website Move Cheap and Safe
- How We Verified Every Step of This Website Move
- Frequently Asked Questions
- Habits That Keep a Moved Website Healthy
- The Website Move Most Owners Should Make First
How to Move a Website to a New Host Without Losing SEO, Step by Step
The table below puts the eight steps on the same footing, with what each one does and what to watch out for. The question of how to move a website to a new host without losing seo is answered by the sequence, not by any single tool, and the steps below must run in the order given.
Two patterns stand out at once. First, most of the work happens before anything moves, in the audit, the backup, and the setup. Second, the dangerous steps are the short ones, like the DNS change, where a single wrong value can take the whole site offline.
| Step | What you do | Watch out for |
|---|---|---|
| Audit the Current Site | List every page, redirect, and ranking keyword before anything moves | A missed page is a page that never arrives on the new host |
| Choose the New Host | Compare speed, support, backups, and renewal price before signing up | A cheap first year can hide a renewal price three times higher |
| Back Up Everything | Copy files, database, and uploads to a place outside both hosts | A backup stored on the old host is lost when the old host is cancelled |
| Set Up the New Hosting Account | Install the same software and settings as the old host | A different PHP version can break a plugin that worked for years |
| Move the Files and Database | Copy every file and import the database, then check the links | A single missed folder can break every image on the site |
| Test on a Staging Address | Open every key page on the temporary address and test forms and checkout | A page that works on staging can still fail after the DNS change |
| Update the DNS Records | Point the domain to the new host and wait for the change to spread | A wrong record can send visitors to the old host for days |
| Monitor and Clean Up | Watch traffic, errors, and rankings for two weeks after the switch | A redirect missed in week one can cost a ranking that takes months to win back |
What a Website Move Costs in Time and Effort
The question of how to move a website to a new host without losing seo is mostly a question of time, and a small site takes four to eight hours spread over a week. A large site with hundreds of pages takes longer, and the audit and testing steps grow with every page that must be checked.
The money cost is usually one month of overlapping hosting, because the old host should stay live until the new one is proven. Cancelling the old host early to save a month is the most common false economy in this guide, and it leaves no way back when something breaks.
A second cost is attention. A move done in a rush on a Friday evening will be finished in a panic, while the same move done on a quiet Tuesday with a checklist is routine. For a site owner, the cheap move is the slow, careful one.
The 8 Steps to Move a Website Without Losing SEO, One by One
The eight steps below are reviewed in the same order as the table, with what each one does, what it asks of the owner, and where it goes wrong when rushed.
1. Audit the Current Site. what it decides
An audit is a full inventory of the site as it stands today. It lists every page, every redirect, every form, and the keywords that bring traffic, so the new site can be checked against a known list instead of a memory. The audit should also note which pages earn links from other sites, because those pages carry the most ranking value. The audit should also record which pages earn the most traffic, so the pages that matter most get tested first on the new host.
The work is mostly copying and pasting. A sitemap, a crawl report, and the search console data give the page list, and a spreadsheet holds it. An owner who skips the audit has no way to know what was lost. A screenshot of the search results for the top ten pages gives a before-and-after record that is easy to compare.
The limit is time on a large site, where a full crawl can take an hour and the list can run to thousands of rows. For a small site, the audit takes an afternoon and saves a week of repair later. The plugin and theme list belongs in the audit too, so the new host gets the same setup. An owner who audits first can prove the new site is complete, because every page on the list can be ticked off against the live copy.
2. Choose the New Host. what it sets
Choosing a host means comparing speed, support, backups, and the renewal price, not just the first-year offer. A host that answers support tickets in minutes is worth more than a host that saves five dollars a month and leaves a broken site waiting. A host that offers a staging area lets the owner test the move without touching the live site. A host that offers a staging area lets the owner test the move without touching the live site, which removes the biggest risk in the whole project.
The work is reading the plan details and testing the support response with a question. A host with daily backups, a free migration tool, and a clear renewal price is the safe choice, even when the headline price is higher. The data centre location matters for speed, and a host near the audience is worth choosing.
The limit is that no host is perfect, and every review mixes genuine complaints with rare edge cases. For a site owner, the host with the best support record beats the host with the lowest price. Check the backup retention period, because a backup kept for one day is little use after a weekend problem. An owner who tests support with a question before signing up will learn more than any review can say, because the reply time is the real service level.
3. Back Up Everything. what it protects
A backup is the only way back when a move goes wrong, and it must cover files, the database, and the uploads folder. A partial backup is almost as bad as no backup, because the missing piece is usually the one that breaks. Test the backup by opening it and checking that the database file and the uploads folder are both inside. The backup should include the uploads folder, the database, and the theme files, since a missing piece is usually the one that breaks the site.
The work is running the backup tool and downloading the copy to a local drive or a separate storage account. A backup that lives only on the old host is not a backup, because it disappears with the account. Keep two copies, one local and one in cloud storage, so a single drive failure cannot take both.
The limit is size on a large site, where a full backup can take an hour to download. For a small site, the backup takes minutes and is the cheapest insurance in this guide. Note the backup date and time, because a restore from the wrong day can undo recent edits. An owner who tests the backup by opening it will know it works, because a backup file that cannot be opened is not a backup at all.
4. Set Up the New Hosting Account. what it prepares
Setting up the new account means installing the same software, the same PHP version, and the same settings as the old host. A site that worked on one version can break on another, and the setup step is where that break is found safely. Enable the free security certificate on the new host before the move, so the site stays secure from day one. The new account should have its security certificate enabled before the move, so the site stays secure from the first day on the new host.
The work is creating the account, adding the domain as a parked or addon domain, and installing the content management system. The new host migration tool can help, but a manual check of the settings is still needed. Set the PHP version to match the old host, then update it later once the move is proven.
The limit is that every host panel looks different, and the setting names vary. For a site owner, an hour spent matching settings now saves a day of debugging after the switch. Create the email accounts on the new host before the DNS change, so mail keeps flowing. An owner who matches the PHP version first avoids the most common break, because a plugin that worked for years can fail on a newer version.
5. Move the Files and Database. what it transfers
Moving the site means copying every file and importing the database, then checking that the links inside the content still point to the right place. A migration plugin can do the heavy lifting, but the owner must still verify the result. Search the database for the old temporary address after the import, because a missed replacement breaks internal links. The database should be searched for the old temporary address after the import, because a missed replacement breaks internal links silently.
The work is running the migration, waiting for the transfer, and then opening the new copy through its temporary address. A file count check against the old host catches a transfer that stopped halfway. Check the uploads folder size on both hosts, since a mismatch means files are missing.
The limit is that large media libraries take time, and a slow connection can stretch the move over hours. For a small site, the transfer takes under an hour and the check takes longer than the copy. Keep the old site untouched during the move, so it stays live while the new copy is tested. An owner who checks the file count after the transfer will catch a copy that stopped halfway, because a missing folder breaks every image on the site.
6. Test on a Staging Address. what it proves
Testing means opening every key page on the temporary address and clicking through the forms, the search, and the checkout. A page that looks right can still hide a broken form, and the staging step is where that break is found without visitors seeing it. Test the contact form by sending a real message and confirming it arrives. The staging test should include a phone check, since mobile problems hide on a desktop screen and most visitors arrive on a phone.
The work is methodical, going down the audit list page by page and noting anything that differs from the live site. A broken image, a missing style, or a slow page all get fixed here, before the switch. Check the site on a phone as well as a computer, because mobile problems hide on a desktop screen.
The limit is that staging cannot test everything, because some features need the real domain to work. For most sites, staging catches nine in ten problems, and the last few are found in the monitoring step. Run a speed test on the staging copy and compare it with the old host, since speed is part of the reason to move. An owner who tests the contact form by sending a real message will confirm the site works, because a form that looks right can still fail to deliver.
7. Update the DNS Records. what it switches
Updating DNS is the moment the move goes live, and it means pointing the domain records at the new host. The change itself takes minutes, but the spread across the internet takes hours, so visitors arrive at the new host gradually. Do the DNS change at a quiet time, like a weekday morning, when traffic is low and support is awake. The DNS change should happen at a quiet time, like a weekday morning, when traffic is low and the support team is awake to help.
The work is copying the new nameserver or address records from the new host into the domain registrar, then waiting. Lowering the time-to-live value a day before the change makes the switch spread faster. Keep the old host live for at least a week after the change, in case some visitors still reach it.
The limit is patience, because a DNS change cannot be hurried and a mistake takes as long to undo. For a site owner, the DNS step is the shortest job and the one that needs the most care. Check the site from a different network after the change, because a local cache can hide the new version. An owner who lowers the time-to-live value a day early will see the switch spread faster, because a low value tells servers to check again sooner.
8. Monitor and Clean Up. what it confirms
Monitoring means watching traffic, error logs, and rankings for two weeks after the switch. A page that returns an error, a redirect that loops, or a ranking that drops all show up in this window, and each one has a fix. Cancel the old host only after two clean weeks, and keep a final backup of the old site first. The old host should stay live for two clean weeks, because some visitors and search engines still reach the old address for days after the switch.
The work is checking the search console daily, watching the crawl errors, and comparing traffic with the week before the move. A small dip in the first days is normal, while a sharp drop means something is wrong. Update any hardcoded links in email signatures and social profiles to the new host where needed.
The limit is that rankings move slowly, and a full recovery can take weeks. For a site owner, the monitoring step is the proof that the move worked, and the cleanup can only start once the numbers are steady. Write down what the move cost in time and what broke, so the next move is faster. An owner who watches the search console daily will catch a crawl error in week one, when the fix costs minutes instead of months of lost ranking.
Best Pick by Job
The table below matches the pick to the job, so a reader can find their own situation and see the step or tool that fits it. The reasons are short, because the full steps above carry the detail.
| Job / Need | Pick | Why |
|---|---|---|
| Small blog with fifty pages | Audit, then a migration plugin | A small site moves in an afternoon with a plugin |
| Online shop with orders daily | Staging test, then a quiet-hour DNS change | Orders cannot pause, so testing matters most |
| Site with years of rankings | Full audit and redirect map | Rankings live on old URLs that must redirect |
| Owner with no technical help | A host with free migration | The host team does the transfer and the owner tests |
| Large site with thousands of pages | Crawl audit and staged rollout | Volume needs a checklist, not memory |
| Move done in a hurry | Backup first, DNS last | A backup is the only way back from a rushed move |
How to Choose the Right Moment for a Website Move
The question of how to move a website to a new host without losing seo starts with timing, not with the host. A quiet week with low traffic is the right moment, while a sale, a launch, or a seasonal peak is the wrong one. Pick the week first, then the host, because a move during a traffic spike multiplies every mistake.
Move when the site is stable. A site in the middle of a redesign or a content push has too many moving parts. Finish the other work first, then move, so a problem after the switch has only one possible cause.
Keep the old host paid for a month. The overlap costs one month of hosting and buys a way back. An owner who cancels early to save a month has no fallback when the new host fails.
Tell the team before the move. A writer, a shop manager, or a support agent who edits the old site during the move will lose their work. Freeze edits for the move day and tell everyone when the freeze lifts.
A final check is to read the new host migration guide before starting. The host that documents its own process well is usually the host that supports it well, and the guide will name the settings that matter for that platform.
Mistakes That Cost Rankings During a Host Move
The question of how to move a website to a new host without losing seo is most often failed by a missing redirect map. An owner who moves pages to new addresses without redirecting the old ones hands search engines a pile of dead ends. Map every old address to a new one before the DNS change, and test the map after.
A second error is changing the site design in the same week as the move. A new design plus a new host means a ranking drop has two possible causes and no clear fix. Move first, prove the rankings held, and redesign later.
A third error is ignoring the search console for a week after the switch. The console reports crawl errors and coverage problems within days, and a fix applied in week one costs far less than a fix applied in month two. Check it daily for the first fortnight.
Your First Week After Moving a Website to a New Host
The question of how to move a website to a new host without losing seo is proven in the first week after the switch. Check the search console daily, watch the traffic against the week before the move, and open the top ten pages from a phone and a computer. A small dip in the first days is normal, while a large drop means something is wrong.
Keep the old host live and untouched for the whole week. Some visitors and some search engines still reach the old address for days after the DNS change, and the old site catches them. Cancelling early is the most common regret in this guide.
At the end of the week, compare the numbers and decide whether the move is done. If traffic and rankings are steady, cancel the old host and keep a final backup. If a page still errors, fix it before cancelling, because the old host is the only safety net.
How to Keep a Website Move Cheap and Safe
The question of how to move a website to a new host without losing seo can be answered cheaply, because most hosts offer a free migration service. Use the host team for the transfer and spend the owner time on testing, which is the part only the owner can do well.
Avoid paying for a premium migration plugin when the host offers the same move for free. A plugin is worth buying only when the host offers no migration help and the site is large.
Choose a host with a long renewal price in writing before signing up. Several hosts cut the first year heavily and then charge three times more, and the saving is real when the renewal price is known upfront.
Do the move in a quiet week instead of paying for rush help. A move done slowly by the owner costs nothing but time, while the same move done in a hurry by a hired hand costs a day rate.
Keep one backup in free cloud storage instead of buying a backup service for the move. A single full backup downloaded to a local drive and a free storage account is enough for a small site.
Reuse the audit spreadsheet for the next move or redesign. The page list, the redirect map, and the keyword record are assets that save hours every time the site changes.
How We Verified Every Step of This Website Move
The question of how to move a website to a new host without losing seo was checked against the migration guides of the major hosts and the search engine documentation on site moves. Where a host offers a free migration or a staging area, the guide notes it, because an owner who expects help deserves to know before signing up.
The steps were judged on real site work, like auditing a page list, testing a staging copy, and reading search console errors after a switch. A step that catches a real problem before visitors see it scored well here, whatever its length.
Frequently Asked Questions
How long does a website move take?
A small site takes four to eight hours spread over a week, with most of the time spent on the audit and the testing. A large site with hundreds of pages takes longer, and the DNS spread alone takes up to two days. The move itself is quick, and the checking is what takes time.
Will moving hosts hurt my search rankings?
Not when the steps in this guide are followed in order. Rankings drop when pages disappear, redirects are missed, or the new site is slow. An audit, a redirect map, and a staging test keep the rankings steady, and a small dip in the first days is normal.
Should I keep the old host after moving?
Yes, for at least two weeks. Some visitors and search engines still reach the old address for days after the DNS change, and the old site is the only way back when something breaks. Cancel only after two clean weeks, and keep a final backup first.
What is the biggest mistake in a host move?
Skipping the audit and the redirect map. An owner who moves without a page list has no way to know what was lost, and a page that returns an error loses its ranking within weeks. The audit takes an afternoon and prevents the most expensive failure.
Can I move a website myself without a developer?
Yes, for a small site. A migration plugin or a free host migration service handles the transfer, and the owner handles the audit and the testing. A large shop or a site with custom code is the point where hired help earns its fee.
Habits That Keep a Moved Website Healthy
Check the search console every week, not only after a move. A coverage error caught early costs minutes to fix, while the same error found a month later can cost a ranking that takes weeks to win back.
Keep the backup routine running on the new host. A daily automatic backup is the cheapest insurance a site owner can buy, and it matters most in the week after a change.
Keep a note of the host login, the DNS settings, and the backup location in one safe place. A move done in a hurry is hard enough without hunting for passwords, and the record makes the next move faster.
The Website Move Most Owners Should Make First
The question of how to move a website to a new host without losing seo has one step that matters more than the rest, and it is the audit. A site owner who lists every page, every redirect, and every ranking keyword before the move can prove the new site is complete, and the rest of the steps are routine. Start with the audit, and the move follows.
Start this week, on a quiet day, and work the steps in order. The move should make the site faster and cheaper to run, not riskier, and the audit is the step that makes that true. Judge the move by whether the rankings hold after two weeks.