A few years ago, the usual way to improve a website was to redesign it, launch it with a flourish and wait to see whether people liked it. In 2026 that habit is fading in the better-run web teams. More of them now begin with something far less glamorous: a measured snapshot of how the current site behaves. This state-of-the-craft piece looks at why the benchmark-first mindset is spreading in content management and digital marketing, and what a sensible starting snapshot contains.<\/p>\n
Picture a small agency that rebuilds a client’s website. The new design is cleaner, the pages are lighter, the client is delighted at the launch meeting. Three months later the client asks the obvious question: did it work? The agency scrolls through analytics and realises that nobody saved the figures for how long visitors took to reach the contact form on the old site, how many steps the enquiry journey needed, or how editors felt about the publishing workflow. The new site might be better. Nobody can prove it.<\/p>\n
That awkward silence is the origin story of the baseline habit. It is not a new idea, but content teams are finally treating it as a normal first deliverable rather than a courtesy.<\/p>\n
The best ones are modest. They describe three things in plain language.<\/p>\n
Teams add qualitative notes too: the questions visitors keep asking, the pages editors dread updating, the complaints that recur in support messages. None of this needs exotic software. It needs a calendar entry that says “record the starting point” before the first line of new code.<\/p>\n
Three pressures push in the same direction. First, clients are more sceptical of redesigns that promise vague uplift. Second, teams are juggling more moving parts, from content systems to marketing tools, and it is harder to tell which change caused which effect. Third, sites are rarely finished: they are tuned continuously, which means every adjustment needs a fair comparison point. A baseline that is updated with each round of changes works like a ledger of what was tried.<\/p>\n
The planning stage is where the habit pays off most. A walk-through on preparing a company website before development begins<\/a> already treats upfront decisions as the heart of the project, and a recorded starting point fits naturally into those early steps.<\/p>\n Even teams that embrace the idea trip on a few predictable points. Some measure only on a quiet day, so the later figures look worse by comparison. Some change the measuring method halfway, comparing apples with oranges. Others take the baseline after a few quick fixes have already gone live, which quietly moves the starting line. The cure is boring and effective: write down the method, take several readings, and lock the record before anyone touches the site.<\/p>\n There is also the temptation to measure what is easy rather than what matters. A visitor-count graph is handy, but if the goal is enquiries, the baseline needs the enquiry journey. Pick the result you want to move, then measure that.<\/p>\n Another reason the habit helps is that it exposes structural problems early. When you map the existing journey, you often find missing or redundant pages. A guide on the pages a business site should carry<\/a> offers a useful checklist, and holding it against your recorded journey shows where the gaps are before a designer has been briefed.<\/p>\n First impressions deserve the same treatment. Rather than debating taste, teams record how the current landing page performs and what visitors do on it, then judge a new version against that. A look at how a homepage shapes what customers think<\/a> explains why that page carries so much weight, which is exactly why it deserves a careful before-picture.<\/p>\nThe mistakes that still catch people out<\/h2>\n
Structure comes before polish<\/h2>\n
Planning across borders: a parallel from another field<\/h2>\n