A new website. A considered move.
SEO Migration Services
Bring your search foundations into the next version.
Changing your domain, CMS, or site design? We help SaaS and digital-product teams turn the move into a clear plan for pages, developers, and launch-day decisions.
- 01
Before the move
Inventory, map, and test.
- 02
At launch
Check the live journey.
- 03
After the move
Monitor, resolve, and hand over.
Start with what is changing
Different moves need different checks.
Domain or brand change
Carry useful pages to their new addresses. Coordinate redirects, domain ownership, and the search-property transition.
CMS or platform migration
Compare the old and new templates, content, metadata, and conversion paths. Platform defaults should not quietly change the plan.
Redesign or URL restructuring
Decide which pages stay, move, combine, or retire before development locks in the new structure.
A move that has already launched
Start with the release history and affected pages. Establish whether the issue is access, content, measurement, or search visibility.
If only the hosting changes and every public URL stays the same, the work is mainly infrastructure and live-site validation. A URL redirect plan should follow actual address changes.
Inside the delivery
Every old URL needs a decision.
Illustrative mapping for a fictional SaaS website. These are example decisions and expected checks, not a client migration or measured results.
Move
301 → 200Current path
/features/team-plannerPlanned destination
/product/team-planningSame product task, new address. Check the final page still explains the feature and reaches the demo.
Keep
200Current path
/pricingPlanned destination
/pricingThe address stays. Compare plans, metadata, and the signup flow across the old and new templates.
Combine
301 → 200Current path
/guides/team-calendarPlanned destination
/guides/project-planningRedirect only if the destination genuinely incorporates the useful calendar guidance. Record the content review.
Retire
404 / 410Current path
/events/2022-demoPlanned destination
No replacementAn obsolete event with no useful equivalent. Remove internal links; do not send the visitor to an unrelated homepage.
What your team receives
Decisions, tasks, and a record of what passed.
Baseline and priority pages
A dated inventory joining current URLs, content purpose, search data, leads where available, and known dependencies. Agree what needs the closest review.
URL map and developer tasks
Destination decisions, redirect requirements, content changes, named implementation owners, and test criteria for the affected templates and pages.
Staging and live release checks
An issue list with severity and evidence. Recheck the live site after deployment, including key pages, navigation, forms, and agreed tracking events.
Post-launch review and handover
Compare affected page groups with the baseline, investigate changes, retest fixes, and hand over unresolved items with an owner and next check date.
The launch decision
A checklist should change what happens next.
Agree blockers before release. If a priority route fails, the release owner needs the evidence, the fix owner, and a clear retest—not just a green percentage.
Pricing page inherits staging noindex
- Expected
- The approved production pricing page is indexable.
- Observed in this example
- HTTP 200 · X-Robots-Tag: noindex
- Action and owner
- Developer fixes the production header rule. SEO checks the response and rendered page again.
- Release decision
- Hold this release until the agreed blocking condition is resolved. Record the retest result and time.
Work alongside your team
Clear ownership through the move.
Meridian · SEO
Prioritize the pages, specify SEO requirements, review staging, verify agreed checks, and investigate post-launch changes.
Your developer or platform team
Implement templates, redirect rules, hosting changes, and fixes. Own the deployment and the technical recovery procedure.
Your project owner
Confirm content decisions and release timing, arrange access, approve the launch decision, and keep customer-facing teams informed.
Scope, cost, and support
Before you book.
When should we involve an SEO migration consultant?
Before the new URL structure and templates are finalized. That gives the SEO and development teams time to agree decisions and test them. If the launch is already scheduled, share what is fixed and what can still change so we can define a realistic scope.
What affects the cost of website migration SEO services?
URL and template counts, the kinds of changes, language versions, data access, staging readiness, implementation ownership, and the agreed review period. A redirect review and a coordinated domain-and-CMS move are different scopes. We define deliverables and support dates before quoting.
Do you rebuild the website or move the hosting?
The core scope is SEO planning, checks, and coordination. Hosting, DNS, platform development, and content production need named owners. Any Meridian implementation work is listed explicitly in the proposal; it is not implied by an audit or a checklist.
Can you guarantee no traffic loss?
No. Search visibility can fluctuate as a move is processed. We agree the checks, baseline, escalation route, and review scope we can deliver. A search recovery date or a growth percentage would need evidence we cannot promise in advance.
How long does support continue after launch?
The proposal sets a monitoring window, checkpoints, response coverage, and a handover date. Open issues are documented with an owner. Additional releases or extended monitoring are agreed separately, rather than leaving the project open indefinitely.
What if traffic has already dropped?
Compare when and where the change started, then inspect the affected URLs and tracking. Share the old URL list, release notes, and available search data. A focused technical SEO audit may be the right starting point before a wider recovery scope is agreed.
Start with your move
What is changing, and when?
Bring your website, migration type, current stage, and intended launch date. In a 15-minute introduction, we discuss fit, the information needed, and the next scoping step. The full migration review is project work.
Keep Exploring SEO Services
Explore adjacent capabilities in the same service family, or return to the parent page for the complete program.
