Website design: plan a site that helps people decide

What should a business website do?

A business website should help the right visitor understand your offer, decide whether it fits and take a clear next step. Design and development support that job through structure, writing, accessibility, performance and reliable forms. A beautiful homepage cannot make up for missing service information or an enquiry that never reaches your team.

Begin with the visitor’s task. A homeowner comparing a repair service needs different information from a procurement manager reviewing a supplier. Write down what each person needs to know before contacting you. Those questions should shape the pages before colours and animation become the main discussion.

Plan the page structure around real decisions

Give each page a clear purpose and connect it to the next useful step. A small service business might need a homepage, focused service pages, evidence of its work, an about page, helpful resources and contact details. Add more pages only when the reader’s question changes enough to deserve one.

• Homepage: establish what the business does, whom it helps and where to begin.
• Service page: explain the problem, scope, process, fit and next action.
• Proof: show approved examples with enough context to understand them.
• Resource: help a reader make a decision or complete a task.
• Contact: explain what happens after the enquiry and collect the information needed to respond.

Use customer language in navigation. Visitors should not have to learn an internal department name to find a service. If a topic is already covered well, improve and link that page instead of creating a competing version.

Write and prototype before building everything

Test the order of information with a simple prototype before committing to a full build. The Design Council’s Double Diamond separates exploring a problem from developing a solution. Applied to a website, that means understanding visitor needs before polishing a chosen layout.

Draft the headline, explanation, evidence and action for one important page. Ask someone unfamiliar with the business to find a specific service, explain its fit and start an enquiry. Watch where they hesitate. “It looks nice” is useful feedback about appearance, but it does not tell you whether the page helped them complete the task.

Make the page usable beyond one screen

Readable type, clear headings and usable controls are part of the product. Check keyboard navigation, focus indicators, form labels, contrast and content order. Do not rely on colour alone to explain an error or a selected option. The W3C page-structure tutorial explains why semantic regions and logical headings help people navigate.

Use actual content at mobile sizes. A neat three-word placeholder can hide the wrapping problems caused by a real service name. Test long headings, menu items, tables, errors and confirmation messages. Allow text to grow without clipping. SF system fonts work naturally on Apple devices; a sensible fallback stack should remain readable on other systems.

Performance matters too. Google’s Web Vitals guidance distinguishes loading, responsiveness and visual stability. Review real visitor data when available alongside lab testing. A single lab score is not a guarantee that every visitor has a good experience.

Use a launch checklist that includes ownership

A launch is complete when the page works and the business can operate it. Confirm the following before redirecting traffic to the new website.

1. Test every main enquiry journey, including validation and the message received by your team.
2. Check internal links, mobile navigation, downloads and contact details.
3. Give important pages unique titles, descriptions and correct canonical URLs.
4. Plan redirects for changed URLs so existing visitors and links reach the right destination.
5. Confirm domain, hosting, analytics and administrator access belong to the right business accounts.
6. Keep a rollback or restoration plan and assign a person to monitor the launch.

For form routing, use our website-to-CRM guide. For ongoing care, read website management basics.

What changes the scope and cost?

Page count is only one factor. Research, copywriting, original photography, booking or payment integrations, migration and ongoing editing needs can change the work substantially. Ask what is included in revisions, accessibility checks, content entry, training and post-launch support.

Choose the smallest build that supports the business’s real tasks. A custom portal may be justified by a complex workflow; a standard website may be a better fit for a business that needs clear information and dependable enquiries. Maqtrix’s website and landing-page service starts with the purpose and scope of the page.