A client emailed me last month. “Tony, our traffic dropped. What happened?”
I opened the terminal, ran a command, and had the answer in four minutes. A heading change on their homepage three weeks earlier had shifted how Google understood the page. One line of text. Measurable impact.
I could see this because every change to that website is recorded. Not in a spreadsheet someone forgets to update. Not in a Slack thread that scrolls into oblivion. In a version-controlled history where every change has a date, a description, and a diff showing exactly what was different before and after.
Most websites don’t have this. Most websites are black boxes.
The Most Expensive Question
“What changed?” is the question that follows every traffic drop, every ranking shift, every conversion rate wobble. And in most businesses, the answer is some version of “we’re not sure.”
Your web designer updated the homepage copy three weeks ago. Your SEO agency restructured the blog categories. Someone changed a meta description. Someone else added a redirect that points to the wrong page. Each change made sense at the time. None of them were recorded in a way that connects the change to the outcome.
The problem isn’t the traffic drop. The problem is the gap between “something changed” and “this specific thing changed.”
Google Search Console will tell you that impressions dropped on Tuesday. Google Analytics will tell you that bounce rate increased. Neither will tell you why. Because neither knows what changed on your end. They see the effect. The cause is on your side of the wall — and if nobody wrote it down, it’s gone.
Your Website’s Missing Changelog
Every serious piece of software has a changelog. When your phone updates, there’s a list of what changed. When your accounting software releases a new version, the release notes tell you what’s different.
Your website — the thing your customers see first, the thing Google judges you by, the thing your entire online presence depends on — almost certainly doesn’t have one.
Most business websites are updated by someone logging into a CMS, making changes, and clicking publish. No record. No before-and-after. No trail. The previous version is overwritten and gone.
When things are going well, this doesn’t matter. When they’re not — when rankings drop, when a page stops converting, when something breaks — you’re reconstructing from memory. “I think we changed the heading last month. Or was it the month before? And did we change the meta description at the same time?”
I’ve been in this industry for twenty-six years. That conversation happens in almost every SEO engagement. The client is frustrated because something changed. The agency is frustrated because they can’t isolate what. Everyone’s guessing.
What I Do Differently
Every website I manage uses version control. The same technology that software developers use to track changes to code, applied to the website itself.
Every change gets a record: what changed, when, and a description of why. Not a vague “updates” note. A specific message. “Homepage: replace generic heading with location-specific H1.” “Blog: consolidate three overlapping posts into one comprehensive guide.” “Product page: update pricing, add size chart.”
When something shifts in the rankings, I don’t guess. I search the history. “Show me every change to this page in the last 30 days.” The answer appears in seconds. Not “we think we changed something” — “we changed this specific thing on this specific date.”
A real example
Last December I removed fifteen blog posts from this site in one go. Three weeks later, rankings shifted on a handful of pages. Because I’d recorded each removal separately — which posts, which redirects, which internal links were updated — I could trace which specific removal affected which ranking. If I’d done it all as one big “content cleanup” with no detail? I’d have been guessing like everyone else.
I wrote about the full methodology in The Atomic Commit. The short version: treating every website change as a discrete, documented event turns your site history from a black box into a diagnostic tool.
Why This Matters For You
You might not manage your own website. Most business owners don’t. But you can still benefit from this thinking.
Ask your web designer: “Do you use version control for my site?” If the answer is yes, you have a changelog. If the answer is no, every change to your site is being made to a live system with no record of what came before.
Ask: “If my rankings dropped tomorrow, could you show me exactly what changed in the last 30 days?” Not “we think we updated some pages.” Show me. Dates. Specific changes. Before and after. If they can’t, you’re paying for SEO without being able to diagnose problems when they happen.
Ask: “Where can I see the history of changes to my website?” Not the hosting dashboard. Not the CMS activity log that shows “admin edited page” with no detail. A real history. What was the heading before? What is it now? When did it change?
Version control isn’t a developer luxury. It’s the difference between knowing what happened and hoping someone remembers.
The Pattern
This is the third email in a row where the theme is the same: visibility.
Two weeks ago it was about knowing what to work on first — the difference between being busy and being productive. Last week it was about reducing friction — stopping the dashboard tax from eating your day. This week it’s about knowing what changed.
The thread connecting all three: a business that can see itself makes better decisions than one that can’t. See what needs doing. See the tools without friction. See what changed and when.
Most of the expensive problems I’ve seen in twenty-six years of digital work come down to the same root cause: someone couldn’t see what was happening in their own business. The tools existed. The data existed. The connection between them didn’t.
Tony Cooper
We Build Stores
tony.cooper@webuildstores.co.uk
07963 242210
P.S. Every client website I manage has a full version history from day one. When rankings move, we don’t guess — we look. If your current web provider can’t show you a changelog of what’s been done to your site, that’s worth a conversation. Reply to this email and I’ll show you what a proper website history looks like.
