Website Migration Guide: Move Your Site Without Losing SEO Rankings
A step-by-step guide for Irish businesses planning a website migration — switch hosts, platforms, or domains while preserving your hard-earned search rankings.
Migrating your website is one of the riskiest things you can do to your online presence. Done properly, it's a smooth transition that preserves (or even improves) your search rankings and traffic. Done badly, it can wipe out years of SEO work overnight. This guide walks you through every type of migration and how to do each one safely.
Website Migration: Moving Your Site Without Losing Everything You've Built
Website migration is one of the riskiest things you can do to your online presence. Done properly, it's a smooth transition that preserves (or even improves) your search rankings and traffic. Done badly, it can wipe out years of SEO work overnight. This guide walks you through every type of migration and how to do each one safely.
Types of Website Migration
Host migration — moving your website to a different hosting provider while keeping everything else the same. This is the least risky type if done correctly, as your URLs, content, and domain don't change. See our hosting guide for help choosing a new host.
Platform migration — moving from one CMS to another (e.g., Wix to WordPress, Squarespace to Shopify). This is more complex because URL structures, templates, and functionality all change. It's also the type most likely to cause SEO problems if redirects aren't handled properly.
Use a crawling tool like Screaming Frog to compare your old site structure against your new one. You can export both crawls and compare them side by side to identify any missing pages or broken URL mappings before going live. This catches problems that manual checking would miss.
Domain migration — moving to a new domain name entirely (e.g., from oldname.com to newbrand.ie). The highest risk migration because you're essentially telling Google 'everything you knew about my old site now applies to this new address.' It takes time for Google to process this.
HTTP to HTTPS migration — moving from an unsecured to a secured connection. This should be straightforward but still requires proper redirects and Search Console configuration.
Pre-Migration: The Preparation That Saves You
Crawl your current site — use a tool like Screaming Frog to create a complete list of every URL on your current site. This is your master reference for setting up redirects. Export the list and keep it safe.
Document your current SEO performance — record your current rankings, organic traffic, top-performing pages, and backlink profile. Take screenshots from Google Search Console and Analytics. You need this baseline to measure whether the migration was successful.
Create a redirect map — this is the most critical step. For every URL on your old site, map it to the corresponding URL on the new site. Every. Single. One. Use 301 (permanent) redirects. This tells search engines that the content has moved permanently and to transfer the SEO value to the new URL.
Creating a detailed spreadsheet with old URLs in one column, new URLs in the second column, and status notes in a third. Share this with all team members involved in the migration. It becomes your single source of truth and prevents miscommunications that lead to missed redirects.
Back up everything — take a complete backup of your current site: database, files, images, everything. If something goes wrong, you need to be able to restore your old site quickly. Test that the backup actually works by restoring it to a test environment.
Set up a staging site — build and test your new site in a staging environment before going live. Check every page, every form, every link. Test on mobile devices. Run it through PageSpeed Insights. The staging site should be blocked from search engines (noindex, nofollow) until you're ready to launch.
During Migration: The Technical Steps
Implement all redirects — deploy your 301 redirect map. For WordPress migrations, plugins like Redirection or Yoast SEO Premium handle this. For server-level redirects, your .htaccess file (Apache) or nginx config is where they go. Consult Google's site move documentation for detailed guidance on implementing redirects properly. Test every redirect before going live.
Update internal links — while redirects handle old external links, update all internal links on your new site to point directly to the new URLs. Don't rely on redirect chains (old URL → redirect → new URL) for internal navigation — it slows down your site and wastes crawl budget.
Redirect chains are hidden redirects. If old URL A redirects to URL B, which then redirects to URL C, Google wastes crawl budget following all three. Update your internal links to point directly to the final destination. Tools like Screaming Frog can identify and report all redirect chains so you can fix them.
Preserve your content — don't use migration as an opportunity to dramatically change your page content. If a page was ranking well, keep the content similar. You can improve it, but don't completely rewrite pages that were performing. Save major content changes for after the migration has settled.
Transfer meta data — ensure all meta titles, descriptions, heading tags, image alt text, and schema markup are transferred to the new site. Losing this metadata can impact rankings even if the visible content is identical.
Using temporary redirects (302) instead of permanent redirects (301). A 302 redirect tells Google 'this is a temporary move, still credit the old URL.' Use 301 redirects so Google transfers SEO value to your new URLs. Only use 302 if you genuinely plan to move back to the old URL.
Check robots.txt and sitemaps — make sure your new site's robots.txt doesn't block search engines (a surprisingly common mistake when moving from staging to live). Generate a new XML sitemap reflecting your new URL structure.
Post-Migration: The First 30 Days
Submit your new sitemap to Google Search Console immediately. If you've changed domains, use the Change of Address tool in Search Console to notify Google officially.
Monitor for errors — check Search Console daily for the first two weeks. Look for crawl errors, 404 pages, and indexing issues. Fix any problems immediately. Some fluctuation in rankings is normal for 2–4 weeks after migration — don't panic, but do monitor closely.
Check redirect coverage — crawl your old URLs and verify they all redirect correctly. Tools like Screaming Frog can check this in bulk. Look for redirect chains (URL A → URL B → URL C), redirect loops, and any URLs that return 404 errors instead of redirecting.
Update external references — update your Google Business Profile, social media profiles, directory listings, and any other external references to point to your new URLs. For local SEO, NAP consistency across all platforms is crucial.
Track performance against your baseline — compare your post-migration traffic and rankings against the baseline you documented before migration. Allow 4–6 weeks before drawing conclusions, as Google takes time to process the changes.
Common Migration Mistakes
Missing redirects — the number one cause of post-migration traffic drops. Every old URL must redirect to its equivalent new URL. Redirecting everything to the homepage is not a solution — it tells Google the individual pages no longer exist.
Changing URLs unnecessarily — if your current URL structure works, keep it. Every URL change requires a redirect and carries some risk of SEO loss. Only change URLs if there's a genuine improvement in structure.
Migrating and redesigning simultaneously — changing your platform, design, content, and URL structure all at once makes it impossible to diagnose problems. If possible, migrate first, then redesign. Or at minimum, keep content and URLs consistent during the migration. See our redesign guide for more on this.
Removing the old site too quickly — keep your old hosting active (even if just for redirects) for at least 6–12 months after migration. This ensures all redirects continue to work while search engines update their indexes.
Ready to Discuss Your Project?
Get in touch to talk about your website, SEO, or digital marketing needs.
Get in Touch →Frequently Asked Questions
Will I lose SEO rankings during a migration?
Some temporary fluctuation is normal and usually lasts 2–4 weeks. With proper redirects and planning, your rankings should recover and potentially improve. Without redirects, you can lose significant rankings permanently. The preparation and redirect map are what make the difference.
How long does a website migration take?
A simple host migration can be done in a day. A platform migration typically takes 2–4 weeks of planning and testing before the actual switch. A domain migration needs the most preparation — allow 4–6 weeks minimum. The actual switchover should be done during low-traffic hours.
Should I migrate my website myself or hire a professional?
Host migrations are manageable for technically comfortable site owners. Platform and domain migrations are significantly more complex and carry real risk of SEO loss. If your website generates meaningful business, hiring a professional for anything beyond a simple host move is a worthwhile investment.
What if some of my old URLs don't map to new URLs exactly?
Some content inevitably changes during a migration. For pages being merged, redirect the old URLs to the most relevant new page. For pages being deleted entirely, redirect to the most relevant category page or homepage. Avoid 404 errors. Use 301 redirects consistently and test everything thoroughly.
Do I really need to keep the old hosting active for 6-12 months?
Yes. Search engines take time to reindex your entire site. External sites linking to you will continue directing traffic to the old URLs initially. Keeping old hosting active with redirects in place ensures those links still work and direct visitors to your new site. You can downgrade to minimal hosting to reduce costs.
Written by
Founder of Web Design Ireland. Helping Irish businesses make smart website investments with honest, practical advice.