Moving Hosts Without Losing Your Google Rankings

Your new website is live, but now a bunch of old links on search engines lead to 404 pages. That is traffic you worked for but have essentially thrown away.
That is the migration mistake people make when leaving WordPress, changing hosts, rebuilding a site, or simply tidying up page names. Your new site may look better, load faster, and be easier to manage, but search engines, bookmarks, shared links, and old emails still point to the addresses people knew before.
The good news: you do not need to sacrifice your hard-earned visibility to move a small website. You need a URL plan, a redirect list, and a little testing before launch.
Keep URLs whenever you can
A page URL is more than a technical detail. It is the address Google may have indexed, another website may have linked to, and a customer may have saved. If your old service page lived at /roof-repair, keeping that address on the new site is usually the cleanest option.
When a URL must change, add a redirect from the old address to the closest useful new page. Do not send every retired page to the homepage. Someone looking for a specific service, article, or location page should land somewhere that answers the same need.
Make an inventory before you move
Before rebuilding or publishing, list the URLs that matter. Start with your main navigation, service pages, contact page, popular articles, campaign pages, and any URLs used in ads, email, printed materials, or social profiles.
For a larger site, pull a report of your 100 most-visited pages from Analytics. Then make a simple migration checklist:
- Keep the same URL when the page still exists.
- Create a replacement page when the topic still matters.
- Add a redirect when a page moved or was renamed.
- Retire a page only when there is truly no relevant replacement.
If you are moving off WordPress, this is also a good time to read how to convert a WordPress site with AI. A static rebuild can simplify the site dramatically, but it should not erase the map that brings people to it.
Use WebHaste Redirects to preserve old addresses
WebHaste includes a Redirects dialog for mapping old paths to new paths. Add the old path in the “from” field, the destination in the “to” field, and choose the status code that fits the change.
- 301 (permanent): Use this when a page has moved for good, such as a renamed service page or a WordPress URL replaced by a new static page.
- 302 (temporary): Use this when the change is short-term and the original URL is expected to return.
If you paste a full old URL, WebHaste normalizes it into the path needed for the redirect rule. That is handy when your spreadsheet contains complete addresses such as https://example.com/about.html.
The extensionless URL gotcha
Cloudflare Pages and Netlify commonly serve pages without the .html extension. A visitor may request /about even when the page is stored as about.html. This is typically a good thing for users.
WebHaste accounts for this by emitting an extensionless redirect form alongside each .html rule. It is a small detail with a large payoff: fewer broken links caused by the difference between how files are stored and how modern hosts serve them.
One redirect file for Cloudflare Pages and Netlify
When you deploy with Cloudflare Pages or Netlify, WebHaste writes compatible redirect rules to _redirects. That means the same project can move between those hosts without making a separate redirect plan for each one.
There is one important limitation: redirects are not forced. On Netlify, a real page can take precedence over a redirect rule. If you create a new file at an old URL, test the result carefully: you may be serving the page instead of the redirect you expected.
Know when host-level rules are required
WebHaste redirect rules are built for Cloudflare Pages and Netlify. They do not apply automatically to a self-hosted server like Apache or a Packaged offline build.
If you publish to traditional hosting, configure redirects using your server’s tools — for example, an Apache .htaccess file — or ask your host which redirect method it supports. Some hosting companies allow you to manage redirects from a control panel or via CPanel.
Note: Packaged sites are designed to run from a folder or USB stick, so server-side redirects are not available there at all and aren't needed.
Test before and after launch
Do not treat redirects as a set-it-and-forget-it task. Before launch, test a sample of old URLs directly in a browser. After launch, test them again on the live domain.
- Open old URLs from your inventory and confirm they reach the intended new page.
- Check that permanent moves use 301 redirects.
- Run WebHaste Check Links to catch broken internal links.
- Confirm your sitemap reflects the pages you want search engines to find.
- Watch for 404s after launch and add redirects for overlooked addresses.
For a deeper cleanup pass, use the WebHaste Link Checker before you publish. It is much easier to fix a bad link while the project is open than after a customer reports it.
Move the site, not your SEO problems
A new host or a simpler CMS should make your life easier, not reset years of discoverability. Preserve valuable URLs, redirect the ones that change, and verify the work. That is the practical path to a cleaner site without abandoning the traffic you already earned.
Build and publish with WebHaste
WebHaste is a free, open-source CMS and website builder that runs locally in Chrome. You keep control of your files, hosting, and backups while getting visual editing, SEO tools, static HTML output, and direct deployment options for Cloudflare Pages and Netlify.
Download WebHaste: Get the free WebHaste Chrome extension.
Starting a new site? Use the free Bootstrap starter, Tailwind starter, or Bootstrap Business Frontpage starter.
Recent Articles