Claude-first website migration

Update your website by telling Claude what you need.

I move your marketing website into a setup where Claude can prepare new pages, update articles and change copy across the site. You review the changes before they go live.

The problem

A small website change should not become a project of its own.

You launch a feature and need a page for it. Your positioning changes, but the old message is scattered across the site. A useful article needs an update, and nobody wants to work through the editor again.

I set up the site so Claude can work with its code, content and design instructions together. You describe the change, inspect a preview and decide what to publish.

What Claude can prepare

What you can ask Claude to prepare

01

A landing page for a new feature

Give Claude the feature details and a page to use as a reference. It can prepare the copy and layout using your site's existing components.

02

An updated article

Provide new sources and explain what needs changing. Claude can revise the article, suggest relevant internal links and prepare it for review.

03

A positioning change across the site

Give Claude the approved wording. It can find old references across pages, metadata and FAQs, then propose the edits together.

04

Another language

Claude can prepare translated pages using your existing structure. Someone fluent in the language still needs to check the wording and meaning.

05

Internal links and page metadata

Claude can inspect the site, suggest links between related pages and draft titles and descriptions. You review relevance and accuracy before publishing.

What I set up

01

Your website in a repository you control

The site's code and content live in Git, with a record of changes. I assess what can move and identify anything that needs separate handling before starting.

02

Instructions for Claude

I document your page structure, reusable components and writing rules. Claude gets a reference for how to make changes without redesigning the site every time.

03

A preview before publication

I set up a way to review changes before they reach the public site, with checks and a way to return to an earlier version.

04

Migration checks

We agree which pages and functions must carry over. I check the relevant URLs, redirects, metadata, forms, analytics and mobile layouts before launch.

05

A practical handover

I show you how to request a change, inspect what Claude did and publish an approved version. We use a real change to your site during the handover.

You still need to review the work.

Claude can misunderstand a request, invent a detail or break something. You still need to check facts, wording, design and functionality.

The setup gives you a way to make and review changes. It does not remove responsibility for what you publish.

Discuss my website

Questions before you migrate

Questions before you migrate

Do you have to rebuild the entire site?

I review your current setup first. Some sites need a migration; others already have much of what is needed. The scope depends on how your content, code and integrations work today.

Can you keep the existing design?

Keeping your current design is the starting point. I flag anything that cannot transfer directly before we agree the work.

Will this improve SEO or AI-search citations?

There is no guaranteed increase. A migration can also hurt search performance if it is handled badly. The work includes checking the agreed search-related essentials, such as existing URLs, redirects and metadata. Content quality and other factors still matter.

Will I still need a developer?

For some changes, yes. Claude can help with routine page and content work, but complex integrations, security and application logic may still need a developer.

Which framework and hosting will you use?

I recommend a setup after reviewing your site. The choice depends on your content, integrations, editing needs and existing infrastructure.

How much does it cost, and how long will it take?

That depends on the size of the site and what needs to keep working. We agree the scope, price and timing before the migration starts.

Show me your website and the changes you keep putting off.

We can discuss whether a Claude-first setup fits, what needs to move and what should stay as it is.

Discuss my website