Loading content
Loading content
WEBSITE MIGRATION SEO
Move, redesign, or rebuild your website with a migration SEO strategy designed to protect organic visibility, rankings, traffic, and search equity.
THE RISK
Risk often comes from changes to URLs, internal links, redirects, content, indexing, canonicalization, crawlability, and technical signals — not from “changing the CMS” as a slogan.
A migration is any move that replaces how URLs, templates, or content are served. Planning reduces avoidable loss. Rankings and traffic are not guaranteed to stay the same. If visibility already fell after a launch, see SEO recovery.
WHAT I COVER
Each area exists because a typical move can break it. This is not a copy-paste launch checklist.
A sequence for what to capture, map, test, and monitor — so launch day is not the first time SEO is considered.
What currently ranks, what is indexed, and which URLs carry useful organic demand before anything is replaced.
A list of live URLs and where each should go on the new site, so important paths are not left as 404s.
Old addresses should point to the closest relevant new URL, not a generic homepage dump.
Permanent redirects when a URL has a lasting replacement. Temporary redirects and chains create mixed signals.
Navigation, templates, and folders should still let people and crawlers reach important pages.
Crawl, index, status codes, rendering, and performance on the new stack — see technical SEO expertise for that layer.
New templates often drop contextual links. Important pages still need links from related URLs.
Canonicals must point at the intended live URL, not staging, parameters, or a deleted path.
The sitemap should list the new canonical URLs you want discovered, not the old site or noindex URLs.
A leftover Disallow from staging can hide the live site. Allow important paths before launch.
noindex, robots, and login walls accidentally left on production stop pages competing.
Useful copy, headings, and unique page jobs should survive the redesign, not only the visual shell.
Titles and descriptions that already work should be mapped, not regenerated blindly.
Schema that described products, articles, or the organisation should still match the live page — where it is appropriate.
New filenames, missing alt text, or broken media can waste crawl and weaken useful pages.
Country and language URLs, return tags, and canonicals need to move together. See international SEO when the site serves more than one market.
Property, URL prefix, and tracking must match the live host so you can compare against the baseline.
Clicks, coverage, redirects, and important landing pages after launch — not a one-week glance.
BASELINE
Without a baseline, you cannot tell post-launch noise from a real technical or content loss.
REDIRECTS
Old URLs should not simply disappear. If /services/seo-audit becomes /seo/audit, that old path should 301 to the new one — not to the homepage. Redirecting every retired URL to / is usually a poor strategy: people land on the wrong intent, and search systems get a weak replacement signal.
A 301 is appropriate when the replacement is lasting. Avoid chains (old → interim → final) and loops. Test redirects on staging and again on the live host before you treat the migration as done.
REDESIGN
A visual redesign should not remove useful search-focused content simply because the layout changed.
PLATFORM
The technology itself is not automatically the SEO problem. Implementation changes need to be evaluated carefully.
E-commerce catalogue URLs, filters, and templates need extra care — see e-commerce SEO when the move is a store.
DOMAINS
Proper planning reduces avoidable SEO risk. Rankings are not promised to remain unchanged.
CHECKLIST
PROBLEMS
If traffic or rankings already dropped after a move, these are typical places to look — alongside organic traffic recovery and ranking recovery.
Old URLs 404. Equity and bookmarks are lost. Check the map against a crawl of the old site.
A product URL sending people to an unrelated page wastes demand. Check relevance, not only status 301.
A → B → C slows crawlers and can dilute the intended target. Flatten to one hop where you can.
A and B point at each other. Neither URL is a stable landing page. Test with a crawler before launch.
New templates still linking to old paths create 404s inside the site. Recrawl after launch.
Staging noindex on production keeps important URLs out of the index. Check HTML and HTTP headers.
Canonicals to staging, HTTP, or a homepage dump can consolidate the wrong URL.
robots.txt or auth walls hide the new site. Confirm important paths are allowed.
Discovery of new URLs is slower. Publish a sitemap of live canonicals.
Pretty new paths with no redirects from old paths. Map first, then launch.
A thinner redesign can drop the unique job of a URL. Preserve or relocate that content.
Generic titles on every template. Migrate working titles where they still match the page.
Product or article markup disappearing can affect how results are understood. Re-validate where it is appropriate.
Tags pointing at old or redirected URLs. Keep annotations on live canonicals.
Passwords, noindex, or Disallow copied from staging. Treat production as a separate config.
Coverage spikes or drops after launch. Compare indexed counts and important URLs against the baseline.
PROCESS
I work as an SEO professional on the site in front of me. No invented client counts, rankings, or case-study results.
Step 1
Crawl, Search Console, important landing pages, and technical access before anything is replaced.
Step 2
Record traffic, coverage, and key URLs so post-launch comparison is possible.
Step 3
One relevant destination per important old URL.
Step 4
Templates, navigation, and whether high-value pages still exist.
Step 5
Canonicals, robots, sitemap, indexability, and rendering on the new stack.
Step 6
Test hops, loops, and destinations before DNS or go-live.
Step 7
Redirects live, indexable pages, Search Console and analytics on the right host.
Step 8
Coverage, clicks, errors, and important landing pages against the baseline. Outcomes are not guaranteed.
AUDIENCE
MODERN SEARCH
Migrations should preserve the technical and content foundations that help search systems understand the site. There is no required “AI SEO migration hack” or llms.txt file. Strong technical SEO and useful, continuous content remain the foundation across traditional results and AI-assisted experiences.
AI SEO, AEO, and GEO complement those fundamentals. They are not shortcuts around redirects and indexability.
MEASUREMENT
Temporary fluctuations can occur. The goal is to find and fix avoidable technical and content problems quickly. No recovery percentages are invented here.
FAQ
Direct answers about redirects, CMS changes, domains, monitoring, and launch checks — without guaranteed rankings or traffic.
It is the work of planning, mapping, testing, and monitoring so a redesign, CMS change, domain move, or URL restructure does not unnecessarily drop crawl, index, or relevant visibility. It is risk reduction, not a promise that rankings stay the same.
URLs change without redirects, content is removed, pages are noindexed, canonicals point at the wrong host, internal links break, or tracking changes. Demand and competition can also move at the same time. Diagnosis compares the baseline with what actually launched.
If the site already earns useful organic traffic, capturing URLs, landing pages, and technical settings before launch is cheaper than repairing 404s afterwards. A purely visual change with no URL or content change still needs a check that templates did not drop headings, links, or indexability.
They should usually redirect to the closest relevant new URL, or return 410/404 if the content is genuinely gone. Leaving them as unexplained 404s wastes existing links and bookmarks.
When a URL has a lasting replacement, a permanent redirect to the right destination is usually appropriate. Redirecting everything to the homepage is usually a poor strategy. Chains and loops should be avoided.
The CMS is not automatically the problem. URL formats, robots, rendering, templates, and how content is output often change with the platform. Those implementation details need review.
Yes. Signals have to be recrawled on a new host. Careful redirects, Search Console, and internal links reduce avoidable risk. Rankings are not guaranteed to stay the same.
At least through recrawl and a few reporting cycles in Search Console — often weeks to months depending on site size. There is no fixed calendar that fits every site. Watch coverage, redirects, and important landing pages against the baseline.
Redirects live, important URLs 200 and indexable, no staging noindex, canonicals on the live host, sitemap submitted, analytics firing, and a crawl for 404s on old and new paths.
NEXT STEP
Before your new website goes live, make sure your SEO foundations, URLs, redirects, content, and technical signals are ready for the move.