Migrate your website to Claude Code
I rebuild the site you already have into a project you can talk to, and I do it without changing a single URL.
Who this is for
Your site runs on Webflow, WordPress or Squarespace, and it barely matters which. What you want is to stop waiting on someone every time a line of text changes, and you have probably been reading about Astro and headless CMSs while looking for it.
By platform
Why it still goes through a person
You already send prompts, you just send them to your developer, and then you wait four days for a pricing section to show three tiers instead of two.
Some of you do something stranger. You open Claude, describe the page you want, and a minute later it exists, with the layout and the copy already in place. Then you send it to your developer, who rebuilds it by hand in the builder. The page gets made twice, and you pay for the second one.
It has probably crossed your mind that this is an odd way to run a website.
The reason is that your site lives inside a platform that only accepts changes through its own editor, and nobody on your team wants to learn that editor. There are MCP connectors now, but they sit on top of that same old interface, so when the page actually has to look professional it is still safer to ask the developer. The prompt goes to a person instead of to the project. I move the site out.
What it looks like once it is moved
You write the change you want in Claude. It reads the instructions set up in the project, and then it makes the change, with nobody in the middle.
For anything genuinely complicated you still want a developer, and they will get through it faster than they used to, since there is no platform standing between them and the site.
Sites that already work this way
This one does. I change glevsky.com, including this page, by asking Claude Code.
demo.glevsky.com is a bigger example: a marketing site for Openslot, a scheduling product I made up to show how I build, with a blog, a resource library and customer stories.
What does not change
To a visitor and to Google, the new site is the old site:
- every URL, exactly as it is now
- every title, meta description and heading
- the copy, word for word
- canonicals, robots, sitemap, and any redirects you already have
- analytics, tags, consent
- forms, and where they deliver
Most of the traffic damage in a migration comes from rewriting the site while moving it. If the rankings then shift, you have no way of telling whether the new platform or the new text did it, and no way of undoing the right half. So I leave the content exactly as it is.
You may well want to update the look and feel while the site is being rebuilt anyway. I bring in a designer for that once the move has held steady in Search Console, and it goes quickly at that point, since a new look becomes a change to the system rather than a rebuild of every page.
Rules help control the fun
You will be able to change anything on the site, which is the point, and also the thing most likely to go wrong.
For example: there is one size for the biggest heading on the site, and every page uses it. That agreement is most of what separates a site that looks built from one that looks thrown together. So the rule is simple: first try to build the new thing out of what is already there. If that genuinely does not work, for a launch or an event or a campaign, then it becomes a new named part of the system, added once, and available everywhere afterwards.
To make that hold, I write the style guide into the project itself, covering the tokens and what each component is for, and the agent reads it before every change. I also leave checks that fail loudly when something drifts.
The agent follows the rules I write down, most of the time to the letter, and it has no opinion of its own about how your site should look.
Webflow to Claude Code
I have built Webflow sites for years and I still think it is the best visual builder available, which is exactly why I can tell you that almost nobody on your team ever opens it. You are paying for an editor you do not use, and the work still arrives as a message to a developer.
If you have hundreds of pages and people who open the Designer every week, stay where you are and tell me what is actually broken instead.
WordPress to Claude Code
WordPress works well while somebody looks after it properly. When nobody does, it drifts: plugins pile up and half of them stop being maintained, the theme gets edited in three different places, and the whole thing eventually turns into something worth attacking. Untangling that is usually more work than moving the content somewhere calmer.
Claude Code can reach WordPress through plugins and MCP connectors, and it handles content well. Those connectors work through the WordPress API, which covers posts and pages but leaves the theme, the templates and most plugin settings outside of what you can ask for.
Squarespace to Claude Code
Squarespace exports only part of a site. Basic pages and one blog come out as a WordPress-format file, but product, event and index pages, audio and video blocks, and the design itself stay behind. So I rebuild a Squarespace site from its live pages, which is how I move every site anyway.
How the work goes
- Inventory. Before anything gets built, I go through the current site and write down everything it is made of, page by page.
- Foundation. I set up the design system and the project rules that every page after this one is built from.
- Pages. I rebuild each page one to one and check it against the original.
- Infrastructure. The repository and the hosting are created in your own accounts from the first day. Your email, and anything else that runs on the domain or its nameservers, is untouched by the move.
- Launch. DNS and Search Console. Every address stays exactly where it was, so there is nothing to redirect, and the old site stays up until the new one answers on every URL.
- Handover. You make a real change yourself and publish it while I am still there to answer. After that I would rather keep working with you than disappear. If what you want is the speed and the predictability, but not the conversation with Claude, I will keep making the changes for you.
A normal business site takes about three weeks to move, and about two more if you want the new look as well.
What I have not done yet
I have no real experience with ecommerce or with membership areas, and I would rather tell you that now than discover it on your project. If you have one of those and you like the idea anyway, I will take it at a reduced rate.
FAQ
How long does a website migration take?
About three weeks for a full move of a normal business site, and about two more if you want a refreshed look afterwards. Most of that time is spent waiting on decisions rather than on building.
Will my rankings drop?
The URLs and the content stay identical, so there is nothing for Google to re-evaluate except speed, which improves. What breaks migrations is a page quietly changing its address or losing its title, which is why I inventory the whole site before touching anything.
Do I need to know how to code?
No. You describe what you want and look at what comes back, which is what you already do with everything else.
Is there still a CMS for the content?
There can be. Content lives as structured files that Claude reads and writes directly, which is enough for most teams. If you want a proper editing screen for writers who will never open a terminal, a git-based CMS sits on top of those same files and I set it up during the build. Tell me at the start, since it shapes how the project is put together.
What does the site cost to run afterwards?
Hosting a site this size on Cloudflare is usually free, and the only other cost is the Claude subscription your team already pays for.
Who owns it?
You do. The repository, the hosting and the domain sit in your accounts from day one. If you never speak to me again, the site keeps working and you keep editing it.
Want to look at your site?
Book a call and send me the URL beforehand. I will tell you what the move involves, how long it takes, and whether it is worth doing at all.