Key Takeaways
- Judge a website by the customer tasks it supports, not just its appearance.
- Use real content and a working enquiry journey when reviewing designs.
- Separate launch blockers from improvements that can wait.
- Assign an owner to content, technical maintenance and measurement after launch.
A good business website helps the right person understand an offer, judge whether it fits and take a useful next step. Attractive design supports that work; it cannot replace missing prices, confusing service descriptions or a broken form. The practical test is whether a visitor can complete the task that brought them there.
Use these sixteen checks when commissioning a site, reviewing a redesign or deciding what to improve first. For each one, record a specific page, an observed problem and the person responsible. A screenshot of a fault or an unanswered customer question is more useful than a general request to make the website better.
1. A clear purpose
Write one sentence describing the site's main job. A service business might need qualified project enquiries; a retailer needs customers to find and purchase suitable products. A support site may need people to solve a problem without contacting the team. Those are different briefs.
Choose a primary action for each page. The homepage can help visitors choose a route, while a detailed service page can invite a scoped conversation. Avoid making every page sell every service at once. Ask someone unfamiliar with the business to explain the offer after reading the opening section.
2. Customer-led navigation
Use labels customers recognise rather than internal department names. Check that a person can move from a broad problem to the relevant service, then to evidence and contact. Important pages should not depend on knowing an unusual menu label.
Our GTS Reading project documents a service, industry and fleet structure around a transport quote journey. It illustrates a navigation decision, not a measured increase in sales. For an online shop, the equivalent task may be choosing a product category or finding delivery information.
3. A useful mobile experience
Test the actual page on a phone, not only a reduced desktop window. Open the menu, compare options, read a long heading and use the form with the on-screen keyboard visible. Check that a fixed banner does not cover the action you need.
Responsive layout is the beginning of this review, not its completion. An image can fit the screen while its text becomes unreadable. A table may need horizontal scrolling with a clear cue. Keep the same essential service information available across screen sizes.
4. Content that answers buying questions
Explain who the service is for, what is included, what is not included and what happens next. Use examples to clarify unfamiliar terms. If a price depends on scope, describe the factors instead of hiding behind an unhelpful request to call.
Update content when facts or customer needs change. A weekly publishing quota does not make an inaccurate page useful. Google's people-first content guidance is a useful editorial reference; our recommendation is to improve the page that leaves a real question unanswered.
5. Performance on important journeys
Check the homepage and representative service, article and checkout pages. Test initial loading and what happens after the visitor starts interacting. A fast first screen can still conceal a slow booking widget or an unresponsive menu.
Keep the measurement conditions with the result: device, connection, page and date. The website speed diagnosis guide explains how to separate a hosting delay from oversized media or expensive scripts. Do not purchase a rebuild solely because one automated test was slow.
6. Search foundations
Important pages need crawlable links, descriptive titles, useful main content and appropriate indexing settings. Confirm that the live sitemap contains the canonical pages you want discovered. Staging settings should not accidentally travel into production.
Do not measure this with keyword repetition. Match the page to a specific customer question, and use that language naturally in the title and opening answer. Technical access makes discovery possible; it does not promise that Google will index or rank every page.
7. Clear, honest calls to action
Name the action accurately: request a quotation, send a brief or book a consultation. Explain whether there is a cost and what response the customer can expect, using a commitment the business can actually meet.
Offer a lower-commitment route where useful, such as reading a case study before enquiring. Do not invent deadlines or scarcity. A button should be noticeable because of hierarchy, contrast and wording, not because it makes an unsupported promise.
8. Reliable hosting and account control
Know who controls the domain, hosting and renewal payments. Keep recovery details with the business, and agree who responds if the site becomes unavailable. A supplier's uptime marketing is not the same as a response commitment in your contract.
Ask about backups, restoration and supported software. HTTPS protects the connection but does not prove that every part of a website is secure. The website maintenance guide turns these responsibilities into checks you can assign.
9. Measurement that reflects the business
Define a successful enquiry before adding tracking. A form submission, telephone-link click and qualified sales opportunity are different events. Test the collection process and reconcile it with actual messages received.
Record consent and tracking changes alongside releases. Analytics tools can count different populations, so their totals need not match. Avoid interpreting a quiet day as a content failure without checking date ranges, incomplete data and the site's own enquiry records.
10. Consistent branding
Use a recognisable set of type styles, colours, buttons and image treatments. Consistency helps visitors understand which elements are headings, controls and supporting information. It also makes future pages easier for the team to maintain.
Ask the designer to show the system with difficult real content: a long service name, an uneven project image and a detailed table. A presentation made only from short placeholder text can hide problems that appear immediately after handover.
11. Evidence customers can assess
Show relevant work with the brief, decisions and delivered scope. Use testimonials with permission and make their context clear. If an outcome has not been measured, describe what was delivered without inventing a percentage improvement.
One specific case can be more helpful than a wall of unexplained logos. Place proof near the service or claim it supports. Keep a source record so a future editor knows which client approved the wording and whether a result can still be used.
12. Practical contact information
Make email and telephone details readable and usable. Explain the service area honestly and distinguish a registered office from a customer-facing location. A map should help a visitor, not suggest premises that do not exist.
Check contact details in the footer, contact page, proposals and major business profiles. Consistency is primarily about customers reaching the right business. Keep a nominated owner for changes so an old telephone number does not survive in forgotten templates.
13. Forms that work beyond the submit button
Ask only for information needed at this stage. Explain required fields and errors in plain language. Preserve entered information after a recoverable error, and make the success state unambiguous.
Test receipt, not just the on-screen confirmation. Check spam handling, attachment limits and the destination inbox. A test submission should be clearly marked and removed from lead reporting where appropriate. Keep an alternative contact route for people who cannot use the form.
14. Accessibility in real tasks
Use a keyboard to navigate and operate controls. Check labels, focus visibility, headings and image descriptions. Test zoom and readable text rather than assuming that a fashionable visual style is accessible.
The W3C accessibility introduction explains why this work matters. Automated tools can help find issues, but do not establish full conformance. Include manual task testing in acceptance and agree what specialist assessment is required for the project.
15. Readable structure
Give each page one clear subject and descriptive sections. Put the direct answer before lengthy background. Use lists for repeated checks and tables for genuine comparisons, not as decoration.
Our UX and UI buying guide distinguishes the underlying journey from its visual treatment. Ask whether a visitor can scan the page and predict where to find scope, evidence and the next step without reading every sentence.
16. A realistic ownership plan
Launch is a handover, not the end of responsibility. Assign owners for content accuracy, renewals, software, enquiry delivery and measurement. Agree how urgent problems are reported and how changes are tested before release.
Maintain accurate privacy and other required business information with suitable professional advice where needed. Do not copy another company's policies. Turn this checklist into a short backlog: fix broken customer tasks first, then confusing information, then lower-risk refinements.
If you need help deciding between improvements and a rebuild, our website audit and consultation can establish the brief. Custom website design is appropriate when the existing structure cannot support that brief. Send us the pages and tasks that are causing problems, and we can discuss a proportionate next step.
Frequently Asked Questions
What is the most important feature of a business website?
A clear route from the customer's question to a useful outcome. For a service business, that usually combines understandable service information, credible evidence and an enquiry process that actually reaches the team.
Do I need a new website to fix these problems?
Not necessarily. Content, navigation, forms and performance can often be improved on the existing platform. Commission a rebuild when a documented limitation makes those changes impractical, not simply because the design feels old.
How often should website content be reviewed?
Review important pages when services, prices, staff, evidence or delivery arrangements change. Set a periodic ownership check as well, but do not alter dates or publish filler just to appear active.
Can an automated audit tell me whether the site is good?
It can identify useful technical signals, but it cannot fully assess your offer, client evidence or enquiry quality. Combine its findings with manual customer-task testing and a review of actual business enquiries.
What should be checked before approving a launch?
Test representative pages on mobile and desktop, forms through to receipt, essential integrations, indexing settings, redirects, accessibility and account ownership. Record unresolved issues and who will deal with them before approving release.
