Build the Boring Pages: The Website Back Room That Earns Trust

Here is an unpopular opinion: most website projects spend far too long on the homepage and almost no time on the pages that actually do the quiet work. The homepage gets the mood board. The back-room pages get copied text from a template, a broken link and a date from three years ago.

That is a mistake. The unglamorous pages are where trust is either confirmed or quietly eroded. A customer who cannot find the returns address does not email you to say the homepage looked nice. They leave. A visitor who hits a dead-end 404 does not admire the animation. They wonder if the site is still running.

None of this needs a lawyer on speed dial for the basics. It needs plain English, a bit of honesty and someone to check the links.

Delivery and returns: say the awkward bits early

If you sell physical goods, this page is not legal decoration. It is a customer service page. Say what delivery costs, how long it takes, who you use, whether tracking is included and what happens if something goes missing. UK customers want to know about Highlands and Islands, Northern Ireland and click-and-collect if those apply. Do not make them guess.

For returns, spell out the window, the condition, who pays postage and where to send it. If you sell personalised, perishable or made-to-order items, say clearly which items are excluded. If something is faulty, say what you will do. Do not bury this in a wall of terms and conditions and call it done. A short table beats a paragraph of fog.

Common UK mistake: copying an American template that talks about 'shipping', 'ZIP codes' and a returns policy that does not match UK consumer expectations. Another: hiding the returns address in the footer. Put the useful facts where a stressed person can find them in ten seconds.

Accessibility statements: a promise with a date

An accessibility statement is not a badge. It is a short, honest note about what you have done, what still needs work and how someone can report a problem. Say which standard you are aiming for, such as WCAG 2.2 AA, and be careful with the phrase 'fully accessible'. Very few sites are. If you know a PDF is not tagged properly or a form has an issue, say so and give a contact route.

Include a date and an owner. 'Last reviewed November 2026' is more useful than a vague claim that the site is committed to accessibility. UK public sector sites have specific legal duties; small private firms may not, but the commercial case is simple. If someone cannot use your contact form, they cannot buy from you.

Privacy notices: less Latin, more clarity

A privacy notice should tell people what you collect, why you collect it, how long you keep it and who else sees it. That means contact forms, analytics, newsletter tools, payment providers and cookies. If you use a cookie banner, it needs a genuine reject option, not a fake one that makes 'accept all' the only visible button. UK GDPR and PECR are not excuses for impenetrable language.

Write in short sections: who you are, what data you collect, why, lawful basis in plain terms, retention, third parties, your rights and how to complain to the ICO. Link to the notice at the point where you collect data, not only in the footer. If you use a mailing list, say how someone unsubscribes. If you use analytics, say what you measure.

Common UK mistake: a privacy notice that names every possible law but never explains what happens when someone fills in the contact form. Another: a cookie banner with no reject button. That is not a privacy notice; it is a small act of theatre.

Thank-you pages: do not waste the moment

The thank-you page is one of the most underused pages on a small business website. Someone has just done something: sent an enquiry, booked a call, bought a product or signed up. Do not leave them with a lonely 'Thank you' and no next step.

Confirm what happened. Say when they will hear from you. Give them a link to a useful page, a phone number if they need to change something, and a clear note if the message may land in spam. If you sell a service, tell them what happens next. If you sell a product, explain delivery updates. This is also where you can track conversions properly, but the customer should never feel like a data point.

404 pages: help, do not perform

A 404 is not a personality showcase. It is a signpost. Say the page cannot be found, offer search, link to popular pages and give a contact route. If you can, add a way to report the broken link. Do not blame the visitor. Do not use a joke that gets in the way of the fix. A useful 404 can turn a dead end into a sale; a cute one usually just adds friction.

The plain-English test

Read each back-room page out loud. If you run out of breath, it is too long. If you would not say it to a customer in a shop, rewrite it. Use 'you' and 'we'. Use headings and tables. Date the page and name the person responsible for reviewing it. Legal wording has its place, but it should not be the only version a normal human can understand.

The back room is still part of the shop

You would not open a café with a beautiful front counter and a blocked toilet. Do not launch a website with a polished homepage and a returns page that cannot be found. The back-room pages are not the exciting part of web design, but they are part of the experience. Build them properly, write them plainly and check them before launch. Your customers may never mention them. They will notice when they are missing.