Backbase, the engagement banking platform used by banks worldwide
weekly organic sessions to priority pages within a month
priority pages changed URLs, and all 19 were indexed after launch
indexed pages before and after the migration
Backbase sells engagement banking software to banks. Their website is enterprise scale: more than 1,300 indexed pages in three languages, serving regional markets from the Americas to Asia, moving from Craft CMS to Webflow. Ten of the 19 pages that mattered most commercially were changing URLs in the process.
At that scale the migration fear is not abstract. Every changed URL is a bet that Google will follow the redirect, transfer the signals, and index the new page before the pipeline notices anything. Half the priority set was making that bet at once.
| The move | Why it mattered |
|---|---|
| Cut the problem down to 19 pages | You cannot babysit 1,300 URLs through a launch. You can babysit 19. Everything in the monitoring plan flowed from that list: sessions, positions for 64 non-branded focus keywords, branded traffic, indexed page count. |
| Agree the success metric before launch, including its limits | Lead reporting through Salesforce was not available, so I set organic sessions to priority pages as the KPI and put the caveat in writing: a proxy, not the conversion truth I normally insist on. Nobody had to argue about what "success" meant after the fact. |
| Treat redirects as claims to verify, not tasks to tick off | After the November launch I verified every changed URL redirected correctly, watched the temporary dips consolidate onto the new URLs, and tracked indexation until all 19 priority pages were confirmed indexed. |
| Separate migration effects from seasonal ones | Branded traffic dipped after launch. Before calling it a problem, I checked previous years: the same dip starts every late October. Without that check, a seasonal curve becomes a false migration alarm and a panicked, unnecessary fix. |
On a set of pages where more than half the URLs had just changed:
There was no recovery phase, because nothing needed recovering. The one-month review moved straight to growth recommendations instead of triage.
Sessions were a proxy, and I would not accept that again without a fight. Salesforce lead reporting was not connected for this migration, so I could prove the traffic doubled but not draw the line to pipeline. On my migrations since, securing the lead-reporting connection is a pre-launch gate, not a post-launch wish. If you are migrating, get that access sorted before launch day, because you cannot reconstruct it afterwards.
Performance regressed after launch. Mobile Core Web Vitals degraded from mid-November as templates and scripts settled in, and desktop followed in early December. The migration itself was clean; the new build needed a performance pass that the launch plan should have budgeted for.
A migration exposes strategy gaps without creating them. The 64 focus keywords came through stable but scattered, with no consolidation around a cluster the business owns. That was true before the migration too. Moving platforms carried the problem across faithfully, which is exactly what a good migration does, and exactly why it is not a strategy.


lower-funnel conversions the month after launch
A 2,011-page relaunch with no dip, and lower-funnel conversions up 21%Mollie, the European payments company. I led SEO in-house.
monthly clicks on one comparison page in 8 months (13 → 290)
The same page type produced leads at three companies, then AI search started retrieving itThree B2B companies: a Dutch fintech lender, a workplace hardware company, and an event-software SaaS
weekly leads through the launch window
Leads went up during migration launch week, not downBedrijfsfitness Nederland, the Dutch corporate fitness provider