A small-business website needs a defined job before anyone chooses a platform, draws a layout or writes a page. “Look professional” and “get more customers” are aspirations, not objectives. A useful objective states who the website is for, what it should help them do and how the business will recognise a worthwhile result.
This guide shows how to set objectives that are practical enough to shape the website and simple enough to measure after launch. The aim is not to create an elaborate reporting system. It is to prevent expensive decisions being made without a clear reason.
Start with one primary business outcome
Choose the most important outcome the website should support during its first year. It may generate qualified enquiries, complete online sales, take bookings, reduce repetitive customer questions, attract suitable applicants or strengthen a referral-led sales process.
Write the objective as a single sentence:
The website should help [specific audience] understand [offer or information], trust the business and complete [primary action].
For example:
The website should help homeowners within 20 miles understand our renovation services, see evidence of relevant work and request a properly described quotation.
This is more useful than “increase conversions” because it identifies the audience, the offer, the trust requirement and the action that matters.
Separate the website objective from the wider business goal
A website can support growth, but it cannot guarantee revenue, rankings or demand. Sales also depend on pricing, availability, reputation, follow-up, market conditions and the quality of the underlying offer.
| Business goal | What the website can realistically contribute |
|---|---|
| Win more local work | Explain services and service areas clearly, provide evidence and make enquiry routes easy to use. |
| Sell more products | Help suitable visitors find products, understand delivery and returns, and complete a reliable checkout. |
| Reduce administration | Answer common questions, collect complete information and direct people to the correct process. |
| Move into a higher-value market | Present the right positioning, examples and qualification criteria rather than showcasing work the business no longer wants. |
This distinction matters when the results are reviewed. A site may be working as designed while a separate commercial problem still needs attention.
Choose a small set of success criteria
Use one primary measure and a few supporting measures. Tracking every available number usually creates more noise than insight.
For an enquiry-led website
- qualified enquiries received;
- enquiries that become customers;
- enquiries outside the service area or unsuitable for the business;
- failed, abandoned or spam form submissions;
- response time after an enquiry arrives.
For an online shop
- completed orders and net revenue;
- gross margin after transaction, delivery and return costs;
- average order value;
- checkout abandonment;
- returns, cancellations and support problems.
For a reputation or portfolio website
- whether referred prospects use the site before making contact;
- whether prospects understand the offer before the first conversation;
- which examples or credentials influence decisions;
- whether the site reduces repetitive questions;
- whether it attracts the type of work the business wants.
Page views, time on page and social reactions may help diagnose behaviour, but they are rarely business outcomes by themselves.
Define what counts before measuring it
“Lead”, “booking” and even “sale” can mean different things to different people. Record the definition before launch.
A qualified enquiry might require:
- a real name and usable contact details;
- a request for a service the business provides;
- a location within the service area;
- a realistic timeframe or budget;
- enough information for the team to respond productively.
Without a definition, a rise in spam or unsuitable enquiries can be misreported as improvement.
Set a baseline and a review period
For an existing site, record current results before making major changes. For a new site, allow enough time to collect a meaningful sample rather than declaring success or failure after a few days.
Use a review rhythm suited to the business:
- Weekly after launch: broken forms, payment failures, booking problems and serious technical errors.
- Monthly: enquiries, orders, quality, response and notable changes in traffic sources.
- Quarterly: pages that help or obstruct the main journey, repeated customer questions and content gaps.
- Annually: whether the original objective still reflects the business strategy.
Seasonal businesses should compare like with like. December may not be a sensible baseline for February, and a one-off campaign should not be treated as normal performance.
Turn the objective into website requirements
The objective should affect what is built. If the primary aim is qualified enquiries, the site may need service-area information, a structured form, trust evidence and clear response expectations. If the aim is online sales, product data, stock handling, payment reliability, delivery, returns and customer support become central.
| Objective | Likely requirements | What to test |
|---|---|---|
| Generate quotations | Service pages, qualification questions, proof, contact routes | Can a suitable visitor send enough information without confusion? |
| Take appointments | Availability, booking rules, confirmations, cancellations | Can a real booking be completed and managed correctly? |
| Sell products | Product information, checkout, delivery, returns, support | Can an order be placed, paid, confirmed and fulfilled safely? |
| Support referrals | Positioning, relevant work, credentials, process, contact details | Can a referred prospect verify fit and credibility quickly? |
Avoid objectives the website cannot prove
Be cautious with targets such as “rank number one”, “double revenue” or “achieve a 5% conversion rate” when there is no baseline or evidence that the target is realistic. Search visibility is competitive, and conversion rates vary greatly by offer, audience, device, traffic source and measurement method.
A better target describes an improvement the business can verify, such as reducing incomplete enquiries, increasing the proportion of suitable bookings or making ownership and access more secure.
Use a one-page objective record
Before the project begins, record:
- the primary audience;
- the website's main job;
- the primary action;
- the definition of a successful outcome;
- the baseline, if one exists;
- the person responsible for reviewing results;
- the review date;
- important constraints such as budget, service area or capacity.
Attach this record to the website brief and use it when evaluating design, content and feature requests. If a proposed feature does not support the objective, satisfy a legal or operational need, or remove a genuine risk, it may not belong in the first version.
What to check before you act
- Is the objective specific enough to guide page and feature decisions?
- Does it describe an outcome the website can influence rather than guarantee?
- Has the business agreed what counts as a qualified enquiry, booking or sale?
- Can the necessary data be collected lawfully and accurately?
- Is someone responsible for reviewing the result after launch?
The next practical step is to copy the one-sentence objective into the project brief and test every proposed page against it.
Keep the decision under your control
Retain the relevant accounts, source material, supplier terms and recovery information. Recheck changing prices, interfaces and rules before acting.