Switch platforms without losing what you've built.
The fear is always the same: we rebuild and the traffic disappears. It happens, and it can almost always be avoided with work done before launch: mapping every URL, keeping the pages that earn traffic and redirecting the rest.
When a rebuild is worth it.
A rebuild doesn't always pay off. Check which situations apply to you.
If two or more sound familiar, it’s time.
- 01
The platform is the bottleneck
Each change needs a plugin, each plugin adds risk, and speed depends on patches. Improving the platform won't fix it.
- 02
You can't restructure the content
The CMS lacks a real content model, which is usually where growth work stalls.
- 03
Editing requires a developer
Even a headline change needs a ticket, and the yearly cost can exceed a rebuild.
- 04
Security or maintenance debt
Outdated core software, abandoned plugins and no update path turn it into a business risk.
What protects your traffic.
The migration work we do before anyone sees the new design.
A full URL inventory
Every current address, with its traffic and rankings, gathered before deciding what to keep.
Redirect map
One-to-one where possible, deliberate where not. Each URL goes to its closest equivalent, never the homepage.
Content audit
What earns traffic, what adds nothing and what should be merged. Many sites end up lighter on purpose.
Structure carried over
Headings, internal links and metadata are rebuilt with intent, not copied.
Launch rehearsal
The switch is tested end to end on staging, including redirects and analytics.
Post-launch monitoring
Search Console and crawl errors are checked daily for the first few weeks.
What usually goes wrong, and when it doesn't.
Each risk, and how we avoid it.
How it works.
How we usually work. The quote sets the real dates before work starts.
Inventory
Crawl the current site, pull traffic and ranking data, and decide what stays, merges or goes. Deliverables: URL inventory; keep, merge or drop list.
Map
Redirect map, new content model and design decisions, approved before the build. Deliverables: redirect map; content model.
Rebuild
The new site is built and content migrated, keeping the old structure where it was performing. Deliverables: staging site; migrated content.
Switch and watch
A rehearsed launch, then daily monitoring of indexing, redirects and errors. Deliverables: live site; monitoring report.
Questions we get asked
Expect some movement early, then recovery. Done well, sites often return to the same level or better, because the rebuild also improves speed and structure.
Often, yes, if your team knows it and the content model fits. We recommend moving only when the platform is holding the site back.
It's audited, not deleted by default. Pages with traffic carry over, weak pages are usually merged, and you approve the list before anything is removed.
Until the switch. The new site is built in parallel on a preview URL, so downtime is limited to the DNS change.
Yes. Blog URLs are mapped one-to-one wherever the content is kept; that's often where much of the ranking value sits.
Tell us what you need built.
Describe the project in a few lines. We'll reply with a plan, a timeline and a fixed quote.