Full crawl and inventory
Every URL recorded with its traffic, rankings and status before anything moves.
Migration
Move platform or host without losing traffic
A migration is the highest-risk thing you can do to a site that is already working. Change the URLs without mapping them, lose the structured data, let the new host serve the wrong status codes, and months of search equity goes in an afternoon.
We treat it as a checklist rather than a creative exercise. Every existing URL is crawled and recorded with its traffic and rankings. Each one is mapped to its destination, and anything with no natural home is decided deliberately rather than pointed at the homepage. Redirects are tested on staging, DNS is prepared with a short time-to-live so a rollback is quick, and the whole crawl is re-run after the switch. Then we watch Search Console daily for the first fortnight, because that is when problems surface.
from £650
Start a project ↗What you get
What’s included
Redirect map
One-to-one mapping wherever possible, with the exceptions decided deliberately rather than by default.
Staging verification
Redirects, status codes, canonicals and structured data checked on staging before the switch.
DNS and cutover
Short time-to-live set in advance, cutover at a quiet hour, rollback ready if needed.
Two weeks of watching
Search Console and analytics checked daily after launch, with anything that moves the wrong way fixed.
How it works
Three steps, and you see the work at each one.
Inventory
Crawl the current site and record what is there and what it is worth, before touching anything.
Map and test
Build the redirect map and verify it on staging, including status codes and structured data.
Cut over and watch
Switch at a quiet time, re-crawl immediately, then monitor daily for a fortnight.
FAQ
Questions before you call
How long does a migration take?
One to two weeks for a typical business site, most of it preparation. The cutover itself is usually under an hour.
Will there be downtime?
Practically none. We prepare DNS in advance with a short time-to-live and cut over at a quiet hour, so the change propagates in minutes.
What if something goes wrong?
The old site stays available until we are satisfied, and DNS can be pointed back within minutes. That is why the time-to-live is lowered in advance.
Do we need this if we are only changing host?
A host move is lower risk than a platform move, but status codes, HTTPS and IP reputation can still bite. It is a shorter version of the same checklist.
Have a project in mind?
Let’s build something
worth visiting.
Tell us what is not working and we will tell you what we would do about it. No pitch deck, no pressure.