Let ChatGPT or Claude Handle Your Website Updates

There is a new era for websites taking shape. It starts with the ChatGPT or Claude you already use.

The exciting part is being able to describe the website you want in the same way you would describe it to a person.

Your latest project belongs on the homepage. Your services need an update. The layout could use more space on phones. Each change is easy to explain:

Add my latest project. Make the homepage feel cleaner. Fix the layout on phones. Keep the parts that already work.

Your AI can write those changes. You can ask it to try another heading, keep an image, or leave the rest of the page alone.

That is a pleasant way to work. Describe the change, look at the result, and improve it until it feels right.

But until that work leaves the conversation, your website stays exactly the same.

That last step is where things get interesting. There is a simple way to turn those replies into a website you can preview, improve, and publish.

The frustrating part starts after the good answer

Ask your AI for a better homepage and it can write a clearer heading. Ask for a different layout and it can write the page code. Give it useful feedback and it can try again.

Then comes the awkward part.

Where does that work go?

The new headline is in a conversation. The page code is in another block of text. Your actual website still looks exactly the same.

Now you have to turn the answer into a change: work out where it belongs, put it in the right place, check what broke, and get the result online. You asked the AI to take a job off your plate. You still have the last half of the job.

Giving a regular chat your website address does not, by itself, give it access to update that existing site. The AI has an answer. The website has not received it.

Your AI needs somewhere to do the work

Think about hiring someone to update your website.

You would tell them what you want. But you would also give them the things they need to do it: the page they can change, a way to see the result, and a way to put the approved version online.

Without those things, even a great web designer can only send you suggestions.

An AI needs the same practical setup. It needs more than a description of the website. It needs somewhere for the work to become a website.

That is the missing step between "my AI gave me some code" and "my AI helped me update the page."

You should not need to learn a new builder every time you want a different layout. And you should not need to start a new website just to fix the one you already have.

The updates you actually want to make

Usually, you are not trying to invent an entire new product. You want the site to catch up with your business or your work.

Your services have changed. Your portfolio is out of date. Your opening hours are wrong. The main heading says something you would never say to a customer.

Those requests already make sense in plain English:

Replace my introduction with "I design websites for independent businesses." Keep my project images and contact links.

Make the services section easier to read on phones. Keep the desktop layout the same.

Change the opening hours to Monday through Friday, 9 a.m. to 6 p.m. Leave everything else alone.

You can explain those changes without naming a CSS property or finding the right menu. You can also explain what should stay. That matters when you want an update, not another redesign you have to pick apart.

What if you could stay in that conversation?

Imagine the AI handling the page changes while you make the decisions.

"That heading is better. Make it shorter."

"Keep this layout. Use the new service descriptions."

"The phone version still needs more space."

You look at the page instead of trying to picture what a code block will do. You ask for the next change instead of hunting through settings. And you choose when the result is ready to go live.

That is a much better use of your attention. You know your business, your work, and the people you want to reach. Your AI can help turn those decisions into changes to the page.

The useful setup gives you a place to try, review, and publish those changes, with the AI you already use.

Here is the trick: give your AI a website workspace

Think of Figment as a computer for your AI's website work. It gives the page a place to live, the changes a place to run, and you a preview to approve.

ChatGPT or Claude does the editing. Figment turns the returned files into a website you can see and publish.

Here is how you use it today:

1. Bring your website. Open Figment, sign in, and import a public site you own or have permission to copy. You get a separate copy; your original stays unchanged.
2. Prepare the job. Choose Prepare site files, describe your change, then select Prepare files and prompt. Use Download site file and Copy prompt.
3. Let your AI edit it. Attach the downloaded file to your own ChatGPT or Claude chat and paste the prompt. Ask it to return the requested figment-changes.json file.
4. See the result. Upload the returned file under AI response (.json) and choose Create preview. Check the page on desktop and mobile. Prepare fresh files when you want another edit.
5. Put it online. Choose Publish when you approve the result. The edited copy gets a separate Figment URL.

That file handoff is the connection today. You move the files between your chat and Figment; it is not a connected AI account or an unattended agent. The AI edits the selected HTML and CSS. You review the result and approve publication.

Import, editing with your own AI, and previews are free. No Figment subscription or API key is needed. Your AI provider's limits and charges still apply. Figment storage and hosting limits apply, and paid hosting features are separate.

Only have a Figma design? Publish it first with the Figment plugin, then use that public URL. Forms and existing booking links need their own checks; login, databases, and custom backends do not move from a URL. See the connected-services checklist before replacing a working site.

Start with the one update you have been putting off. Let your AI write the change. See what it looks like before you publish.

Let your AI handle your next website update