Your calls drop off in March. You call your web person and ask what changed. Nobody knows, because nobody wrote it down, so you spend six weeks guessing at a problem that took someone four minutes to cause in February. A website change log is a dated list of every change made to your site, and it’s the cheapest insurance a small business can buy.
What a change log actually is
It’s a record. Date, what changed, who did it, and why. That’s the whole thing, and a spreadsheet handles it fine.
You’re not documenting code. You’re documenting decisions, and decisions are what you’ll need to reverse later. A line that reads “March 3, rewrote the services page headline, wanted to sound less stiff” is worth more six months from now than any analytics report.
Most small businesses have no version of this. The site changes constantly, and the record of those changes lives in scattered emails, a text thread and one person’s memory.
Cause and effect stops being a guess
Search results move for lots of reasons. Some are yours and some are Google’s, and you can’t separate them without a timeline. A traffic dip with no log is a mystery. The same dip with a log is a two-minute check.
Line up your changes against your traffic dates and patterns appear fast. For a land survey company, a simple title change or URL update can be enough to affect rankings if it isn’t documented. The page you edited on the 12th started sliding on the 19th.
Without the log you get the worst outcome available. You change five more things trying to fix it, and now you have six variables and no idea which one matters.
Your web person will leave
Someday your developer moves on, your agency drops you, or your marketing coordinator takes another job. Everything they know about your site walks out with them.
The next person inherits a website with no history. They don’t know why the contact form has that weird redirect, or why one page has a different template, or which plugin is holding the whole thing together. So they either break something or they rebuild from scratch and charge you for it.
A change log is the handoff document you never had to write. It also makes you a better client, because you can answer questions instead of shrugging.
Accountability cuts both ways
If you pay an agency, a log tells you what you got. Monthly reports say things like “on-page improvements” and mean almost nothing. A change log with real entries makes the work visible.
It protects them too. When traffic tanks and the client points a finger, a log showing they touched nothing that month settles it in a minute. Good agencies keep one already and will hand it over if you ask.
Ask for it before you sign. If a vendor won’t give you a running record of changes to a site you own, that’s the answer to your question about them.
What to write down
- Page content edits, with which page and roughly what changed
- Title tags and meta descriptions, before and after
- URL changes and redirects, always, with no exceptions
- New pages published and old pages deleted
- Plugin, theme or platform updates
- Schema markup added, changed or removed
- Google Business Profile edits, since those move local results
- Hours, phone number or address changes anywhere they appear
- Anything a third party did to your site
That URL line is the one people skip. A changed URL with no redirect kills a page’s rankings silently, and nobody notices for weeks. It’s the most common self-inflicted wound in local search.
Where to keep it
A shared spreadsheet works. Five columns: date, what changed, where, who, why. Pin it somewhere everybody with site access can reach.
Fancier tools exist and most small businesses abandon them by week three. The best log is the one that’s still getting entries in month nine. Boring wins here.
One rule makes it stick. Write the entry when you make the change, not later, because later never comes. It’s fifteen seconds while you’re already in the tab.
The AI search wrinkle
Search results now include AI answers that pull from your pages, and those systems are picky about what they quote. Change a paragraph and you might lose a citation you didn’t know you had. Nobody sends you an alert about that.
Content edits used to be low risk. Now a rewrite that reads better to you can quietly remove the exact sentence an AI was pulling. Without a log you can’t even test the theory, let alone put the sentence back.
Keep the old text in your log entry, or at least a note about what the paragraph said. That’s a small habit with a real payoff when something stops working and you need to walk it back.
What not to bother with
Don’t log image swaps, typo fixes or a comma. You’ll quit in a week and the log dies with the habit.
Log anything that could change what a search engine reads, what a customer sees, or how the site works. Everything else is noise. If you can’t decide, ask whether you’d want to know about it during a bad month.
Start with the last six months
Sit down once and write what you remember from the past half year. It’ll be incomplete and it’ll still be better than nothing, and it gives the log a running start instead of an empty page.
Then add entries as you go. In a year you’ll have something no competitor of yours has, which is a real record of what you did and when. That’s the whole trick, and it costs nothing but the habit.
