A website migration is any significant change to your site: a new domain, a new platform, a redesign, or a restructured set of URLs. Done carelessly, it is one of the fastest ways to lose the search rankings you have spent months or years building. Done properly, it barely causes a ripple.
Direct answer: the single biggest factor in a safe migration is redirecting every old URL to its new equivalent using 301 redirects, so both visitors and Google are pointed to the right place. Combine that with a pre-migration audit of your top pages, a like-for-like content match, and post-launch monitoring, and most small business sites recover fully within a few weeks.
Here is how to do it properly.
What counts as a website migration?
Not every website change is a migration. A migration involves one or more of these:
- Moving to a new domain name
- Changing from HTTP to HTTPS, or www to non-www
- Switching platforms, such as moving from a website builder to WordPress
- A redesign that changes your URL structure
- Merging or splitting websites
A simple redesign that keeps the same URLs and platform is lower risk and does not need the full process below, though the monitoring step still applies.
Step 1: audit your current site before touching anything
Before you change a single thing, document what you currently have. This is your baseline, and without it you cannot tell later whether the migration went well.
- Export a full list of your current URLs
- Note your top-performing pages by traffic, using your analytics tool
- Record current rankings for your most important keywords, so you have something to compare against afterwards
- Check for broken links and fix them before migrating, since a broken link carried into the new site becomes a broken link on the new site too
Step 2: map every old URL to its new equivalent
This is the step that determines whether your migration is smooth or disastrous. Every existing URL needs a clear destination on the new site.
How to do it: create a simple spreadsheet with two columns, old URL and new URL. Go through every page on your current site and decide where it lives on the new one. If a page genuinely no longer exists and has no equivalent, that is fine, but note it deliberately rather than letting it fall through unnoticed.
Step 3: set up 301 redirects for every mapped URL
A 301 redirect tells browsers and search engines that a page has permanently moved, passing on most of its accumulated ranking value to the new URL.
How to do it: in WordPress, a redirection plugin lets you set these up without editing server files directly. Work through your URL map from step 2 and create a redirect for each row. Avoid redirecting everything to your homepage as a shortcut. This loses the specific relevance each page had and is treated as a weak signal by Google.
Step 4: keep core content consistent
If a page’s content changes dramatically during the migration, along with its URL, Google has less reason to treat the old page’s ranking history as relevant to the new one.
How to do it: for your most important pages, keep the core topic and main heading similar even if you refresh the wording. Save major content rewrites for after the migration has settled, so you are only testing one variable at a time.
Step 5: update your XML sitemap and submit it
Your sitemap tells Google exactly which URLs exist on your new site.
How to do it: most SEO plugins generate this automatically. Once your new site is live, submit the updated sitemap through Google Search Console and request indexing for your most important pages directly, rather than waiting for Google to find them on its own schedule.
Step 6: monitor closely for the first few weeks
Some ranking fluctuation immediately after a migration is normal, since Google needs time to recrawl and reprocess your site.
How to do it: check Google Search Console weekly for coverage errors, particularly 404s on pages that should have redirected. Compare rankings for your key terms against your pre-migration baseline. A temporary dip that steadily recovers over three to six weeks is typical. A dip that keeps getting worse usually means a redirect or content issue needs fixing.
Migration checklist
| Step | Task | Why it matters |
|---|---|---|
| 1 | Audit current URLs, traffic and rankings | Gives you a baseline to compare against |
| 2 | Map every old URL to a new one | Prevents pages falling through unnoticed |
| 3 | Set up 301 redirects for every mapped URL | Passes ranking value to the new page |
| 4 | Keep core content consistent | Preserves topical relevance signals |
| 5 | Submit an updated sitemap | Helps Google find and recrawl the new site faster |
| 6 | Monitor weekly for six weeks | Catches redirect or indexing problems early |
Common mistakes that cause real ranking loss
- Redirecting everything to the homepage. This discards the specific relevance of each page and is a weak, generic signal.
- Changing the domain and the content at the same time. Too many variables change at once, making problems hard to diagnose.
- Forgetting internal links. If your internal links still point to old URLs, visitors and search engines hit unnecessary redirect chains. Update them to point directly to the new URLs.
- No pre-migration baseline. Without knowing your starting rankings and traffic, you cannot tell whether a dip is normal or a genuine problem.
When migration is part of a bigger redesign
Migration risk is one of the main reasons a full redesign needs careful planning rather than a rushed rebuild. If you are weighing up whether your site actually needs a full redesign or just a lighter refresh, our guide on the signs it’s time for a redesign is worth reading first, since a well-planned redesign that follows the steps above should protect your rankings and often improves them once the dust settles.
FAQs
Will migrating my website hurt my search rankings? It can, temporarily, but a well-planned migration with proper 301 redirects for every page typically causes only a short-term dip that recovers within a few weeks.
How long does it take Google to reindex a migrated website? Most small business sites are substantially recrawled within one to two weeks of submitting an updated sitemap, though full stabilisation of rankings can take up to six weeks.
Do I need to redirect every single page? Yes, ideally. Any page without a redirect returns a 404 error, which is a poor experience for visitors and a lost opportunity to pass on that page’s ranking value.
Can I migrate a website myself without a developer? For a straightforward WordPress site with a redirection plugin, yes, provided you work through the steps above methodically. More complex migrations, such as a full platform change, benefit from experienced help.
