Content Lexicon.

Website

In one line

The part of the web an organisation owns outright, where its content can inform, educate, persuade and support, and where anything said about it elsewhere can be checked.

A website is one or more pages and services published under a domain an organisation controls. It may include search, forms, tools, transactions, documentation and downloadable data.

A microsite is a website with a narrow purpose. An intranet is a website for an organisation’s own staff. A profile on a social platform is not a website: the platform controls how it works, who sees it and whether it remains available.

That control makes the website the natural home for the definitive version of things: the organisation decides what goes where, how deep it goes, how long it stays and which version is current.

Social feeds, newsletters and press coverage carry messages towards people, and the website is where they arrive to find out what is true and use what is on offer.

Why it matters for content

A website is better understood as the frontend of a connected content system rather than as a technical solution or a pile of documents with the same header.

Content can inform, educate, persuade, entertain or support. Many websites stop at the first: they describe the organisation’s services rather than providing them. A page explaining that a helpline exists is information about support; a page that helps someone through the first hour after a diagnosis is support. Software documentation is half the product. An evidence library is how a think tank gets quoted.

A website is also where many buying decisions happen, as well as actual purchases. People use a website’s content to discover products and services, understand what they will get, compare their options and judge whether what they will receive will deliver what it promises.

The cycle of a full website redesign every four or five years often rebuilds the container and keeps the content model, so the new site is a slightly better version of the old one. What changes the result are solid content foundations and the continuous, unglamorous work: an owner for each section, review dates, pages that work for disabled people and on a weak phone signal, and a reason for every page to exist. Without it, a website gradually becomes an archive of organisational indecision presented as current information.

How AI changes the picture

AI summaries and assistants can answer some questions without a visit to the website. That changes what a visit is for: people may arrive to verify something, explore it in depth or use a service that an answer alone can’t provide.

The website remains an important source of information, but its direct value also lies in experiences the organisation can offer. An interactive exhibition guide, for example, could let a visitor compare objects, listen to a curator and choose a route around their interests. A summary can introduce the exhibition; the website can help someone explore it.

As AI opens up cheaper, faster software development, the boundary between website and software will become increasingly blurred. This will speed up a trend that was already happening: websites will become places people and agents do things (apply, join, create), as much as opportunities to read and absorb. Expect more interaction and less broadcasting.

Questions people ask

Do we still need a website if people get their answers from AI?

More than before, in one respect: the answers are made from somewhere, and your own site is the version you control. What changes is the job. Fewer people browse, and the ones who come are checking a claim, going deeper or doing something, so those pages deserve care.

Our traffic is falling. Is the website failing?

It may be doing better. Traffic was always a proxy. Look at completions instead (applications, donations, bookings, downloads of the full report), at questions the support team gets that the site should have answered, and at what AI assistants say about you when asked. A site with a third fewer visits and the same number of applications is doing more with less.

How often should we redesign?

The container rarely, the content continuously. A sound site can go five years or more between rebuilds if someone is reviewing, merging and retiring pages every month. Rebuilding every few years without changing how content is owned and maintained mostly moves the same problems to a new address.

Should every piece of content be a web page?

No. Some material belongs in a service, a tool, a dataset, an email or an accessible document. Choose the format around what people need and who’ll maintain it, not habit.

Learn more

Type a term, or a word from its definition.⌘K opens this from any page.