There is a particular kind of chaos that comes from asking thousands of separate public bodies to independently reinvent the same wheel. That is more or less what happened when British local government went online. UK council websites history is, in the most generous reading, a story of civic ambition outrunning technical capacity. In a less generous reading, it is a catalogue of clip-art logos, broken PDF links, and planning application search forms that have not worked since Internet Explorer 6 was current.
I’ve spent a fair amount of time digging through archived pages from the Wayback Machine, and the experience is genuinely strange. You find the ghost of Wolverhampton Borough Council circa 1997 sitting alongside a half-finished welcome message from a Wiltshire district that clearly ran out of either budget or enthusiasm sometime around the second paragraph. The early web was full of half-finished things, of course, but local government managed to be half-finished in ways that felt particularly poignant, because the ambition was real.
How councils first got online: enthusiasm before expertise
The early to mid 1990s produced a handful of pioneering UK council websites, most of them driven by a single enthusiastic officer rather than any strategic plan. Oxfordshire County Council is often cited as one of the earliest, going online around 1994 or 1995. Cambridge City Council followed. These were not the product of IT departments with large budgets; they were the product of someone, usually in a library or information services role, who had discovered the web, understood what it might mean for public communication, and spent a few evenings learning HTML from a Netscape guide.
The pages they produced were, by any objective measure, extremely limited. A few lines of text about council services. A telephone number. Sometimes a photograph of the town hall, saved at a resolution that made it look like it had been pressed through a sieve. But they were there, publicly accessible, and they represented something genuinely new: the first attempt to give ordinary residents a direct digital route into local government without picking up the phone.
The problem was that nobody coordinated any of this. England alone has hundreds of councils, county councils, district councils, unitary authorities, London boroughs, metropolitan boroughs, and each one was effectively operating as an independent republic of web design. There was no shared template, no shared guidance, no shared anything. The Local Government Association existed, but digital standards were not exactly high on the agenda when most councils were still arguing about whether they needed a website at all.
The budget problem, and the workarounds people invented
Money was the constant constraint. A county council in the late 1990s might have allocated a few thousand pounds to its website, which in practice meant either paying a local web design agency (often a two-person operation working from a bedroom in a market town) or handing the job to whoever in the building already knew how to use a computer. Both approaches produced results that are, to put it charitably, of historical interest.
Some councils turned to their local universities for help, a connection explored in the broader story of how British universities raced to build their own first websites, a competition that occasionally spilled over into partnerships with the surrounding civic infrastructure. A computing department might build a council site as a student project. The site would then be handed over, with minimal documentation, to a council officer who had no idea how to update it.
By the early 2000s, the pages were frequently out of date. Contact details from 1999 sat next to news items about events that had already happened. Downloadable forms linked to files that no longer existed. One persistent trope in local government web history is the council that built a genuinely impressive site for the year 2000, sometimes tied to millennium funding, and then more or less left it alone for the next five years while the rest of the web moved on around it.
The proliferation of microsites and the navigation nightmare
Somewhere around 2003 to 2007, a new problem emerged. Councils had not replaced their original websites so much as grown things around them. Tourism departments had their own separate sites. Economic development teams had their own sites. The planning department occasionally had its own site. Libraries had their own site. There was rarely any consistent design, rarely any shared login, and almost never any coherent information architecture that told a resident where, exactly, they should go to renew their parking permit or report a broken pavement.
I’ve seen archived versions of council homepages from this era that had more than forty navigation links on the front page. Forty. The logic, presumably, was that if you put everything on the front page, residents would find what they needed. The actual result was that nobody found anything. You would click what seemed like the right link and end up in a PDF that had been scanned sideways. Or you’d hit a Flash-based interactive map that required a plugin version nobody had installed since 2005.
The commercial web had exactly the same problems in its early years, of course. Portal sites like LineOne, the short-lived BT and News International joint venture, tried to solve internet navigation by putting everything in one enormous index and hoping users would browse their way to what they wanted. It didn’t work for portals, and it didn’t work for council websites either. But where a commercial portal could be shut down and replaced, a council website carried the weight of legal obligation. Planning notices had to be published somewhere. Statutory consultations needed to be accessible. You couldn’t just start again.
Government gateway, e-government and the false dawns
The Blair government was genuinely interested in digital public services. The e-government agenda of the early 2000s set an ambitious target: all government services available online by 2005. Local councils scrambled to hit the target. The result was a wave of transaction forms that technically existed online but were almost impossible to use, a council tax payment page that redirected you to a third-party payment processor with its own login, or a benefits application that required you to post a printed confirmation afterwards anyway.
The Government Gateway, launched in 2001 by the Office of the e-Envoy, was meant to give citizens a single point of access to public services. In practice, local councils often built parallel systems that didn’t connect to it. Each council had signed contracts with different software suppliers, Civica, Capita, IDOX, and dozens of smaller firms, and those suppliers had no particular incentive to make their products talk to each other. If you’d like a sense of what the commercial advertising landscape looked like around this period, some of the early revenue models explored by local authority web teams included attempts to buy banner ads UK websites services as a potential income stream, though very few councils actually pursued it in any sustained way.
The BBC covered the persistent problems with council digital services extensively through the 2000s and into the 2010s, noting that the gap between stated ambition and actual usability remained wide even as broadband made the connections faster. Faster access to a confusing website is still a confusing website.
How the road to GOV.UK design standards actually happened
The transformation came slowly and unevenly. The Government Digital Service, established in 2011, produced GOV.UK in 2012, a genuinely radical simplification of central government’s online presence. Its design principles were plain, its language was plain, its navigation was plain. It worked. And it set a benchmark that local government could see but had no obligation to meet.
The GOV.UK design system, published openly and freely available to any public body that wanted to use it, gradually influenced local council design, but the uptake was patchy. Some forward-looking councils adopted its principles quickly. Others were locked into long contracts with suppliers who had their own design systems and no interest in change. A unitary authority in the north of England might have a clean, accessible, well-structured website by 2018 while a neighbouring district council still had a site that pre-dated responsive design, rendering as a tiny column of text on a mobile phone.
Full adoption of consistent design standards across local government is still, in 2026, an unfinished project. The Local Digital Declaration, signed by hundreds of councils, committed them to building services that meet user needs and use shared standards. Progress has been real. But the digital graveyard is not entirely cleared. If you know where to look in the Wayback Machine, you can still find the ruins, the 1998 homepage for a market town council, the millennium microsite that nobody ever updated, the planning portal that required ActiveX controls and therefore has not functioned on any modern browser for roughly fifteen years. They are still there, perfectly preserved, a record of what civic digital ambition looked like when it had more hope than knowledge.
There is something almost moving about it, in the way that old maps are moving, not because they are accurate, but because they show you how people understood their world at a particular moment. UK council websites history is really a history of public sector institutions trying to understand a technology that was changing faster than any procurement cycle could accommodate. They got a lot wrong. They also, quietly, got some things right.
Frequently Asked Questions
When did UK local councils first build websites?
A small number of pioneering councils went online as early as 1994 and 1995, with Oxfordshire County Council and Cambridge City Council among the earliest. Most councils followed through the late 1990s, often driven by a single enthusiastic officer rather than any coordinated strategy.
Why were early council websites so difficult to use?
They were built without professional web design expertise, consistent standards, or adequate budgets. Many were created by local agencies or internal staff with limited training, and then left largely unmaintained. The proliferation of separate microsites for different departments made navigation extremely confusing for residents.
What was the e-government target of 2005 and did councils meet it?
The Blair government set a target to have all government services available online by 2005. Most councils technically met the target by publishing online forms, but the actual services were often unusable in practice, with disconnected payment systems, paper confirmation requirements, and incompatible software from different suppliers.