Leave WordPress without leaving your SEO behind.
I move your site to a modern stack your team can edit. Every old address is kept or redirected, and you see the full list before anything goes live.
Rankings can’t be guaranteed. I can show you every URL, redirect and tag before launch.
| What you buy | From | Usual time |
|---|---|---|
| MigrationYour site moved to a modern stack, every URL kept or redirected | €12k | 2–4 weeks |
Week one is a fixed fee of €3,000, counted toward the project. Stop at the end of it and I refund it in full. Prices excl. VAT.
The risk
The fear is losing your search traffic. It’s a fair one.
The migration nobody wants to own.
You spent years earning those rankings, and a careless move can undo them in a weekend. Old addresses stop answering, titles go missing, and the pages that brought in customers drop out of Google.
Most of that is avoidable, and all of it is checkable. Google’s own guidance says permanent redirects don’t lose PageRank, and that you should expect rankings to move around for a while during a move. So I can’t promise rankings, and neither can anyone else. What I can do is account for every address, carry over every tag, and put the list in front of you before launch.
The hardest case is changing your domain as well. Unless you need a new one, I keep the one you have.
Public benchmark
523 days
is how long it took, on average, for organic traffic to come back after a move to a new domain. In 17% of cases it had not come back after 1,000 days.
Source: Search Engine Journal (opens in a new tab), 2025. 892 domain migrations, traffic estimated by a third-party tool. That is the worst case, a change of domain. It is not a result of mine.
How I take the risk down
- Your domain stays.Unless you need a new one. A change of domain is where the long recoveries come from.
- Every address gets a decision.Kept, redirected or merged, on a list you sign before launch.
- The old site is the way back.It stays up, untouched, until the new one has passed the checklist.
- Ninety days of watching.404s, indexed pages and clicks, checked at day 1, 7, 30 and 90.
The redirect map
Every old address gets a new one.
What it isOld site 10 URLs
New site 9 URLsWhat changes
- Home/ stays at /
- Page/
about- us/ redirects to /about with a 301 - Page/
services/ redirects to /services with a 301 - Page/
services/ web- design- 2/ redirects to /services/web-design with a 301 - Category archive/
category/ news/ redirects to /blog with a 301 - Tag archive/
tag/ company- news/ redirects to /blog with a 301 - Post/
blog/ 2019/ 05/ 14/ pricing- update/ redirects to /blog/pricing-update with a 301 - Post, by ID/
?p=1432 redirects to /blog/moving-office with a 301 - File/
wp- content/ uploads/ 2021/ brochure.pdf redirects to /files/brochure.pdf with a 301 - Page/
contact- us/ redirects to /contact with a 301
- /200Same address
- /
about301Shorter address - /
services301Trailing slash dropped - /
services/ web- design301Duplicate slug cleaned up - /
blog301Two archives folded into one - /
blog/ moving- office301A real address in place of an ID - /
blog/ pricing- update301Date taken out of the address - /
contact301Shorter address - /
files/ brochure.pdf301File moved, link kept alive
10 of 10 old URLs have a destination
A sample map with made-up addresses. Yours lists every URL the crawl finds, and you sign it off before launch.
- Sheet
- M-02
- Title
- Redirect map
- Status
- Sample
The paperwork
What you see before launch, and after.
| Old URL | What it is | Visits a month | Links in | Decision |
|---|---|---|---|---|
| / | Home | 4,210 | 38 | Keep |
| / | Page | 1,120 | 9 | Redirect |
| / | Post | 640 | 14 | Redirect |
| / | File | 310 | 6 | Redirect |
| / | Post, by ID | 230 | 3 | Redirect |
| / | Archive | 85 | 0 | Merge into /blog |
| / | Landing page | 0 | 0 | Retire or keep? |
A page with no visits and no links can go. That is your call, not mine, so it is clouded until you make it.
Sample rows for a made-up site. The real one has a row for every URL the crawl finds, sorted by what it would cost to lose.
- Sheet
- M-01
- Title
- URL inventory
- Status
- Sample
Before launch
- Crawl the old site and list every URL
- Map each URL to its new address, signed off by you
- Carry over titles, descriptions, headings, canonical tags and structured data
- Test every redirect on a staging copy
- Record Core Web Vitals, so there is a before
Launch day
- Switch at a quiet hour, with the old site kept as the way back
- Submit the new sitemap to Search Console
- Open the top pages by hand, on a phone
After launch
- Catch 404s daily in week one and fix them the same day
- Compare indexed pages and clicks at day 7, 30 and 90
- Leave the redirects in place for at least a year
Cleared for launch
Every line tickedThe list I work down. You get a copy with the date each line was ticked.
- Sheet
- M-03
- Title
- Launch checklist
- Status
- Sample
Day 1
Every redirect answers. No 404 on a page that had visits.
Day 7
Indexed pages against the inventory. Errors in Search Console.
Day 30
Clicks and impressions against the same weeks before. Core Web Vitals from real visitors.
Day 90
The before-and-after report: traffic, speed, what moved and why.
No result is drawn here on purpose. The report shows yours, whatever they are.
- Sheet
- M-04
- Title
- 90-day watch
- Status
- Sample
An honest note. I don’t have a published migration case yet, so this page shows you the paperwork you’ll get in place of a logo. Week one produces the inventory and the redirect map. If they don’t convince you, stop there and I refund the week.
Two tools I’ve drawn for a move
- Concept
A control room for a site move
Rehearse the move before launch, watch every old address get tested, and decide each failure by name.
- Concept
A content mover that shows its work
Old CMS markup goes in, typed content blocks come out, and a count taken on both sides shows that no word was lost.
Concepts I drew to show how the paperwork gets made. They are not client work.
The gains
What you get for moving.
Public benchmark
8.4%
more retail conversions when a mobile site got 0.1 seconds faster.
Source: web.dev, Milliseconds make millions (opens in a new tab), 2019. 37 brand sites, a study commissioned by Google. A public benchmark. It is not a result of mine and not a promise.
What lift would cover the price, on your numbers
Two numbers and the sum appears here. Nothing is filled in for you.
8.4% is one study’s figure for retail sites that got 0.1 s faster on mobile. It is a reference, not a forecast for your site. Your numbers stay in this tab.
- Sheet
- M-05
- Title
- Lift worksheet
- Status
- Your numbers
Public benchmark
8%
more sales in Vodafone’s A/B test, after its main content loaded 31% sooner.
Source: web.dev, Vodafone case study (opens in a new tab), 2021. A public benchmark. It is not a result of mine and not a promise.
Public benchmark
7,966
new security holes were found in the WordPress ecosystem in 2024, and 96% of them were in plugins. Off WordPress, that upkeep is gone.
Source: Patchstack, State of WordPress security (opens in a new tab), 2025. A public benchmark. It is not a result of mine and not a promise.
A site more than one person can edit.
If only one person still knows how to change your site, that ends here. Your content moves into a CMS with the fields your pages need, so marketing can publish a page or change the opening hours without filing a ticket.
The code sits in your repository and the hosting and CMS are in your accounts, from the day you carry on past week one. Hosting and CMS fees are yours and go straight to the providers. I don’t resell them.
Scope
What you get, and what you don’t.
Included
- The crawl and the URL inventory
- The redirect map, signed off by you before launch
- Your content moved as it is, into a CMS your team can edit
- Titles, descriptions, canonical tags and structured data carried over
- The launch, with the old site kept as the way back
- The 90-day watch and a before-and-after report
- The code in your repository, the hosting in your accounts
Not included
- A redesign. That is the website scope, and both can run as one project
- New copy or new pages
- Moving an app, a shop checkout or a design system. Those are quoted after week one
- Hosting and CMS fees, which you pay the providers directly
- A promise about rankings
Anything under “Not included” can be added. It changes the quote, and you see the new number before I start on it.
- Sheet
- M-06
- Title
- Scope
- From
- €12k
- Time
- 2–4 weeks
Price
Priced on the risk, not the hours.
Moving pages has become the cheap part. Cursor moved its own site off a CMS in three days, for about $260 in tokens. If I billed hours, a migration would cost very little and you would carry the risk.
So the price is for the part a tool doesn’t own: every address accounted for, every tag carried over, a launch you can undo, and ninety days of someone watching the numbers. From €12,000, usually 2–4 weeks.
Source for the Cursor figures: Lee Robinson, “Coding Agents & Complexity Budgets” (opens in a new tab), December 2025.
Moves the price up
- Many pages, or many page types that each need a template
- A second language
- A new domain at the same time
- Forms, gated content or integrations that must keep working
- A redesign on top
Keeps it at the from-price
- Content that moves as it is
- One language, the same domain
- One person on your side who signs off the redirect map
The first step
Check the site you have.
The free site check reads your current site the way a visitor and an AI crawler do, and lists what it finds. It takes about a minute and gives us a before picture. Bring it to the call, or skip it and book the call.
- Tool
- Site check
- Time
- About a minute
- Cost
- Free
FAQ
Questions people ask before they move.
I can’t promise rankings, and I’d be careful with anyone who does. What Google says: permanent redirects don’t lose PageRank, and rankings can move around for a while during a move. What I control: every old address gets a destination, every title and tag is carried over, and you see the full list before launch. Then I watch the numbers for ninety days.
The old site stays up, untouched, until the new one has passed the checklist. If something breaks on the day, I point the domain back, fix it, and launch again. That is why launch happens at a quiet hour and never on a Friday afternoon.
Yes. From the day you carry on past week one, the code is in your repository and the hosting and CMS are in your accounts. If you stop working with me after that, nothing has to be handed over, because you already have it.
Yes. That is half the reason to move. Content lives in a CMS with the fields your pages need, and I record a short walkthrough for the people who will use it.
Usually 2–4 weeks. Week one is the crawl, the inventory and the redirect map. You can stop at the end of it and I refund the week.
Yes, as two releases inside one project, priced as both. I move the site as it is first, then the redesign goes live on the new platform, so if the numbers move we know which change did it. If the design is fine and the platform is the problem, moving it as it is costs less and carries less risk.
WordPress, Webflow, Wix and Squarespace. If yours is something else, send me the address and I’ll say on the call whether I’m the right person for it.
Because moving the pages was never the risky part. You are paying for the list of every address, a decision about each one, a launch that can be undone, and someone who checks the numbers at day 1, 7, 30 and 90.
Guarantees
Four promises, in writing.
Fixed price
No overrunsThe price on the quote is the price. If I underestimated, that is my cost.
Staged payments
Stop after any stageYou pay per stage and can stop after any stage.
Week one
Refunded if you stopWeek one is a fixed fee of €3,000, counted toward the project. Stop at the end of it and I refund it in full.
Revisions
Until you sign offChanges inside the agreed scope of a stage are included until you sign it off.
A migration starts at €12k. Week one costs €3,000, and you get it back if you stop there.
Book a 20-min call