SEO migration services for sites that cannot lose traffic
Most migrations that go wrong were signed off as fine. The redirect file was written in launch week, nobody crawled staging, and the drop showed up three weeks later when it was expensive to unpick. We plan migrations from ten weeks out and stay through the recovery window.
Tell us about your migration
We come back within two working days with the risks we can see from outside, and what we would want in place before launch day.
TRUSTED BY GROWTH LEADERS
150+ Reviews
150+ Reviews
150+ Reviews
What SEO migration services protect
Your rankings are not stored on your website. They are attached to URLs, and to the years of links, internal signals and crawl history sitting behind those URLs. A migration changes the URLs. Everything else is a question of whether you carried that history across cleanly or dropped it on the floor.
That is the whole job. Our SEO migration services exist to make sure every URL that earns something today has a destination tomorrow, that the new templates say the same things to a crawler that the old ones did, and that somebody is watching the logs on launch night rather than reading about the problem in next month’s report.
We work with your build team, your agency or your platform partner. We are not there to slow the project down. We are there so nobody has to explain a 40% traffic drop to the board in quarter three.
What is an SEO migration
An SEO migration is the work of preserving search visibility while something structural about your website changes. The change might be the platform, the domain, the URL pattern, the hosting, the front-end framework, or the number of sites you run. If a URL changes, or the way a page is built and served changes, you are doing a migration whether or not anyone called it one.
The most common mistake is scope. Teams assume a migration means a domain change. In practice a design rebuild that keeps every URL identical can still cost you a third of your traffic, because the new front end renders content client-side, or the H1s were replaced with styled divs, or the internal links moved into a JavaScript menu that Googlebot never expands.
The second most common mistake is timing. A migration plan that starts when the build is finished is not a plan. It is triage. Redirect mapping, content parity checks and template review have to happen while the new site is still cheap to change.
Types of website migration SEO services
Each of these breaks in a different way. The plan is not interchangeable, and an agency that runs the same checklist for all of them will miss things. Our website migration SEO services are scoped to the kind of move you are actually making.
Replatforming to a new CMS
Shopify, WooCommerce, Magento, Salesforce Commerce, AEM, Contentful, or a headless build. The risk is that the new platform generates URLs, metadata and pagination its own way, and defaults quietly overwrite ten years of decisions.
Domain change and rebrand
The highest-stakes version, because everything moves at once and there is no partial rollback. Needs Search Console change of address, a complete one-to-one redirect map and outreach to update your most valuable inbound links.
URL structure change
Often done for good reasons, and often done without checking which old URLs actually earn traffic. Chain redirects, orphaned pages and internal links still pointing at the old paths are the usual damage.
Merging two websites
Acquisitions and multi-brand cleanups. Two pages that both rank now have to become one, and choosing the wrong survivor throws away the stronger link profile. This needs a page-by-page decision, not a bulk rule.
Subdomain to subfolder move
Usually a blog or help centre moving onto the main domain. The upside is real, but the transfer of authority is gradual and the interim dip is normal. Knowing that in advance stops a panic rollback in week two.
Front-end rebuild
The one everyone underestimates. Client-side rendering, lazy-loaded content, headings turned into styled divs, navigation locked inside a script. The URLs survive and the rankings do not.
Not sure which migration you are doing
Send us the plan. We will tell you which risks apply to your build and which ones you can safely ignore.
Why sites lose traffic without site migration SEO
Five things cause most of the damage we get called in to repair. None of them are exotic. All of them are cheap to prevent and expensive to fix afterwards.
Redirect map built from the sitemap
Your XML sitemap does not contain every URL that earns traffic or holds links. Old campaign pages, retired products with strong backlinks, PDFs and paginated URLs all sit outside it. Building a map from the sitemap alone routinely misses a fifth of what matters.
- Merge crawl, Search Console, analytics, log files and backlink data
- Every URL with traffic, links or impressions gets a destination
- One-to-one where possible, never a bulk redirect to the homepage
No content parity check
New templates often ship with shorter copy, missing FAQ blocks, dropped schema or specifications moved behind a tab that renders on click. The page looks better and says less. Search engines notice the second part.
- Field-level comparison of old versus new on a sample of every template
- Word count, headings, schema, internal links and images all checked
- Gaps raised as build tickets before launch, not after
Staging never crawled
Staging is usually behind a password or a blanket noindex, so nobody crawls it properly. Then the noindex ships to production, or the robots.txt disallow does, and the site quietly disappears from the index over the following fortnight.
- Whitelisted crawl access to staging as a condition of the engagement
- Full pre-launch crawl with a diff against the live site
- Robots and meta directives verified within minutes of go-live
No owner on launch night
Launches happen on a Friday evening, the developers go home, and the first crawl of the new site happens on Monday. Two days of 404s and redirect loops is enough to start losing index coverage on a large site.
- A named person on the launch call, live crawling as pages go up
- Redirect spot-checks against the top thousand URLs immediately
- An agreed rollback trigger and who is allowed to pull it
The dip was misread
Almost every migration dips. The question is whether it is the normal reprocessing dip or a real problem, and teams that cannot tell the difference either panic and revert a good migration or wait patiently through a broken one.
- Baseline metrics captured before launch so comparison is honest
- Daily indexation and coverage monitoring for the first eight weeks
- A clear read on whether this is settling or breaking, in writing
What our SEO migration services include
Nine workstreams across the pre-launch, launch and recovery phases. On a smaller site some of these take a day. On a large catalogue they take weeks.
Baseline audit and inventory
A full crawl plus Search Console, analytics, log files and backlink data, so we know exactly what you have to lose before anything moves. This baseline is what every later comparison is measured against.
URL mapping and redirect strategy
Every valuable old URL mapped to a specific new one, delivered as a file your developers can implement directly. Rules where a pattern genuinely applies, manual decisions where it does not.
Template and content parity review
Old versus new compared field by field across every template type. Headings, copy depth, schema, internal links, canonical tags, images and alt text. Anything that shrank gets flagged and ticketed.
Rendering and crawlability testing
How the new build actually renders for a crawler, not how it looks in a browser. JavaScript dependencies, lazy loading, navigation, pagination and any content that only appears after interaction.
Structured data carry-over
Product, Article, FAQ, Breadcrumb, Organisation and review markup rebuilt on the new templates and validated. This is also what keeps you readable to AI systems after the move.
Hreflang and international setup
Language and region tagging rebuilt correctly, with self-referencing canonicals and return tags checked. Broken hreflang is one of the easiest ways to lose several markets at once during a move.
Launch day cover
A named person on the go-live call, crawling as pages come up, spot-checking redirects against your highest-value URLs and confirming robots, canonicals and sitemaps within the first hour.
Eight-week recovery monitoring
Daily indexation, coverage and ranking tracking against the pre-launch baseline, with a weekly written read on whether the site is settling or breaking, and what we are fixing this week.
AI citation continuity
Assistants cache and cite specific URLs. We track your citation footprint before and after the move in Aham37 and make sure the pages models were quoting still resolve to equivalent content.
Our SEO migration checklist
This is the short version of what we actually work through. You are welcome to hand it to whoever is running your build, including another agency.
Before launch
- Full crawl of the current site, saved as the baseline
- Export Search Console queries and pages for the last 16 months
- Pull backlink data and identify the URLs holding the most equity
- Rank and traffic snapshot for your top thousand pages
- One-to-one redirect map covering every URL that earns anything
- Crawl staging and diff it against the live baseline
- Template-level parity check on copy, headings and schema
- Rendering test on the production build, not a local one
- Robots.txt, meta robots and canonical tags reviewed line by line
- XML sitemaps regenerated for the new structure
- Analytics and tag manager ported and tested on staging
- Rollback trigger agreed, with a named decision maker
Launch and after
- Live crawl during deployment, not the morning after
- Redirect spot-checks on the highest-value URLs within the hour
- Confirm the staging noindex did not ship to production
- Submit new sitemaps and request indexing on priority pages
- Search Console change of address, if the domain moved
- Server log review for crawl errors in the first 48 hours
- Fix redirect chains and loops as they surface, daily at first
- Update internal links still pointing at old paths
- Outreach to update your most valuable inbound links
- Weekly indexation and coverage report against the baseline
- Re-check structured data and AI citation footprint
- Formal read at week eight on where recovery actually stands
Want this SEO migration checklist on your build
We will run the baseline audit first and tell you honestly whether you need us for the whole project or just launch week.
How our SEO migration company works
Six phases anchored to your launch date. The earlier we start, the more of this is prevention rather than repair.
Baseline and access
Crawl the current site, pull Search Console, analytics, logs and backlinks, and agree access to staging. We meet your developers and find out what is already locked down in the build.
Requirements into the build
Our technical requirements go into your backlog while the new site is still cheap to change. URL patterns, heading structure, schema, pagination and rendering approach get agreed now, not argued about later.
Redirect map delivered
The full mapping file, with rules where a pattern fits and manual decisions where it does not. Your team implements it, and we test the implementation rather than assuming it worked.
Staging crawl and sign-off
Full crawl of staging diffed against the live baseline. Parity gaps, rendering problems and directive errors get raised as blocking or non-blocking, so the launch decision is made on evidence.
Go-live cover
Someone from our team is on the deployment call, crawling as it happens, checking redirects and directives in real time, with an agreed rollback trigger already written down.
Recovery and reporting
Daily monitoring, weekly written reads against the baseline, and continuous cleanup of chains, orphans and internal links. We stay until performance has settled, not until launch week ends.
Domain migration SEO explained
A domain move is the only migration where you cannot hedge. Every URL changes at once, there is no gradual rollout, and the authority your old domain built over a decade has to be handed over deliberately.
Redirects have to be one-to-one and permanent. A blanket redirect of everything to the new homepage is the single most common cause of a catastrophic domain move. Google treats it as a soft 404 at scale and passes almost nothing. Every page needs its own equivalent.
Keep the old domain registered and redirecting for years, not months. Links and citations pointing at the old domain will keep arriving long after launch. Letting the registration lapse throws away everything you just transferred, and we have seen this happen at the two-year mark more than once.
Search Console change of address is a signal, not a switch. Submit it, but do not treat it as the migration. It helps Google understand intent, and it does nothing if the redirects underneath are wrong.
Your brand SERP has to be rebuilt separately. Knowledge panel, social profiles, directory listings, review platforms and Wikipedia-style references all still name the old brand or domain. Domain migration SEO includes chasing those down, and it takes months of unglamorous outreach.
Expect a dip. On a well-executed domain move, four to eight weeks of instability is normal and recovery to previous levels typically lands somewhere between two and four months. Anyone telling you a domain change carries no risk has either not done one or is not telling you the whole picture.
opositive.io/services/technical-seoopositive.io/blog
SEO website migration services for AI search
Assistants cite specific URLs. When those URLs change and nobody thinks about it, your brand quietly falls out of answers it used to appear in, and no ranking report will show you that happening. Our SEO website migration services treat citation continuity as part of the standard scope.
- 1
We record your citation footprint
Before launch we capture which of your pages are being cited across ChatGPT, Gemini, Perplexity and AI Overviews for your priority prompts, using Aham37, our own visibility tracker.
- 2
Cited URLs get priority in the redirect map
A page that models quote is worth more than its raw traffic suggests. Those URLs get one-to-one destinations with equivalent content, never a redirect to a category page.
- 3
We rebuild the structure models use
Clear definitions, direct answers near the top, comparison tables and valid structured data all have to survive the new templates. Design rebuilds are where these usually get lost.
- 4
We re-measure after the move
Citation share is checked again at weeks two, four and eight. If a prompt set has dropped you, we can see it and work on it rather than discovering it a quarter later.
Us vs a typical SEO migration agency
Not a claim that everyone else is careless. These are the specific choices we made, including where they cost us.
| What you are comparing | Typical agency scope | Your build partner | opositive |
|---|---|---|---|
| When they get involved | Once the build is close to done | From the start, but SEO is not their job | Ten weeks out, with requirements in your backlog |
| Redirect map source | Sitemap export | Whatever the CMS can generate | Crawl, Search Console, analytics, logs and backlinks merged |
| Staging access | Often never granted | Full access, no SEO crawl | Crawl access is a condition of the engagement |
| Launch night | Available by email | Focused on functionality | Named person on the call, crawling live |
| After launch | A report at day 30 | Bug fixes only | Daily monitoring and weekly written reads for eight weeks |
| Where we are weaker | Cheaper, faster to book | They know your codebase better than we ever will | We will refuse a launch date we think is unsafe, and say so in writing |
Already migrated and traffic dropped
We take on recovery work too. Send us the launch date and what changed, and we will tell you what is recoverable.
How we lower website migration SEO risk
Six working rules. They exist because each one comes from a migration that went badly somewhere before we adopted it.
No launch without a staging crawl
If we cannot crawl staging, we cannot sign off. This has held up launches by a week and it has also caught a global noindex that would have taken the site out of the index entirely.
Written rollback trigger
Before launch we agree what level of breakage means reverting and who is allowed to make that call. Deciding this at two in the morning with everyone tired is how bad calls happen.
Baselines saved before launch
Crawls, rankings, coverage and citation data are all archived before anything changes. Without a baseline, arguments about whether the migration hurt become a matter of opinion.
One-to-one redirects only
Nothing valuable gets redirected to the homepage or a generic category. If a page has no real equivalent we say so and decide deliberately, rather than hiding it inside a catch-all rule.
Phased launches on large sites
Where the platform allows it, we move a section first, watch it for two weeks, then move the rest. Slower, and it turns a potential site-wide incident into a contained one.
Documentation you keep
The redirect map, baseline exports, parity findings and decision log live in your systems. If you change agency next year, none of it walks out of the door with us.
Platforms and sectors we migrate
We have run search programmes across 40+ industries. These are the environments where migration work comes up most often.
Why choose our SEO migration agency
Six reasons clients have given us, including the one that occasionally loses us the project.
Honest expectations in writing
Almost every migration dips before it recovers, and we say that at the proposal stage rather than after launch. We would rather set honest expectations and keep your trust than over-promise and lose it.
Built for AI search
We are an AI-first agency with our own tracker, Aham37. Citation continuity through a migration is a standard part of scope, not something we introduce as an upsell afterwards.
We work with your build team
Requirements go into your backlog in your format, with reasons attached. Developers push back far less when the ticket explains why the pattern matters rather than just asserting it.
We stay through the recovery window
Eight weeks of monitoring after go-live is included, not billed as a new engagement. Most of the damage from a bad migration is fixable if someone catches it in the first fortnight.
We take on migration rescues
If you have already migrated and traffic fell off, we will audit what happened and tell you what is recoverable and what is not. Sometimes the honest answer is that the damage is partly permanent.
We will tell you not to launch
If staging is not ready and the date is arbitrary, we will say so in writing and recommend moving it. That conversation is uncomfortable and it has saved clients more traffic than any other single thing we do.
An award-winning WordPress SEO company
Recognised by industry bodies and rating platforms, and founded by IIT-IIM innovators.
Our SEO migration results
Averages across our client base rather than one flattering example. Migration outcomes depend heavily on how early we were brought in.
Non-blog clicks for a co-living brand after technical SEO and local search work.
View case study → ECOMMERCE+54.2%Organic users for a UAE racquet sports ecommerce brand following structural catalogue work.
View case study → TRAVEL+33.4%Growth in keywords appearing in AI Overviews for a luxury villa rental brand.
View case study → EDTECH4xIncrease in AI citations for a data analytics education brand.
View case study →What our clients say
Real words from founders and marketers we’ve worked with.
“Within a few months, our wellness brand started showing up more often in AI recommendations. Opositive helped us build authority, improve citations, and get noticed where customers are searching today.”
Andrea Nerep | Founder, The Petzbe App
“Opositive understood how property buyers search today. Their GEO strategy helped us reach more qualified buyers and improve our visibility across AI platforms.”
Tony Foster | Founder, Foster Funeral Direction
“Most agencies focus on rankings. Opositive helped us build visibility across the AI platforms our customers actually use.”
Ana Velez | Founder, WOAHCO
What SEO migration can and cannot do
The version we give clients before they sign, because a migration is one of the few projects where a bad surprise is genuinely expensive.
What it can do
- Carry the great majority of your rankings across a well-planned move
- Shorten the dip and make recovery predictable rather than uncertain
- Catch build decisions that would have cost you traffic, before launch
- Turn a replatform into a chance to remove years of accumulated waste
- Keep your pages resolving for the AI assistants that were citing them
- Recover a meaningful share of traffic after a migration already went wrong
- Give you a documented baseline so the debate afterwards is factual
What it cannot do
- Guarantee zero traffic loss, on any migration, ever
- Prevent the normal reprocessing dip on a large site
- Fix a launch we were brought into during launch week
- Recover equity from pages your team decided to delete outright
- Rescue rankings for content that was cut from the new site
- Override a platform limitation your engineering team will not change
- Make a slower, thinner new site rank better than the old one
How to choose the best SEO migration company
Migration pitches are hard to compare, because everybody shows you a process diagram with the same five boxes. These five questions separate the field, and you can ask them in a first call.
1. How do you build a redirect map? If the answer starts and ends with the XML sitemap, keep looking. You want to hear crawl data, Search Console, analytics, server logs and backlink data merged together.
2. Will you need access to staging, and what happens if you do not get it? The right answer is that crawl access to staging is a requirement, and that without it they cannot sign off the launch. An agency happy to work blind is telling you something.
3. Who is on the call on launch night? Ask for a role and a name. “We will be reachable” is not cover.
4. How long do you stay after go-live? Most damage surfaces in the first two weeks and is fixable if someone is watching. A scope that ends at launch leaves you alone for exactly the period that matters most.
5. Have you ever told a client to delay a launch? If nobody has ever said no to a date, they are not doing the sign-off part of the job.
Whoever you pick as the best SEO migration company for this project, get the answers in writing. A migration is one of the few pieces of SEO work where the cost of getting it wrong lands all at once.
Put us through those five questions
Bring your launch date and your build partner to the first call. We will answer in order, including where we would say no.
SEO migration services FAQs
SEO migration services are the planning, testing and monitoring work that preserves your search visibility when something structural about your website changes. That includes a platform move, a domain change, a URL restructure, a site merger or a front-end rebuild. The core deliverables are a baseline audit, a one-to-one redirect map, a template parity review, rendering and crawl testing on staging, launch day cover, and monitoring through the recovery period.
On a well-planned move you should expect a temporary dip while search engines recrawl and reprocess the site, typically two to six weeks, with most sites returning to previous levels within one to three months. On a domain change the window is usually longer. Large or badly planned migrations can lose a great deal more and take much longer, sometimes not recovering fully. Nobody can honestly promise zero loss, and an agency that does is guessing.
Ideally eight to twelve weeks before launch, while the new build is still cheap to change. That window lets technical requirements go into the backlog rather than becoming post-launch fixes. We can work with shorter notice and often do, but from about two weeks out the work shifts from prevention to damage limitation, and the outcome is measurably worse.
Yes. Recovery work starts with reconstructing what the old site looked like using archived crawls, Search Console history and third-party index data, then finding which URLs lost their destination and which pages lost content in the move. Much of it is usually recoverable if we get to it within a few months. Pages that were deleted outright, and equity from links that have since been removed, generally are not.
We work with them. Your build team or platform partner owns the implementation and we supply the requirements, the redirect map, the testing and the sign-off. We write tickets in your tracker with reasons attached, and we join the calls where launch decisions get made. On projects where there is no in-house technical lead we can coordinate directly with the platform vendor.
The short version is on this page. It splits into pre-launch work such as baseline crawls, Search Console and backlink exports, the redirect map, staging crawls, parity checks, rendering tests and directive reviews, and post-launch work such as live crawling during deployment, redirect spot-checks, sitemap submission, log review, chain cleanup, internal link updates and eight weeks of monitoring against the baseline. You are welcome to use it with another agency.
In SEO terms, usually yes. If the templates, rendering method or navigation change, the way search engines see your pages changes even though the addresses did not. Headings converted to styled divs, copy shortened for a cleaner look, content moved behind tabs that render on click, and menus locked inside JavaScript all cost visibility. This is the most commonly skipped case and one of the most common reasons we get called for recovery work.
Assistants cite specific URLs, and they also rely heavily on third-party sources that name your old domain. When those URLs move, you can drop out of answers you previously appeared in even where your rankings hold up. We capture your citation footprint in Aham37 before launch, prioritise cited URLs in the redirect map, make sure the structure models rely on survives the new templates, and re-measure at weeks two, four and eight.
Ask how they build the redirect map, whether staging crawl access is a requirement, who will be on the launch call by name, how long they stay after go-live, and whether they have ever recommended delaying a launch. Vague answers on staging access and on post-launch scope are the two most reliable warning signs, because both are where the real work sits.
No, and nobody can. What we commit to is a documented baseline, a complete redirect map, staging sign-off based on evidence, someone on the call at launch, and honest weekly reporting through recovery. If something goes wrong you will hear it from us before you see it in your own dashboard.
Wrap in FAQPage schema on the live page.
SEO migration guides
Ecommerce category page SEO
What category templates need to carry across a replatform, and what usually gets dropped.
Schema markup for GEO and AEO
Which markup types matter, and why rebuilding them properly protects AI visibility.
LLM visibility vs traditional SEO
Why citation loss after a move will not show up in any ranking report you already run.
Talk to our SEO migration company
Send us your current site and your launch date. We will crawl what you have, tell you which risks apply to your specific build, and be straight with you about whether the timeline is safe. If you have already launched and traffic fell, send that instead.
