How to switch website providers without losing Google rankings

Updated September 26, 2026

You want a better website provider without undoing the search visibility your business has already earned. The safest starting point is to preserve what customers and Google already use: your domain, useful pages, and their addresses. Treat the switch as a planned handover, with someone responsible for checking every important page.

Decide what is actually changing

A hosting move keeps the same website addresses on different equipment. A rebuild may also change the pages, their content, or their addresses. A domain change adds another task because your business is moving to a different web address altogether.

Write down which changes you need. Switching providers does not automatically mean choosing a new domain or transferring your domain registration. Keeping the current domain is usually the simpler choice when the business name has not changed.

Ask the new provider to explain the move in plain English: which services move, who changes the domain settings, and whether email is affected. Our guide to website hosting in plain English helps separate the parts.

If you only need new hosting, Google's hosting change guidance recommends preparing and testing the new infrastructure before directing traffic to it. Give the provider that scope rather than accepting a complete rebuild by default.

Save the pages and results you have now

Make a list of existing page addresses before work begins. Include pages outside the main menu, such as older service guides, project examples, seasonal offers, and downloadable information. Ask your current provider for a full page list and sitemap.

For each important page, record:

• Its current address and page title.
• The service or customer question it covers.
• Photos and text you are entitled to reuse.
• Where its contact form sends inquiries.
• Whether it should stay, change, or be removed.

Use Search Console to identify pages already receiving search clicks. Save a dated performance export and note seasonal conditions, such as a heating contractor moving during the transition into winter. Later, you will have a useful comparison rather than a vague memory that calls used to be better.

If reporting has never been connected, set up Search Console as soon as practical. Keep your business account in control throughout the handover.

Keep working addresses and useful content

Give the new provider the page list and ask them to preserve existing addresses wherever possible. A water heater repair page should remain a water heater repair page, even if its design improves. Replacing it with a general plumbing page removes information customers previously found useful.

Read the old and new versions side by side. Check service descriptions, towns served, qualifications, access instructions, and the next step for booking. Correct stale claims, but do not erase helpful details merely because a shorter page looks cleaner.

Avoid combining a provider move, new domain, new page structure, and wholesale rewrite unless the work truly requires it. Google's site move guidance recommends changing one major thing at a time where possible and notes that search visibility can fluctuate during a move.

Make the scope explicit in writing. Ask which existing pages will be recreated, which will disappear, and who approves those decisions. A preview of only the homepage is not enough to approve the whole move.

Map changed pages to relevant replacements

If a page address must change, create a simple old-address-to-new-address list. Each old address should lead to the closest relevant replacement. A roof leak repair page should send visitors to the new roof leak repair page, not automatically to the homepage.

Ask the provider to implement permanent server redirects, normally 301 or 308 redirects, for permanent moves. Those responses tell browsers and search engines where the page has moved. Google's redirect guidance explains the distinction between permanent and temporary redirects.

Do not accept a blanket redirect of every missing page to the homepage. If a service is truly gone and there is no relevant replacement, discuss returning a proper missing-page response instead. For retained services, rebuild the useful page or choose a destination that answers the same need.

For changed URLs, Google recommends keeping redirects for at least a year in its site move guidance. Agree who will maintain them before cancelling any service that currently provides them. Update links inside the new website so they point directly to the final addresses.

Test the move before cancelling anything

Ask for a working preview and a written launch checklist. Open each priority page on your phone and walk through the tasks customers actually perform. A garage door repair customer should be able to find the service area, tap the phone number, and submit a repair request.

Check the following with the provider:

1. All agreed pages and images are present.
2. Forms deliver messages to the right inbox.
3. Phone numbers and booking links work.
4. The live domain will use a valid security certificate.
5. Temporary preview restrictions will not block the launched website from search.
6. Redirects, preferred page addresses, and the sitemap match the finished site.

Keep a copy of current DNS records before changes. Email records need particular care if nameservers are changing. Arrange the switch when both providers can respond, and agree how to restore service if launch checks fail.

Resolve account access through the designer handover checklist before the old provider's involvement ends. Do not assume the domain, email, and website all share the same cancellation date.

Watch customers and search after launch

Visit old page links directly after the switch. Confirm that each loads the same page or reaches its intended replacement, with no loops or missing-page surprise. Send another form submission from the live site and verify receipt.

Submit the current sitemap and inspect your priority pages in Search Console. Review new errors and compare search performance with your saved baseline, allowing for reporting delays and seasonality. A sustained drop affecting one service page gives you something specific to investigate.

If the domain itself changes, ask the provider to follow Google's Change of Address instructions, including the required redirects. That tool is not for simply changing hosts while keeping the same addresses.

Record actual calls and requests alongside search clicks. Our guide to measuring website inquiries helps you check whether the customer journey still works after the move.

Frequently asked questions

Can anyone guarantee I will keep every ranking?

No. Search results change, and Google needs to process significant website changes. A careful provider should explain the risks and the checks they perform rather than promise an unchanged position.

Do I need to transfer my domain to the new designer?

Not necessarily. Your domain can often remain with its existing registrar while its website records point to the new host. Decide registration, website hosting, and email arrangements separately.

Can I delete old blog posts during the move?

Review them first. An older article may still answer a useful question or bring customers to a service page. Keep, improve, or retire each page deliberately instead of deleting everything by publication date.

Should I close the old hosting account on launch day?

Wait until the agreed checks pass and you know which services still depend on it. Ask the provider to confirm where email, DNS, and redirects will run afterward. Cancel only the services that are no longer needed.

The short version

Preserve the useful pages and addresses your business already has. Plan redirects, test real customer actions, and monitor the live site after the switch. No move comes with a ranking guarantee, but a documented handover reduces avoidable mistakes. With Front Step Sites, your domain is registered in your own name, and you can leave any time and take it with no transfer fee.