You want to move your website somewhere else but you are afraid of vanishing from Google. Here is what actually causes that, and how to move without it.
Most people who are unhappy with whoever looks after their website stay put anyway, and when you ask why, the answer is almost always the same. They are not worried about the cost or the hassle. They are worried about disappearing from Google.
It is a reasonable fear. Sites do lose visibility when they move. But they lose it for specific, avoidable reasons, and knowing what those are turns a vague dread into a checklist.
What actually causes the drop
Moving hosting does not cost you rankings. Google does not know or care which company's server your site sits on.
What costs you rankings is changing your URLs and not telling anyone.
Say you have a page at /servicios/instalaciones-electricas that has spent three years earning its place for a search that brings you work. The new site rebuilds it at /electricidad. Nobody connects the two. As far as Google is concerned the old page has gone and a brand new one has appeared with no history. Every link pointing at the old address now leads nowhere.
Do that across forty pages and you have not moved your website. You have deleted it and published a different one.
The one thing that prevents it
A redirect. Specifically a permanent one, a 301 or a 308, from every old address to the page that replaces it.
Google has said plainly that permanent redirects do not cause a loss of ranking signals. The equity your old page built transfers to the new one. This is the single most important task in any move, and it is the one most often skimped.
Three ways it gets done badly.
Using a temporary redirect. A 302 tells Google the move is not permanent, so it holds off passing the signals across. Months can go by before it settles.
Chaining them. Old page to interim page to final page. Each hop bleeds a little and slows crawling. Map old straight to new.
Sending everything to the homepage. This is the one that really hurts, and it is common because it is easy. Someone points all forty old URLs at the front page, the site technically has no broken links, and every specific page's history is thrown away. A person searching for a specific service lands on a generic homepage and leaves.
What a proper move looks like
Before anything changes, list every URL the old site has. Your existing sitemap, Google Search Console and a free crawler will each give you a list, and between them you will have all of it.
For each one, decide where it goes. Most map one to one. Some merge. A few genuinely have no replacement, and those should return a proper 404 rather than being pointed somewhere irrelevant.
Then, and this matters more than people expect: keep the URLs the same wherever you sensibly can. A redirect is a repair. Not needing one is better. If the old addresses are readable and describe the page, carry them over even if you would have named them differently starting fresh.
Before you switch anything over, lower the TTL on your DNS records a day or two ahead. That is the setting that controls how long the internet caches where your domain points. Drop it to a few minutes and the switch happens in minutes rather than over a day of some people seeing the old site and some the new.
Check the new site properly on a staging address first, with search engines blocked from it. Then, on the day, put the redirects live at the same moment as the site, not afterwards.
What to expect afterwards
Be realistic. Even a well-run move usually shows a wobble.
Typical figures reported for a well-executed migration are that things settle within about two to four weeks, with more complex sites taking longer. A redesign that also changes content and structure can show a noticeable dip in the first month before recovering.
So do not judge it after five days. Watch for a month, and watch the right things: pages indexed, crawl errors, and whether your important pages are still ranking for the searches they used to. Google Search Console shows all three for free.
If traffic has not returned after two months, something is wrong and it is worth looking rather than waiting.
The things people forget
Rankings get the attention, but these cause more day to day pain.
Email. If your email runs on the same domain, moving hosting can interrupt it. Establish where your email is actually hosted before anything moves. This catches people out constantly.
The domain itself. If your current provider registered it in their own name, you may find you cannot move at all. That is worth checking before you start, and we wrote about how to find out who owns your domain separately.
Your Google Business Profile. If the site address changes, update the listing. It is a two minute job that is easy to forget for six months.
Analytics and Search Console. Make sure the new site is verified and tracking before launch, not a fortnight later when you want to know whether the move worked.
Common questions
Can I move if my current provider will not help?
Usually yes, though it is more work. The site content can be recovered, and the domain can normally be transferred through the registrar's own process. It is harder if the domain is registered in their name rather than yours.
Will I lose my Google reviews?
No. Reviews belong to your Google Business Profile, not to your website. Changing the site does not touch them.
How long does the actual switch take?
The technical switchover is usually under an hour if the preparation is done. The preparation is the job; the launch is the easy part.
Should I move and redesign at the same time?
It is more efficient, and it is what most people want. Just know that if something goes wrong afterwards you will have two possible causes rather than one. Get the URL mapping right and it is a perfectly normal thing to do together.
The short version
You are allowed to leave. Being afraid of Google is not a good reason to stay with someone who is not looking after you.
Map every URL, redirect permanently, keep the addresses you can, and watch Search Console for a month. That is the whole job.
If you would rather not do it yourself, moving sites across is a normal part of what we do when we build a website, redirects included. Send us your current address and we will tell you honestly how involved the move looks.