Where AI earns its place on a small website

AI is everywhere in website pitches right now. Some of it is genuinely useful for a small business or community organisation. Some of it adds weight, cost and risk to a site that was working fine. This note is how we tell the difference when a client asks us to “add some AI”.

The short version: we add AI where it saves a real person real time, and we leave it out where it mostly adds kilobytes and things to go wrong.

Start with the job, not the tool

Every feature on a website has a job. A booking page gets people booked. A services page helps someone work out whether you can help them. Before we talk about AI at all, we ask what job is currently being done badly, and by whom.

If your team spends hours answering the same five questions by email, that’s a job. If visitors can’t find the right page, that’s a job. “We should have a chatbot because everyone has one” isn’t a job, it’s a feature looking for a reason.

Where AI genuinely helps

Drafting, with a human editor

The most useful AI on most small sites never appears on the site at all. It sits in the workflow behind it. Drafting a first version of a page, summarising a long policy into plain language, suggesting alt text for a batch of photos, or turning meeting notes into an update for supporters: these are good uses, as long as a person who knows the subject edits the result before it’s published.

What you publish should still sound like you and still be correct. AI is a fast first draft, not a fact-checker.

Helping people find things

Small sites often have useful information buried three clicks deep. A better on-site search, one that understands “how much does it cost” means the pricing page, can help more people than a flashy homepage. Done well, it runs only when someone searches, so it adds nothing to the weight of every other page.

Answering the questions you already answer

A well-structured FAQ, written by you and kept up to date, beats a chatbot for most organisations. Where a chat assistant does make sense, it should answer only from your own content, say clearly that it’s automated, and hand over to a person whenever it isn’t sure.

Checking your work

AI tools can help spot accessibility problems, unclear wording and broken structure before they reach your visitors. They don’t replace testing with real people and assistive technology, but they catch a lot of small issues early.

Where it adds weight and risk

Heavy widgets on every page

Many chat and personalisation tools load large scripts on every page, for every visitor, whether or not anyone uses them. That makes pages slower, especially on older phones and patchy connections, and it means more energy used for every visit. If a feature is used by a small share of visitors, it shouldn’t slow the site down for everyone else.

Generated filler

Pages written by a model and published without care tend to read the same way: long, vague and confident. Visitors notice, and so do search engines. A short page that answers the question is worth more than a long one that circles it.

Privacy and trust

Anything a visitor types into an AI feature may be sent to a third-party service. That needs to be clear in your privacy policy, and some organisations, particularly in health, community services and education, need to think carefully before collecting anything at all. Trust is hard to win back once a visitor feels their information was handled carelessly.

Our rule of thumb

Before we add an AI feature to a client site, we ask four questions:

• Does it do a job that a real person currently does slowly or badly?
• Can it load only when someone needs it, instead of on every page?
• Is it clear to visitors when they’re dealing with an automated tool, and what happens to their information?
• Will someone on your team own it, check it and keep it current?

If the answer to all four is yes, it’s probably worth building. If not, there’s usually a simpler, lighter way to do the same job.

Where to start

If you’re curious about AI for your website, start behind the scenes: use it to help draft, tidy and check your content, and keep a person in charge of what goes live. Then look at your enquiries and your site search to see what visitors are actually struggling to find.

If you’d like a second opinion on what would genuinely help your site, tell us what you’re working on. We’ll give you honest advice, including when the answer is “you don’t need it”.