Our method: Blue Ocean positioning and StoryBrand messaging - how we build sites that win
ServicesIndustriesExpertiseCase studiesPricingProcess
Get a free website redesignContact us
Migrations — Hand-coded / HTML → Claude Code

HTML to Claude Code migration.

An old hand-coded site is fast but frozen: every change means finding a developer, and nobody remembers how it was built. We rebuild it as plain, modern code on Claude Code - keeping what works and the rankings - so it stays fast and owned, but you can change it by asking instead of hunting for whoever wrote it.

Start a migrationSee it on your homepage, freeSpeed kept · rankings kept · most sites live in 1–3 weeks

What actually changes.

The same site, the same content, a completely different foundation. Everything on the left disappears; everything it did is either built into the code or no longer needed.

Hand-coded / HTML logoBefore · the hand-coded stackuntouched since the developer left
The developer who leftlast seen years ago
Hand-edited HTML pagesevery change is manual
Manual FTP deploysno version control
No CMScontent frozen in markup
jQuery + old librariesunpatched for years
Desktop-era layoutpinch to zoom on mobile
Ageing shared hostingrenews annually
Claude CodeAfter · plain code on Claude Codeowned outright
Your content, as structured datayours
Plain, fast codeyours
Schema, SEO and analytics built inincluded
A repository in your nameowned
Nothing to update. Nothing to patch. Nothing to renew.
Why move

Three things you stop paying for.

Maintainable again

Modern, structured code that any engineer can read - and that you can change just by describing what you want, usually live the same day.

Fast and accessible

We keep the speed of a lightweight site and add what older builds miss: accessibility, responsive layouts, structured data and Core Web Vitals held at threshold.

Rankings kept

URLs mapped, 301 redirects in place, metadata carried over - the search equity of a long-standing site is preserved, not reset.

How rankings survive the move.

The SEO-safe migration, in one glance

Redesigns lose rankings through skipped redirects, so we never skip them. Every migration runs the same four checks, in order, and the last one happens after launch, not before.

Step 1

URL inventory

Every URL on the old site crawled and recorded, with its rankings, backlinks and traffic noted. Nothing moves until the full map exists.

the complete map
Step 2

Rebuild, mirrored

Content, titles, metadata and structured data carried over one to one. The design can be kept faithful or sharpened; the crawlable structure stays deliberate.

staging site, verified
Step 3

Redirects, one to one

Every old URL 301-redirects to its exact successor. No wildcard shortcuts, no redirect chains, no orphaned pages.

redirect map shipped
After launch

Crawl re-test

The live site is re-crawled against the inventory: every redirect checked, every page indexed, Search Console watched through the handover weeks.

rankings holding
How editing works after the rebuild
Can we add the new case study to the homepage and update the team page with two new starters?
Done. Both changes are live, and the case study is linked from the services page too.
shipped same day · no admin panel · nothing to update
Editing, after the rebuild

Change the site by asking.

You describe the change and we ship it, usually the same day. No admin panel to learn, no update that takes the site down on a Friday, no waiting for a developer to be found.

Honest caveat: if hands-on, drag-and-drop editing is essential for your team, we’ll tell you on the call and recommend Duda instead. We build on both lanes daily and recommend on fit.

The honest comparison

Hand-coded / HTML vs plain code, plainly.

Hand-coded / HTMLPlain code on Claude Code
OwnershipTechnically yours, practically opaque - only its author really understood itPlain code in a repository in your name, readable by any engineer
SpeedOften quick - lightweight pages age well - but unoptimised for modern devices and formatsThe same lightness, built to Core Web Vitals thresholds and held there
SecurityOld libraries and forgotten scripts, unpatched for years, on ageing hostingModern dependencies, minimal surface, a monitored footprint
MaintenanceEvery change means finding a developer willing to touch itNothing rots. Changes are made to the code deliberately, when you ask
EditingHand-editing markup and uploading over FTP, if anyone still daresDescribe the change, it ships same day. Structured content keeps edits safe
Cost over timeCheap to host, expensive to change - and one emergency from very expensiveHosting measured in pounds, changes shipped by asking

Where Hand-coded / HTML genuinely fits, we’ll say so on the first call. The migration makes sense when ownership, speed and the end of maintenance matter more.

Asked before every migration.

No. Plain code stays fast; we just make it maintainable, accessible and properly optimised on top.

Related