How to Migrate a Website Without Losing SEO

You keep your rankings through a migration by doing four things: list every URL the old site has, keep addresses that do not need to change, redirect every address that does change to its closest new equivalent with a permanent redirect, and watch Google Search Console closely after launch. Skip any one of them and the traffic that brings you enquiries can fall away. This guide walks through the full checklist for a relaunch, a platform change, a new host or a new domain, written for Irish small businesses.
TL;DR
- Before anything changes, record every live URL and its traffic, and decide which ones can stay exactly as they are.
- Use server-side permanent redirects (301 or 308) from each old URL to its closest new page, and keep them in place for at least a year.
- Keep the new site hidden from Google while you build it, then remove every block on launch day.
- Expect a temporary wobble in rankings. Compare Search Console and analytics against your pre-launch figures to tell normal reprocessing from a real fault.
- Change as little as you can in one go: a new design on the same URLs is far safer than a new design, new domain and new structure together.
Table of Contents
- What counts as a migration, and why rankings are at risk
- Before you build: take stock of what you have
- Build the new site out of Google’s sight
- The redirect map: the heart of the migration
- The technical checklist before launch day
- Launch day
- After launch: what to watch and when
- Common mistakes that cost Irish small businesses traffic
- Redesign, rebrand or just a new host?
- Getting help with a safe relaunch
- FAQ
- Sources
What counts as a migration, and why rankings are at risk
A migration is any change that alters how Google reaches your pages. That covers a redesign on a new platform, a new domain after a rebrand, a switch from http to https, a restructured menu with new page addresses, or a move to a new hosting provider.
Google ranks addresses, not designs. When an address disappears or changes without a clear signal, the history attached to it (links from other sites, years of being indexed, clicks) has nowhere to go. The risk is highest when URLs change, lower when only hosting changes. Google’s own guidance on changing hosting without changing URLs is a short, low-risk process: prepare the new servers, switch DNS, and monitor traffic.

That gives you the first rule: the fewer things you change, the less you can lose. The team at Agility Docs puts it well: the safest redirect is the one you do not need, so keep existing URL paths wherever you can.
Before you build: take stock of what you have
The most important work happens before a single new page exists. John Mueller of Google has said that tracking individual URLs, so you know what existed and what should exist afterwards, is the most crucial part of a migration.
Build a full URL inventory
Create a spreadsheet with one row per page. Pull addresses from several places, because no single source is complete:
- your current XML sitemap
- Google Search Console (the pages that get impressions and clicks)
- Google Analytics or whichever analytics tool you use
- a crawl of the live site with a crawling tool
- a backlink report, so you know which pages other sites link to
For each URL, note the page title, the main heading, the monthly clicks, and whether it has external links. A tradesperson with a 12-page site may finish this in an hour. A shop with hundreds of products needs a proper export.
Decide the fate of each page
Give every row one of four outcomes:
- Keep the address. Same URL, new design. No redirect needed.
- Change the address. Old URL gets a redirect to a specific new URL.
- Merge into another page. Several thin pages become one stronger page, and all the old addresses redirect to it.
- Retire. No equivalent exists, so the page can be removed.
For retired pages with no real match, Agility Docs advises returning a 404 or 410 rather than redirecting everything to the home page. A redirect to an unrelated page confuses visitors and gives Google little reason to pass on relevance.
Record your benchmarks
Before launch, export 3 to 6 months of data: organic clicks and impressions by page, your top search queries, enquiry form submissions, calls and WhatsApp clicks. Without a baseline you cannot tell later whether a dip is serious. Also screenshot your current Google Business Profile details, as the website address listed there will need to stay correct.
Build the new site out of Google’s sight
A new site under construction should not be indexed. Put it on a staging address protected by a password, which is more reliable than a request to search engines to stay away.
Then make sure of three things while you build:
- Content carries across. Titles, headings, body copy, image alt text and internal links on pages that already rank should be preserved or improved, not stripped back. A prettier page with a quarter of the words can rank worse.
- Structure is crawlable. Important pages are reachable through normal links, not hidden behind scripts or menus that only work on click.
- Local signals survive. Your business name, address and phone number, your service-area pages and your embedded map should all reappear. If you rely on location pages, our guide to keeping location pages useful covers the checks worth doing.
The redirect map: the heart of the migration
A redirect map is a two-column list: old URL on the left, new URL on the right. Google’s site move documentation recommends server-side 301 (moved permanently) or 308 redirects that point each old URL directly at its new one, avoiding chains where A goes to B goes to C.
Rules for a clean map
- Match page to page. Redirect to the closest equivalent, not the home page. The Agility Docs guidance notes that closest-equivalent redirects protect relevance and user intent.
- Use permanent redirects. A temporary 302 tells Google the old address is coming back.
- Avoid chains and loops. Test the final target of every redirect, including
wwwand non-wwwandhttpandhttpsversions of each old address. - Redirect at the server level. Not through a page that loads and then jumps with a script.
Example
Suppose a plumber in Galway changes from an old builder to a new site:
| Old URL | New URL | Action |
|---|---|---|
| /services.html | /services/ | 301 redirect |
| /boiler-repair-galway.html | /boiler-repair-galway/ | 301 redirect |
| /gallery-2019 | none | Retire (404 or 410) |
| /about-us | /about/ | 301 redirect |
If you want a step-by-step on the mechanics for domains, we have written a full guide to domain redirect setup for Irish businesses.
How long to keep redirects
Google recommends keeping redirects in place for as long as possible, generally at least one year, so that signals transfer to the new URLs. Do not delete them the week the traffic looks settled. If you change domain, the same applies to the old domain itself: Google says to keep paying for it for at least a year. Let it lapse and someone else can register it and inherit the links pointing at it.

The technical checklist before launch day
Work through this the day before launch, on the staging site, and again immediately after it goes live.
Crawling and indexing
- Remove any
noindextags left on staging pages. This is the most common launch-day mistake, and it can remove a whole site from search. - Check that
robots.txton the live site does not block the whole site or important folders. Google’s guide on changing hosting tells you to remove any temporary blocks to crawling when you start the move. - Generate a new XML sitemap that lists only the final, indexable, live URLs.
- Check that each page has one canonical address pointing at itself, on the correct domain and protocol.
On-page elements
- Every page has a unique title tag and meta description.
- Each page has one clear H1 heading and a logical heading order.
- Images have descriptive alt text and are compressed for fast mobile loading.
- Internal links point to the new URLs directly, not through the redirects.
- Structured data (such as local business details) has carried across and validates.
Technical health
- HTTPS works on every page with no mixed-content warnings.
- Forms, WhatsApp buttons and phone links work on mobile and desktop. A migration that keeps rankings but breaks the enquiry form still costs you business.
- Analytics and conversion tracking are installed and recording.
- 404 pages are friendly and point users to useful pages.
Business email and DNS
If you change host or domain, record your email DNS settings (MX, SPF and similar records) before touching DNS. Moving a website sometimes silently breaks business email, which is a nasty surprise when customers cannot reach you.
Launch day
Choose a quiet time, not the week before your busiest season. A sensible order is:
- Put the new site live and switch DNS if the host is changing.
- Switch on the redirects and test a sample of old URLs, including your top 20 pages by traffic.
- Confirm that no blocks to crawling remain.
- Submit the new sitemap in Google Search Console.
- If you changed domain, use the Change of Address tool.
On that last point, Google says to use the Change of Address tool for all verified variants of the old domain, including subdomains and both www and non-www versions. After using it, keep redirects in place for at least 180 days, and longer if Google Search traffic still arrives at the old address.
If you also changed your business name, update your Google Business Profile, directory listings and social profiles so the new address is consistent everywhere. Our Google Business Profile setup help page explains what we look after there.
After launch: what to watch and when
Google states you should expect temporary ranking fluctuations during a significant site migration while it recrawls and reindexes your pages. A small dip in the first days or weeks is normal. What matters is the pattern.
The first week
- Open Search Console daily. Look for crawl errors and rising 404s.
- Check that the sitemap has been read and that the number of indexed pages is climbing.
- Click through your top pages from Google search results and make sure each lands where it should.
- Fix redirect gaps as you find them: any old URL that returns a 404 but had traffic needs a redirect.
Weeks two to eight
Compare organic clicks, rankings for your main searches and enquiry numbers against the benchmarks you saved. A practical approach, also described in Pantheon’s migration checklist, is to monitor 404s, ranking volatility and sitemap indexing status, then compare post-launch traffic and conversions with pre-migration figures.
How to read what you see:
| What you see | Likely meaning | What to do |
|---|---|---|
| Small, short dip, then recovery | Normal reprocessing | Keep monitoring |
| Specific pages vanish from results | Redirect missing, noindex or canonical fault | Check those URLs directly |
| Whole site drops sharply and stays down | Crawl block or major technical fault | Check robots.txt and noindex first |
| Traffic fine, enquiries down | Form, tracking or content problem | Test forms; see our guide to sites not getting enquiries |
Months three to twelve
Keep the redirects. Review them against Search Console once a quarter and update any internal links that still pass through a redirect. A regular routine helps here, and our website maintenance checklist fits into 45 minutes.
Common mistakes that cost Irish small businesses traffic
- Redirecting everything to the home page. It looks tidy and wastes the relevance each page built.
- Leaving staging blocks on. The new site goes live with a request for Google to ignore it.
- Changing too much at once. New domain, new URLs, new copy and new platform together make a fault almost impossible to trace. Google’s guidance on reducing risk points to changing one element at a time.
- Letting the old domain expire. Links and redirects disappear with it.
- Forgetting the Google Business Profile. The listing still shows the old address or old name.
- Rewriting good copy for style. If a page ranks, rework its wording carefully.
Redesign, rebrand or just a new host?
How much risk you take depends on what you change:
| Change | Risk level | Main job |
|---|---|---|
| New host, same URLs | Low | Switch DNS, monitor |
| New design, same URLs and copy | Low to medium | Preserve titles, headings, content |
| New platform with new URL structure | Medium to high | Full redirect map |
| New domain | High | Redirect map, Change of Address, keep old domain |
| New domain plus new structure plus new copy | Highest | Split into stages if you can |
If your rebrand includes a new name, our rebrand website plan shows how to sequence the work.
Our view: a migration is a business job, not a design job
Most small business owners come to us after a bad experience: a site rebuilt by a friend or a larger agency, a prettier design, and enquiries that quietly dried up. The cause is almost always the same. Nobody wrote down what the old site was doing for the business before changing it.
That is why we start with a list of the pages that bring in your enquiries and keep their addresses wherever we can. We work with fixed quotations and you deal directly with the person building your site, so there is nobody to chase when you want to know why a redirect is set up the way it is.
Our approach is to keep the plan simple: protect what already works, fix what does not, and tell you in plain English what is happening. Local SEO is part of the build, not an afterthought, because for an Irish tradesperson or sole trader, the search for a service in their town is where the next job comes from. And the work does not end on launch day. Monitoring in the weeks after is where a migration is saved or lost, which is why ongoing website care matters.
niall
Getting help with a safe relaunch
If you would rather not manage URL maps and Search Console yourself, our website redesign and rebuild service is built for exactly this: moving an Irish business onto a modern, mobile-friendly site while protecting the pages that already bring in customers. Our website packages start at €499 for a Launch Website, with Website Care from €29 per month covering hosting and technical upkeep. See the full pricing page for what each includes.

Tell us what your current site does well and what you want to change, and we will say plainly how much risk a relaunch carries and how we would manage it.
FAQ
Will I definitely lose rankings when I migrate my website?
Not necessarily, but a temporary fluctuation is normal. Google says to expect some movement while it recrawls and reindexes your site. With a good redirect map, unchanged content and careful monitoring, most sites recover and many improve.
Do I need a 301 or a 302 redirect?
Use a permanent redirect, which means 301 or 308, when a page has moved for good. A 302 is temporary and signals that the old address will return. Google’s site move guidance recommends server-side permanent redirects.
How long should I keep redirects after a migration?
At least a year, and longer if the old URLs still receive traffic or links. If you used the Change of Address tool, Google says to keep redirects for at least 180 days and to keep paying for the old domain for a year. There is little cost to leaving them in place.
Can I change my design without changing my URLs?
Yes, and it is usually the safest choice. If your page addresses and key copy stay the same, you avoid most redirect work and most of the risk. Change the addresses only when there is a clear reason to.
Sources
- Site Moves and Migrations, Google Search Central
- Changing your hosting, Google Search Central
- Change of Address tool, Search Console Help
- Keep Your Search Rankings Through a Migration, Agility Docs
- Google’s Mueller on Keys to a Successful Site Migration, Search Engine Journal
- A Phase-by-Phase SEO Website Migration Checklist, Pantheon
