Moving to a new website or host without losing your Google rankings

Your website brings in customers from Google. Now you want a new design, a move from an old custom site to WordPress, a different hosting company or a new domain, and you are worried the move will cost you those customers. The worry is fair. A site that goes live with changed links, missing pages or a leftover "do not index" setting can lose much of its search traffic within weeks, and winning it back is slow.

A migration does not have to hurt, though. Google can follow a move well when every old address leads clearly to a new one and the content people searched for is still there.

First, know what kind of move this is

Not every move carries the same risk:

• Host change only (same domain, same pages, same links): the lowest risk. The jobs are a clean copy, little or no downtime, and checking afterwards that nothing broke.
• Redesign or new platform (same domain, but page addresses or content change): medium risk. Every old address needs a new home.
• New domain: the highest risk. Every page changes address, and Google needs time to carry over what it knew about the old site.

Many projects combine two or three of these. If you can, do them one at a time.

Before launch: build the map

1. Record where you stand. Export your top pages and search queries from Google Search Console and note current traffic in your analytics. You need a baseline to compare against later.
2. List every old URL. Use your sitemap, the page indexing report in Search Console and a crawler tool. Include blog posts, product and category pages, PDFs and any images that get traffic.
3. Map old to new. In a spreadsheet, put each old URL next to its new URL. Pages with traffic, or with other sites linking to them, need a close match, not just the home page.
4. Keep what ranks. Your best pages should keep their main text, headings and titles, even if the design changes. Rewriting them during the move makes any later problem hard to trace.
5. Test on a staging copy that search engines are blocked from, and check the redirects there before launch.

On launch day

1. Set up permanent (301) redirects from every old URL to its mapped new URL. Avoid chains where one redirect leads to another.
2. Remove the "noindex" or "discourage search engines" setting that protected the staging site. This one forgotten setting is behind many failed launches.
3. Check robots.txt, the HTTPS certificate and the canonical tags on key pages.
4. Submit the new sitemap in Search Console. If the domain changed, verify the new domain there too and use its change of address feature.
5. Open your top pages on a phone using mobile data, the way many of your customers will.

Mistakes that cost rankings

• Redirecting every old page to the home page. Google may treat these as missing pages rather than moved ones.
• Letting the old domain or hosting lapse too soon. Keep the old domain and its redirects running for a long time, ideally permanently.
• Dropping "unimportant" pages that were quietly bringing in search visitors.
• Launching just before your busiest season, such as the weeks before Eid, when you cannot afford a dip.

Some ups and downs in the first few weeks are normal while Google recrawls the site. A steady fall after that usually points to a missing redirect or a blocked page.

What you can do yourself, and where help is useful

You can collect the baseline, list your important pages and test the new site from a customer's point of view. The redirect map, server rules and Search Console checks are where an experienced developer saves you from expensive mistakes, especially for a domain change or a large online shop. If traffic does fall after launch, a step-by-step traffic drop diagnosis helps find the cause.

The smallest useful first step

Before anyone touches the new design, export your top pages from Search Console and save the list. That list is the backbone of a safe move. If you are planning a migration and want a second pair of eyes, see how I handle website development and migrations.