Key takeaways
- A website migration is any deliberate change to a site’s URL, platform, or design made to meet a business objective — and every type carries SEO risk if executed poorly.
- The biggest risk in migrations is often the most neglected: SEO. Benefits are easy to quantify; costs and risks are overlooked until disaster strikes.
- Success requires the SEO team at the table from day zero through 90 days post-launch — not brought in at the end to “check the SEO.”
- Prioritize ruthlessly: know your P0s, P1s, P2s, and P3s before the project kicks off, not when scope gets cut.
- A-grade SEO teams don’t just execute well — they communicate upward, build cross-functional trust, and bring senior leaders on the journey without surprises.
What is a website migration?
A website migration is any deliberate change to a site’s URL, platform, or design, made to meet a business objective. Every migration falls into one of two buckets: strategic or tactical.
Strategic migrations serve the business: rebranding, consolidations from mergers and acquisitions, digital transformations. Tactical migrations serve the stack: CMS changes, HTTPS upgrades, mobile-responsive redesigns, URL restructuring.
Sometimes companies migrate sites — or parts of sites — off their platform entirely because they’re shutting down or selling a line of business.
The underlying motivation is always the same: competitive advantage, better customer experience, stronger operational capabilities, and ultimately, more profit through increased revenue or reduced costs after the migration.
What migrations look like in practice
Website migrations take a handful of recognizable forms:
- Twitter.com to X.com (rebrand plus domain migration)
- A Fortune 500 retailer consolidating m.company.com and www.company.com into a single mobile-first site
- HTTP to HTTPS protocol migration
- Host migration from GoDaddy to Rocket.net
- CMS change from static pages to Contentful, WordPress, or Sitecore
- Subdomain to subfolder consolidation
- On-site search engine replacement
Each of these looks different on the surface. Under the hood, they all share the same risk: if SEO isn’t accounted for, rankings disappear.
• • •
How migrations break crawling and indexing
A migration hides its risk in the structural layer. The page can look perfect to users while broken URLs, redirects, and rendering quietly cost you rankings.
Full platform migration: a home renovation
A full platform migration changes everything at once — frontend, backend, and infrastructure — so every element has to be ported, tested, and validated together.
Think of it as a home renovation. You gut the house to the studs and rebuild the layout, plumbing, electrical, and finishes. Done right, it’s a better home — but every system has to connect. If the plumbing doesn’t reach the water main, if the electrical isn’t up to code, if the foundation shifts, you get a beautiful house that doesn’t function. Miss one connection in a migration and the whole thing fails the same way.
CMS migration: an engine swap
A CMS migration swaps the system that builds your pages, while the pages themselves stay identical to users and crawlers.
Think of it as an engine swap. Same exterior, same paint, same seats — the driver should only notice it runs better. But if the new engine isn’t wired to the transmission, fuel lines, and electronics, the car stalls. If content, URL patterns, schema, internal links, and technical signals aren’t ported over exactly from old CMS to new, it won’t matter how efficient or scalable the new system is. You will lose rankings.
Domain migration: a heart transplant
A domain or subdomain migration asks search engines to transfer all of a site’s trust, authority, and link equity to a new address.
Think of it as a heart transplant. Same person, same body, same history — but the new heart has to connect perfectly, every artery and vein and signal. One failed connection and the body rejects it. If redirects aren’t 1:1 mapped, using proper status codes and free of chains and hops, equity is lost and rankings tank. Done correctly, link signals compound and rankings climb.
• • •
Who owns a migration
Every migration starts in one of two places: top-down from C-level executives, or bottom-up from marketing, engineering, and product. Strategy-based migrations tend to come from the top, with executives driving digital transformation down to implementation teams. Tactical migrations bubble up from the bottom, with teams persuading leaders that the current stack creates bottlenecks or makes it impossible to work at scale.
Wherever the idea comes from, the bigger the organization, the more rigorous the buy-in process and the more complex the execution.
Here’s the problem: while benefits are easy to quantify and align around, the costs and risks are often overlooked or understated. Even the most expert among us often don’t know what we don’t know.
The biggest risk, neglected until disaster strikes, is SEO.
What a failed migration does to traffic
A failed migration damages SEO in three cascading stages: crawling, indexing, and ranking.
🔍 Crawling and rendering issues. Search engines can’t access or properly render the new pages. JavaScript frameworks, blocked resources, server errors — all invisible to humans, all catastrophic to bots.
📑 Indexing issues. Pages that were indexed for years suddenly disappear from the index. New pages aren’t picked up. Redirect chains confuse crawlers about which URL is canonical.
📉 Ranking issues. Even when pages are crawled and indexed, they’ve lost the signals that made them rank: link equity not transferred, content parity not maintained, technical signals broken.
The result: traffic tanks. Revenue follows.
Questions to ask before you start
Seven questions decide whether a migration succeeds or ends in a post-mortem, and each is cheaper to answer before kickoff than after:
- Who gets the credit when migrations go well?
- Who gets the blame when they don’t? (Usually: managers, engineering, agencies, PMs — rarely the executives who approved the timeline)
- When should SEO be brought into the conversation?
- What are the real project timelines — not the aspirational ones?
- What does success actually look like?
- What KPIs are we measuring before and after?
- How do we mitigate risk, or if needed, roll back changes in the event of disaster?
If these questions aren’t answered before the project starts, they’ll be answered in a post-mortem.
• • •
What the SEO lead owns
The SEO lead owns four non-negotiables in any migration: parity, 1:1 redirects, page-type validation, and upward communication.
Ensure parity at minimum. Every page on the current website must have an equivalent on the future website. Parity is the floor, not the ceiling.
301 redirects must be 1:1. The product page for Air Jordan 1s “Fresh Bred” Edition should redirect to the same page on the new site. “Better” is redirecting to the AJ1s category page. “Good” is redirecting to the Air Jordan category page. Sometimes that’s the only option because the product is discontinued. But 1:1 is always the goal.
Validate every page type. Verify every major page element. Verify all essential content is migrated. Verify navigation elements — header and footer — are intact.
Overcommunicate without being a squeaky wheel. If you’re only communicating routinely or reactively, stakeholders are losing trust in you — or at minimum, questioning whether you’re on your A-game. Always be on your A-game, especially during complex initiatives. Excellence is doing the basics really well, really consistently.
This last point was one of my biggest growth areas moving from manager to senior manager to director. You have to bring senior leaders on the journey without boring them with every detail. Fine balance to strike, but strike it you must — because nobody, especially high-performing executives, likes to be surprised.
• • •
How to prioritize when scope gets cut
Scope always gets cut, timelines compress, and resources get pulled — so prioritize by business value first, SEO value second.
Use your web analytics and Google Search Console to identify the pages with the greatest opportunity cost. If we don’t properly migrate pages X, Y, Z, what’s the expected revenue or traffic impact?
Always know your P0s, P1s, P2s, and P3s.
The P0–P3 priority framework
Every page gets one of four priority levels, set by how much revenue and traffic it puts at risk:
| Priority | Definition | Risk if Botched | Examples |
|---|---|---|---|
| P0 | Business-critical. Direct revenue/traffic impact. Non-negotiable for launch. | Catastrophic — immediate revenue loss, exec escalation, potential rollback | Homepage, top 10 revenue-driving landing pages, checkout flow, primary category pages |
| P1 | High value. Significant traffic or conversion impact. Must launch within days of go-live. | Severe — noticeable traffic drop, stakeholder concern, recovery takes weeks | Secondary category pages, top blog posts by traffic, key product listing pages |
| P2 | Medium value. Supports SEO health and user experience. Fast-follow after launch. | Moderate — ranking slippage, missed opportunities, but recoverable | Supporting content pages, schema implementation on lower-traffic templates, internal linking optimization |
| P3 | Lower value or lower risk. Nice-to-have. Can be scheduled post-launch. | Minimal — can be addressed without major impact to core metrics | Legacy pages with low traffic, cosmetic metadata updates, edge-case redirects |
How to score a page’s priority
A page’s priority rises with the cost of losing it: the greater the risk to rankings, traffic, or revenue, the closer it sits to P0.
Ask:
- If this page breaks, what’s the dollar impact?
- How many users/sessions does this page drive monthly?
- Is this page in the top 10% of organic revenue or traffic?
- Does this page support critical user journeys (checkout, lead gen, key content)?
What separates good SEO leaders from great ones?
Great SEO leaders connect every priority to a business outcome; good ones only assign it.
They don’t say: “Schema is important for SEO.”
They say: “Product schema on our top 50 PLPs is P0 because it powers rich results. Rich results increase CTR by 15-30%. These 50 pages drive $2M/month in organic revenue. Losing rich results means losing clicks, which means losing revenue. That’s why it’s non-negotiable for launch.”
The difference is connecting tactics to business outcomes — not rattling off buzzwords.
• • •
What to validate before launch
Before launch, every page type needs a parity check: the new page must give a crawler the same signals as the old one, even if it looks different.
What a parity check looks like
Here’s a parity check for a category page:
| Element | Current State | New State | Match? |
|---|---|---|---|
| URL | /shoes/air-jordan-1 | /shoes/air-jordan-1 | ✓ |
| Title Tag | Air Jordan 1 Shoes - Shop Retro & New Releases | Air Jordan 1 Shoes - Shop Retro & New Releases | ✓ |
| Meta Description | Shop Air Jordan 1 shoes. Free shipping on orders over $50. | Shop Air Jordan 1 shoes. Free shipping on orders over $50. | ✓ |
| H1 | Air Jordan 1 | Air Jordan 1 | ✓ |
| H2s | Retro High, Retro Low, Kids’ Sizes | Retro High, Retro Low, Kids’ Sizes | ✓ |
| Schema | Product + ItemList | Product + ItemList | ✓ |
| Body Content | 150 words + buying guide | 150 words + buying guide | ✓ |
| Internal Links | 24 product links, 3 related category links | 24 product links, 3 related category links | ✓ |
| Breadcrumb | Home > Shoes > Air Jordan 1 | Home > Shoes > Air Jordan 1 | ✓ |
| Images | 12 product images with alt text | 12 product images with alt text | ✓ |
| Canonical | Self-referencing | Self-referencing | ✓ |
The goal: a search engine “sees” and downloads the same page even if it looks different or is generated by a different CMS.
Run this checklist for every major page type. Automate where possible. Document everything.
• • •
Two kinds of SEO leader
A migration reveals what kind of SEO team you have. The difference isn’t skill — it’s mindset.
The A-grade SEO leader
An A-grade SEO leader treats the migration as owned risk — baselined, prioritized, and communicated upward before anything breaks.
Goals
- Constantly reminds the team and stakeholders of the SEO goals they’re responsible for
- Rigorously tracks baseline metrics (rankings, traffic, revenue) before migration begins
- Knows every page type and keyword set that drives organic performance
- Can articulate exactly what’s at stake if things go wrong
Strategy
- Demonstrates strategic acumen — understands not just what to do but why it matters to the business
- Maintains executive presence: calm, clear, confident in high-pressure meetings
- Doesn’t compromise on P0s and P1s, but negotiates P2s and P3s as fast-follows
- Thinks beyond SEO — aware of cross-functional dependencies (API gateways, database architecture)
Tactics
- Has the technical skills to run the work: massive crawls, staging validation, defect tracking
- Uses enterprise-grade tools appropriately (Botify, Screaming Frog)
- Catches issues before they reach production — proactive, not reactive
- Documents requirements thoroughly so nothing is left to memory
Implementation
- Strong rapport with implementation teams (developers, architects, QA)
- Presents a united front externally, even when debates happen internally
- “Be your own manager” mentality — every team member owns their domain
- Never assigns blame; focuses on solving problems
Controls
- Puts clear controls in place to derisk the downside and maximize the upside
- Communicates upward regularly — doesn’t wait to be asked
- Brings senior leaders on the journey without overwhelming them with details
- No surprises — especially in environments where surprises are constant
- Has contingency plans: soft launch to secondary search engine first, PPC budget to offset traffic loss, rollback readiness
The A-grade mindset: Knows they’re doing phenomenal work but still sees room to improve. Owns their gaps. Open to feedback, even when uncomfortable. When something goes wrong, asks “what did we miss?” not “who’s to blame?”
The D-grade SEO leader
A D-grade SEO leader treats the migration as someone else’s problem — unmeasured, unprioritized, and explained only after the traffic has already dropped.
Goals
- Vaguely aware of traffic numbers but can’t articulate what’s at stake
- Doesn’t track baselines rigorously — “we’ll know if it breaks”
- Can’t connect SEO metrics to business outcomes
Strategy
- Reactive, not strategic — waits to be told what to do
- Folds under pressure in meetings; either silent or defensive
- Treats every task as P0 because they can’t prioritize
- Siloed thinking — “that’s not an SEO problem”
Tactics
- Over-reliant on tools without understanding what they’re measuring
- Doesn’t validate in staging; discovers issues in production
- Documentation is sparse or nonexistent
- “We sent the requirements” = job done
Implementation
- Adversarial relationship with dev teams — “they never listen”
- Throws teammates under the bus when things go sideways
- Lone wolf mentality; doesn’t build coalition or trust
Controls
- No contingency plan; assumes everything will work
- Communicates only when asked — and then defensively
- Surprises senior leaders constantly
- No pulse on cross-functional dependencies
The D-grade mindset: Shares one thing with A-grade: doesn’t know what they don’t know. The difference is openness. D says: “No one else gets SEO. It’s Google’s fault. It’s the dev team. It’s corporate red tape.” D isn’t a failure — but D isn’t growing either. And in a migration, that gap becomes visible fast.
• • •
Golden rules: what to always do
- Use the G-STIC framework. Every stakeholder involved in pitching, planning, managing, delivering, and reporting should have full clarity on: Goals (company and department), Strategy (who we’re migrating for and the value we’re creating), Tactics (what each function must execute), Implementation (who’s responsible, deadlines, milestones), and Controls (how we verify success and communicate progress).
- Run continuous crawls in staging. Use Screaming Frog or enterprise tools like Botify. If something breaks, know about it before it hits production.
- Match every page type to parity. Every URL to every top keyword to every primary CTA to every key on-page element. Document the mapping.
- Prioritize by business value. Know your P0s, P1s, P2s, P3s before scope gets cut — not after.
- Communicate upward without being asked. Bring senior leaders on the journey. No surprises.
Silver rules: what to never do
- Do not leave the SEO team out of planning. Even if they’re annoying and talk a lot — tell them to be quiet and be a fly on the wall. Every high-level decision translates to tactical changes that impact SEO. SEO needs to be there from day zero to 90 days after launch.
- Do not wait until development is done to start SEO work. You will run into rework and cram at the last minute before the plane lands on the runway. Set SEO requirements early — not when engineering is already building.
- Do not chase every new feature. Get to parity first. You’re doing your employer a disservice if you’re pushing for enhancements while baseline functionality is broken — unless this is explicitly an SEO-driven initiative.
- Do not sleep on JavaScript. New tech means SPAs, client-side rendering, AJAX frameworks. Don’t assume crawlers will render your beautiful content. Test it.
- Do not rely only on the DOM. Also test view-source. We’re mitigating risk, not leaving crawler interpretation to Google’s guidelines or flawed algorithms.
- Do not assume development matches requirements. Smoke test everything. Stress test everything. From both human user and bot crawler perspectives.
- Do not ignore accessibility or semantic HTML. In the rush to launch on timeline, this is often deprioritized. Don’t let it be.
• • •
This is the foundation. Each migration type — platform, CMS, URL/domain — has its own deep dive coming. Subscribe to get notified when they publish.