← All articles Big Site, Small Budget

Is it safe to let AI work on your website?

None of it is new or clever. It's a short list of habits we follow every time, with no exceptions for the AI.

A green wooden sailboat out of the water on jack stands in a boatyard, with the travel lift waiting at the water's edge in the fog

The work happens out of the water. It goes back in when it's ready.

It’s a fair worry. If an AI can change your website, what stops it from breaking your website? The honest answer is that it can, and so can a person. AI website safety comes from the habits that have always kept websites safe, applied more strictly when an AI is doing the typing.

Part of Big Site, Small Budget, a series about how small businesses can get the kind of website that used to take an enterprise budget.

How we handle AI website safety

We never work on your live site directly. Every change happens on a private copy first, where we can look at it, and break it, without anyone seeing.

Before every change, we back up the database (where your pages and settings are stored). It takes about two seconds. On one project this year we took 44 of those backups.

Nothing goes live until a person approves it. Our deploy tools, the ones that put changes live, show exactly what’s about to change. Then they wait for someone to type the word “deploy.” The AI isn’t allowed to type it.

The tools also refuse some changes outright. If a change would delete a page, change which plugins are running, or replace a page with one that doesn’t match it, the deploy stops before anything happens.

Customer information stays private. When we work with things like volunteer or customer lists, our tools are written so they never show anyone’s details.

Two mistakes, and what caught them

On a nonprofit’s site, an early deploy replaced the wrong page. A page on our copy shared an ID number with the nonprofit’s history page on the live site, and the live one got overwritten. We restored it from the backup taken minutes before. That mistake is why the matching check above exists.

On the same site, a database tool turned the curly quotes and dashes on nine pages into question marks. A character setting had defaulted to the wrong value. We repaired all nine pages the same day from the backups, and every script we run now sets that value explicitly.

Both are the kind of mistake anyone who works on websites makes sooner or later, with or without AI. The backups kept them small.

Questions for whoever runs your site

  • When was the last backup, and have you ever restored from one?
  • Do changes happen on a copy first, or straight on the live site?
  • Who can put changes live, and does a person check them first?
  • Is WordPress kept up to date? Here’s what that involves.

If the answers are vague, get that fixed before something goes wrong. The same goes if you built the site yourself with a chatbot and the answers are yours to give.