Keep your site fresh: the edit-and-republish workflow

Your site is live — and then real life happens. Your hours change. You add a service. You spot a typo on the About page. The thing people quietly dread about “having a website” is keeping it current, and it turns out to be the easiest part of the whole business. You don’t call anyone, and you don’t start over. You change one file and republish, and your live site updates itself in about a minute. Here’s the loop.

How does updating a live site actually work?

Remember what your website really is: a file (or a few files) sitting in your GitHub repository, which Netlify turns into your live site. So “updating your website” really means “replacing a file.” That’s the whole concept.

The loop is three steps: change the file → put the new file in GitHub → Netlify rebuilds it. You wait about a minute, and the change is live. No code, no developer, no monthly plan with a web company.

How do I make the change with Claude?

The safe path for a beginner is to let Claude make the edit and hand you a clean, finished file — rather than editing the website code by hand, where one missing bracket can break the page.

Three steps:

1. Give Claude your current file. Open Claude and upload the index.html you have saved. This matters: use your latest version, the one that matches what’s live right now — not an old copy from three updates ago.
2. Tell it exactly what to change, in plain language. You don’t need to know any code:

3. Download the updated file Claude gives you. That’s your new index.html.

For a tiny fix — a single typo — you can edit the file directly in GitHub (the pencil icon). But for anything bigger than a word or two, letting Claude rewrite the whole file and handing you a clean copy is safer and just as fast.

How do I publish the change?

You’ve done this once already when you first went live; it’s the same move every time. Go to your repository, into the folder where your index.html lives, and choose Add file → Upload files. Drag in your new index.html — because it has the same name, GitHub replaces the old one — and commit the change.

That’s it. Netlify is watching your repository, so it notices the new file and rebuilds your site automatically. About a minute later, your live site shows the change. If you don’t see it right away, your browser is showing you a cached copy — a hard refresh (Ctrl+Shift+R, or Cmd+Shift+R on a Mac) clears it.

The one habit that prevents disaster

Here’s the mistake that bites careful people: editing an old copy of your file, uploading it, and quietly wiping out a change you made last month.

The fix is a simple habit: always work from your latest version, and save each new one as you go. After every update, keep the file Claude gave you as your “current” copy — that’s the one you’ll hand it next time. If you’re ever unsure which version is newest, the answer is always the one sitting in GitHub right now; download that one before you start editing, and you can’t go wrong.

(GitHub also quietly keeps a history of every version you’ve ever uploaded, so a bad change can be undone — but it’s far easier to avoid the tangle than to unpick it.)

Does republishing cost anything?

No. Republishing is simply another deploy, and your free Netlify plan includes a monthly allowance of them — currently enough for roughly twenty updates a month on top of normal visitor traffic. Occasional upkeep — new hours, a price change, an added page now and then — stays comfortably inside that. (Even in the unlikely event you blew past it with dozens of changes in a single day, the free plan pauses rather than charging you; the full picture is in Publish with Netlify.) For normal maintenance, keeping your site current costs nothing.

That’s the rhythm of owning your own site: change a file, republish, done — in a minute, for free, without anyone’s help. And when the change is about wording — new copy for a page, a fresh headline — the same plain-language approach from writing your business pages applies. The website you built is yours to keep current, easily, for as long as you run your business.