Engineering: website rebuild
Scriters
A full rebuild onto edge infrastructure, shipped in one move, with the mail flow untouched
The problem
Rebuilding a live site usually means a window where something breaks, and the thing that breaks is almost always email. The DNS record that points the site somewhere new is often the same record set that carries the mail, so a rebuild that looks clean in a browser can quietly stop the business receiving enquiries.
What we built
- A complete static rebuild, deployed to an edge worker. Pages are served from the edge with no origin server to keep alive, patch or pay for, which removes a whole class of failure rather than monitoring it.
- Email deliberately left where it was and untouched through the cut over, so the mail flow never depended on the rebuild going right.
- Structured data and machine-readable content files, so the pages can be parsed and quoted by answer engines rather than only rendered for people.
- One cut over, not a staged crawl. The rebuild was finished and verified before anything was switched, so the live site never spent a week half migrated.
What we would not claim
No traffic, ranking or conversion figures. A rebuild changes the ground a site stands on, and attributing later performance to it without a clean before and after would be guesswork.
Client engagement. No performance figures are published for this client.
Your turn
We set the baseline before the work starts.
That is the part that makes a number mean something a year later.