How to edit a static website with an AI assistant

A static website has no dashboard to log in to. For a lot of people that sounds like a drawback, until they realize they already have something better: an AI assistant they talk to every day. This is how editing a static website with an AI assistant actually works, from the setup to everyday changes.

Why a static site and an AI assistant work so well together

A static site is a folder of plain files: HTML for the pages, one stylesheet for the design. That’s exactly the kind of thing AI assistants are good at reading and writing. There’s no page builder to click through, no plugin settings to hunt for, and no database in the way. Your assistant opens the file, makes the change you asked for, and saves it.

I run my own site this way. I describe the page or post I want, my assistant (I use Claude) builds it from the same components as the rest of the site, and I check it before it goes live. It’s the fastest way I’ve ever added to a website.

What you need

• An AI assistant that can work with files. The smoothest options can run commands on your computer, such as Claude Code, OpenAI’s Codex, or Gemini CLI. A chat-only assistant works too; you just copy its changes into place yourself.
• A connection to your site. Usually SSH, a secure connection your host provides. If you host with me, this guide gives you a prompt that walks your assistant through the setup.
• A guidebook for your assistant. This is the piece most people skip, and it’s the one that keeps your site safe.

The guidebook: how to edit without breaking anything

An AI assistant will happily change anything you ask, including things you didn’t mean to touch. A guidebook is a short set of instructions written for your specific site. It tells your assistant how the site is put together, which files hold content, which parts are the design, and what it should never change on its own.

Every static site I hand over comes with one. It keeps your assistant to content, like text, images, pages, and posts, and away from the layout and the code that holds the site together. Working through it, the chance of breaking anything is very low. You own your site, so you’re free to work outside the guidebook. That’s just where things can break.

What everyday edits look like

Once you’re set up, editing your site is a conversation. A few examples:

• “Change our hours on the contact page to 9 to 5, Monday through Friday.”
• “Replace the photo in the About section with this one.”
• “Add a page for our new service, using the same layout as the other service pages.”
• “Turn these notes into a blog post, and add it to the blog.”
• “Show me what a testimonials section would look like on the home page.”

Ask your assistant to show you the change before it goes live, then look at the page on your phone and your computer. If you don’t like it, ask for something different or ask it to put things back the way they were.

When to ask a person

Your assistant can handle almost all of your content. Bring in your developer when you want something structural: a new page template, a set of landing pages with a new design, a form connected to another service, or a fix your assistant can’t sort out. That’s exactly how I work with my static clients. They run the day-to-day, and they come back for a block of hours when they want something bigger.

Want a site you can run with your AI?

If AI is already part of your day, a static site is the easiest website you’ll ever own. Here’s how I build them, and how the handoff works.