Ahrefs
Semrush
Search Console
Redesigning your marketing site, moving to a new CMS or changing domain? We plan the SEO side of the move, map every URL that matters, test the new site before launch and monitor it afterwards, so avoidable mistakes don’t cost you rankings, sign ups or demos.
Migrations we support
Do you need migration support?
Not every change needs a migration specialist. Tick what applies to your project for a rough idea of how much SEO support it needs. Nothing is saved or sent.
Tick what applies to your migration.
Already launched and lost traffic? See how recovery works.
Migration types
The risk depends on how much changes at once, whether URLs change, how the new site is built and how much search traffic is at stake. These are the situations we help with most.
New design and templates, with URLs kept as they are.
Watch out forLost content, changed headings and internal links, and template or rendering changes.The site moves to a new CMS or framework, often with new templates.
Watch out forURL patterns change by accident, and pages rendered in the browser may hide content from crawlers.The whole site moves to a new domain, often after a rebrand.
Watch out forEvery URL changes, so redirects, a change of address in Search Console and backlink continuity all matter.Folders and URL patterns change, for example to a new product or solution structure.
Watch out forRedirect mapping at scale, plus updating canonicals, sitemaps and internal links.Subdomains, blogs or several sites merge into one.
Watch out forChoosing which pages survive, avoiding duplicates and redirecting to the closest match.Language or country sections move, or new ones are added.
Watch out forHreflang annotations, regional URLs and language versions competing with each other.A blog, help centre or resource library moves to a new system.
Watch out forThousands of URLs, media files and internal links moving at once.A product or company name changes, often alongside a new domain.
Watch out forCombining a domain move with content changes, which makes it harder to see what caused any drop.A migration has already happened and organic traffic has fallen.
Watch out forFinding what changed, fixing it quickly and setting realistic expectations.Migration risks
Most migration losses come from a handful of avoidable mistakes. These are the ones we look for first.
The technical side, simply
Many migration problems come from mixing these up. Here’s what each one does, and what it doesn’t.
Send visitors and search engines from an old URL to its new one. When a URL changes permanently, a server side 301 or 308 redirect is the right tool. Keep redirects in place for as long as possible, and generally for at least a year.
Tell search engines which version of similar pages you prefer. They don’t move anyone anywhere, so they never replace a redirect when a page has moved.
List the URLs you want found. A new sitemap helps search engines discover the new site faster, but it doesn’t guarantee indexing or rankings.
A page can load perfectly and still not be indexed, for example because of a noindex tag, a blocked crawl or a canonical pointing elsewhere. After launch, we check each stage for your priority pages.
How it works
The earlier SEO is involved, the cheaper problems are to fix. Ideally we start before designs and URLs are final, but we can join at any stage.
What’s changing, your goals and launch date, plus a saved baseline of rankings, traffic and conversions.
Every indexable URL from crawls, sitemaps, analytics and backlink data, ranked by traffic, links and conversions.
What the proposed URLs, templates and platform mean for search, and what has to be protected.
Old to new URL mapping, plus requirements for templates, metadata, canonicals, sitemaps and tracking.
Crawl the staging site, test redirect rules on samples, check key templates and confirm staging is hidden from search.
Priority pages, redirects, status codes, indexability, robots rules and sitemaps checked as soon as the site is live.
Recrawls, Search Console coverage, organic landing pages, rankings and conversions watched for the agreed period.
Issues prioritised by impact, fixes checked, and a summary of where things stand.
Working with your team
SEO migration work is mostly planning, specifying and testing. Implementation usually sits with whoever builds the site. Because we also build SaaS websites, our developers can implement redirects and fixes too, when that’s agreed.
Post migration recovery
Some movement after a migration is normal while search engines process the changes. A sharp or lasting drop usually has a cause we can find. This is how we investigate.
Old URLs that brought traffic are matched against what exists now.
Missing, chained, looping or irrelevant redirects are found.
Noindex tags, robots rules, canonicals and sitemaps on the live site.
Removed content, new templates and lost internal links.
Tracking gaps or changed setups that make the drop look worse, or better, than it is.
The pages that matter most to sign ups and demos come first.
What to expect. Fixing technical problems often helps once search engines recrawl the affected pages. Losses caused by removed content or weaker pages may need new work, and how fast rankings return depends on the site and the search engine, so we don’t promise a recovery date.
Get Help With a Traffic DropScope and expectations
No two migrations are the same size, so we don’t sell fixed packages. You get a written scope, timeline and price before work starts.
Our work
One of these clients moved off a website builder onto a new platform built by our team. Client names are withheld, and we’re happy to talk through the details on a call.
Case 01
This client had outgrown their website builder. We moved them to a new SaaS platform with an admin dashboard, automated emails, a new website and SEO.
50%
faster page loads
+40%
member engagement
30%
less admin work
Case 02
We designed and built the product and website, then grew it with advanced SEO, including AEO and GEO, and Google Ads.
~20,000
organic visits a month, from a new domain
+38%
quiz completion
1.8s
average page load
Case 03
We took an HR platform from idea to launch, with product design, development and a new website, then SEO to bring in users.
~11,000
organic visits a month, from search
+45%
trial signups
40%
less HR admin time
Testimonials
Client names are withheld. Each quote comes from a real client and is shown with their company type only.
[Paste the client's own words here. A short, specific story about what changed after launch.]
[Paste the client's own words here. One or two plain sentences.]
[Paste the client's own words here. One or two plain sentences.]
[Paste the client's own words here. One or two plain sentences.]
Services
This page covers SEO for site migrations. These services help before and after the move.
SEO for SaaS companies, from keyword strategy and technical SEO to comparison pages and reporting tied to sign ups and demos.
Clear, accurate content written for software buyers, from problem guides to feature and comparison pages.
SEO for large SaaS sites with thousands of pages, several teams and complex technical setups.
Answer Engine Optimisation helps your product be understood and cited when people ask direct questions.
Generative Engine Optimisation looks at how AI assistants describe and recommend tools in your category.
FAQ
Not always. Developers make sure the new site works. SEO support makes sure search engines can follow the move, which needs a redirect map, checks on indexing rules and monitoring. If your team already covers those, a short review may be enough.
Yes, if URLs, content, headings, internal links or templates change. A same domain redesign is usually lower risk than a domain move, but pages that bring in traffic can still lose content or be left out.
Less of it. Keeping URLs removes the biggest risk. It’s still worth checking that content, internal links, metadata, rendering and tracking survive the new templates, which a focused pre launch review can cover.
Most of them, if we can crawl the staging site. Redirect rules, templates, indexing rules and tracking can all be tested before anything goes live.
We start with a recovery audit that compares the old and new sites, checks redirects and indexing, and looks at what content changed. Technical fixes often help once pages are recrawled. Losses from removed content may need new work.
Search Console and analytics for the current site, a list or crawl of the old URLs, access to the staging site, the planned URL structure and a developer contact. For a domain move, Search Console access for the new site too.
Yes, our developers can implement redirects and fixes when that’s agreed and we have access to your site or hosting. Otherwise we hand your team a redirect specification and test their work.
For as long as possible. Google advises keeping them for at least a year, and many sites keep them permanently because old links keep sending visitors.
Some short term movement is common while search engines recrawl and reprocess the site. Good planning reduces avoidable losses, but nobody can promise rankings won’t change.
Yes. Monitoring covers indexing, redirects, organic landing pages, rankings and conversions for the period we agree, with fixes prioritised by impact.
It depends on the number of URLs, how much changes, the platform and when we’re brought in. You get a written scope, timeline and price before work starts.
Tell us what’s changing, when you plan to launch and how much of your growth comes from search. We’ll tell you how much SEO support the migration really needs.
Prefer email? Write to hello@saasassistant.com
Figma 
Google Ads 
