Your Website Changes Once a Year

Think about what changed in your business over the last twelve months. A service you stopped offering in that form. A type of client you now take and did not before. A price structure that moved. A person who left and a person who joined. A question every prospect started asking that nobody asked two years ago.

Now think about what changed on your website. For most companies the honest answer is a phone number.

The gap between the business and the page

A website gets treated as a project with an end date. It is commissioned, built, approved and launched, and from that moment it describes the company as it was in the month the copy was signed off. The business keeps moving. The page does not.

The gap is invisible for a while and then it is not. A prospect reads a service page describing work you no longer do that way, or lands on a team page showing two people who left last year, or finds nothing at all about the thing you now spend most of your week on. None of them tell you. They form a view about how current the whole operation is, and they close the tab.

What it costs inside a sales conversation

The sharpest version of this shows up after a good meeting. A prospect you met on Thursday goes back to the site on Friday to check one thing, and finds a version of the company eighteen months behind the one they just spoke to. They do not conclude that the site is out of date. They conclude that one of the two is not quite real, and the follow-up they were going to send waits a week.

The same thing happens to a referral. Somebody recommends you, the person they recommended you to looks you up, and the page answers a question nobody asked while staying silent on the one they actually have. A referral is the warmest lead you ever get, and it is routinely spent on a page written for a different business.

Why the page stays frozen

Not budget, usually. The retainer that covers small changes is rarely the constraint. The constraint is that a change is a request to somebody else.

Somebody has to write down what they want, send it, wait, review what came back, explain the part that was misunderstood, and wait again. For one sentence. A change that takes four minutes of actual work takes nine days of calendar time and three emails, and after that happens twice nobody bothers. The correction joins the list of things to do when there is time, and there is never time.

The second constraint is that nobody owns it. Whoever handles marketing assumes the agency is watching. The agency waits to be told. The owner notices something wrong once a quarter and mentions it. That one thing gets fixed while nine others stay wrong.

The third is that nobody knows what is wrong. A site of forty pages, written over three years by four people, has no inventory. Nobody can tell you which pages still mention the old pricing or the discontinued service, so the audit never starts, because it has no shape.

What AI changed about this

The audit now takes minutes instead of a week. A system can read every page you have and compare it against a current description of what the business does. What comes back is a list. These six pages describe a service you no longer sell. These four name people who left. These nine answer a question nobody asks any more. This one contradicts that one on your turnaround time. That used to be a person reading forty pages with a notepad, which is precisely why it never happened.

Drafting changed too. The reason a correction waits nine days is that somebody has to write it in the company's voice. A system holding your actual positioning can produce the replacement paragraph immediately, and a person then spends ninety seconds approving it instead of thirty minutes writing it. The bottleneck moves from writing to deciding, which is where it belongs.

And the questions that should drive the page are now visible. What people ask your sales team, what they type into your search box, what they email after reading a proposal, can be gathered and grouped without anybody doing it by hand. The page stops being a description of your company and starts being an answer to what people actually want to know.

What AI will not do for you

It will not decide what you sell. Every useful change to a website starts with a decision the business made somewhere else, and a model reading your old pages will faithfully reproduce the positioning you are trying to leave behind.

It will not keep your facts true. A claim about your turnaround time, your certifications or the size of your team is only correct if somebody who knows checks it. Generated copy is confident about things it cannot verify, and a confident false claim on a service page is worse than an outdated one.

And it will not fix a site nobody can edit. If every change still has to pass through a queue, faster drafting just makes the queue longer.

What to build instead

Put the content where the people who know things can change it. If the person who knows the service changed cannot alter that page themselves in under five minutes, the page will go stale no matter who built it.

Keep an inventory. One list of every page, what it is for, when it was last touched and who owns it. Most sites cannot produce this, which is the whole problem in one line.

Decide who signs off, and keep that list short. Plenty of pages go stale waiting for an approval nobody asked for. Name one person who can change wording without a meeting, and reserve review for claims about price, scope and legal commitments.

Run the comparison on a schedule rather than when somebody notices. Once a quarter, read the site against a current description of the business and produce the list of contradictions. The value is in it being routine.

And separate the two kinds of change. Rebuilding the design is a project. Keeping the words true is an operation. Treating the second as though it were the first is how a site ends up a year behind the company.

We build sites the people running the business can actually change, with the content structured so a correction is an edit rather than a request. See Web Development.