What a business website needs before it goes live

A website can look finished while the business behind it is still unprepared for the first enquiry. The photographs are in place, the menu opens and the homepage reads well—but nobody has checked where a request goes, who responds or whether a customer can complete the form on a phone.

Before launch, think less about ticking off pages and more about completing the customer's journey. Here is a practical checklist for a business website, whether it is your first site or a replacement for something you have outgrown.

1. Decide what a visitor should do next

Start with one useful action. That might be requesting a quote, booking a consultation, viewing a catalogue or buying a product. It does not need to be the same action on every page, but each important page should make its next step clear.

A manufacturer could show recent work, explain the types of orders it accepts and invite a customer to submit quantities and requirements. A service business might explain its coverage area before asking for an appointment. These are examples, not rules for every business.

Write down the primary action and what information the customer needs before taking it. This becomes a better test of the page than whether it has enough decorative sections.

2. Gather the information that removes uncertainty

A customer should be able to understand what you offer, who it is suitable for and how to get started without contacting you for every basic detail.

Check the essentials: accurate service descriptions, real contact details, relevant project photographs used with permission and any important limits such as service areas or minimum order quantities. If pricing depends on a specification, say what affects the quote rather than publishing an invented starting price.

Project images are especially useful when they explain something. A short caption describing the material, purpose or scope is more informative than an unexplained gallery of attractive pictures. Avoid presenting stock imagery or generated illustrations as work you completed.

For search visibility, useful original content should take priority over filling pages with repeated keywords. Google's people-first content guidance supports that approach; it does not guarantee a ranking or a particular amount of traffic.

3. Test the enquiry, not just the button

Send one clearly marked test enquiry through the public website. Check that required fields are sensible, mistakes are explained and the customer sees a confirmation after submission.

Then follow the request on the business side. Was it saved? Did the notification reach the intended destination? Is there a record to refer to if the email is delayed? Does the person receiving it have enough information to take the next step?

Avoid collecting everything you might possibly want. Name, contact details and the information needed to assess the request are usually a better starting point than a long form full of mandatory questions. Do not place passwords, identity documents or payment-card details in a general enquiry form.

Agree who owns the inbox and how another person can take over when they are unavailable. A form without a response process is an unfinished workflow.

4. Review it on a real phone

Open the site on a phone and try to use it, rather than only shrinking a desktop browser. Read the headline, open the menu, follow a service link and complete the form. Check that text is readable, controls are easy to reach and important content is not hidden behind an overlay.

Also test with a keyboard. You should be able to move between links and fields, see where focus is and close a menu without a mouse. W3C's accessibility design tips highlight readable contrast, labelled fields, clear feedback and consistent navigation. These are practical checks, not a claim that a quick review certifies a site as accessible.

Look at the site on a slower connection too. A large image that looks impressive in the studio may be frustrating when a customer is trying to find a number in a parking area.

5. Confirm ownership and recovery

Know who controls the domain, hosting account, source files and important third-party services. Keep access in business-controlled accounts where possible, with appropriate protection and a way to recover access if a person leaves.

Ask what is backed up and how restoration is tested. A copy on the same server is useful for reversing an update, but it is not an independent recovery plan if the server itself is lost. Define who handles updates, expired services and unexpected downtime.

The handover should explain how routine content changes are made. You should not need to guess how to replace a project photograph or remove an expired special.

6. Make a small plan for after launch

Choose a few meaningful checks: whether enquiries arrive, whether people can complete the main action and whether contact details and offers stay current. Page views can be useful context, but they are not the same thing as qualified enquiries or sales.

Set a reminder to review the site after the first few weeks. Real questions from customers often reveal information that needs to be clearer. Improve those gaps before adding features simply because another website has them.

Before approving launch, ask one final question: can a customer understand the offer, take the next step and receive a useful response? If the answer is yes, you have a stronger starting point than a website that merely looks complete.

Avuno builds websites and digital experiences around that journey. Tell us about your project if you want to work through the requirements before deciding what to build.