A new website is a significant investment, but it is difficult to judge whether the project has been successful if the only goal is to “look more professional”.
Good design matters. So do clear content, straightforward navigation and reliable technical performance. However, a website should also support the way your organisation operates and the outcomes you want to achieve.
Those outcomes will vary from one business to another. You may want to generate more relevant enquiries, help your sales team answer questions, attract suitable applicants, provide important information or reduce pressure on your staff.
The key is to turn broad ambitions into a small number of realistic website goals. This gives your project direction and helps you make better decisions about content, features, budget and ongoing improvements.
Start with the business problem, not the website features
It is tempting to begin with a list of features:
- A new contact form
- A portfolio section
- Online booking
- A product catalogue
- A customer login area
- A news or blog section
These may all be useful, but they do not explain what the website needs to achieve. A feature should support a genuine business or customer need rather than exist simply because another website has it.
Start by asking:
- What is not working well at the moment?
- Where are customers or prospects becoming uncertain?
- Which questions does your team answer repeatedly?
- What would you like visitors to do next?
- Which internal processes could the website support?
For example, a manufacturer may receive enquiries that are too vague for the sales team to respond to efficiently. The website goal might not be “add a new form”. It could be to help potential customers provide the product, application or project information needed for a useful first response.
Similarly, a healthcare provider may need to make services, locations and appointment information easier to find. A school may want parents to locate policies, term dates and admissions information quickly. A growing business may need a website that supports recruitment as well as sales.
The business problem should lead the project. The feature comes afterwards.
Choose the main role your website needs to play
Most business websites support more than one objective, but it is still helpful to identify the primary roles.
1. Generating relevant enquiries
For many businesses, the main purpose of a website is to encourage suitable prospects to make contact.
A realistic enquiry goal should focus on quality as well as quantity. More form submissions are not necessarily useful if they are incomplete, irrelevant or impossible for your team to follow up.
Your website may need to:
- Explain your offer clearly
- Show who your services are suitable for
- Answer common buying questions
- Present evidence of your experience
- Make the next step obvious
- Capture enough information for an effective response
Possible measures include completed contact forms, telephone calls, email enquiries, quote requests or downloads that indicate buying interest. Make sure you can distinguish genuine enquiries from spam and general messages.
2. Supporting sales conversations
A website does not have to complete a sale to create commercial value. It can help your sales team prepare prospects before a conversation takes place.
This is particularly important for businesses with technical products, considered purchases or longer sales cycles. Clear service pages, product information, case studies, FAQs and comparison content can help prospects understand your offer before they speak to you.
A sales-support goal might be:
Help prospective customers understand our main services and arrive at an initial conversation with clearer expectations.
You could assess this through feedback from your sales team, the questions customers ask, visits to key pages and the number of relevant enquiries containing useful background information.
3. Supporting recruitment
For some organisations, attracting suitable employees is a key website objective. This may apply to manufacturers, engineering businesses, healthcare providers, schools and growing professional services firms.
A recruitment-focused website should explain more than available roles. It should give candidates a realistic understanding of your organisation, working environment, values and expectations.
Useful goals may include:
- Make current vacancies easy to find
- Explain how to apply
- Present your organisation as a credible employer
- Answer practical questions about working with you
- Reduce incomplete or unsuitable applications
Avoid setting an unrealistic goal such as “the website will solve our recruitment problems”. Recruitment depends on many factors, including the role, location, salary, market conditions and wider employer reputation. The website can support the process, but it cannot control every outcome.
4. Providing important information
Some websites are primarily information services. Schools, clinics, membership organisations and businesses with complex products may need visitors to find accurate information without contacting a member of staff.
An information goal should be specific. Instead of saying “make information easier to access”, identify the important journeys:
- A parent needs to find term dates
- A patient needs to understand available services
- A buyer needs to download technical documentation
- A customer needs to find delivery information
- A prospective employee needs to understand the application process
You can then organise navigation and page content around these tasks. Search data, staff feedback and customer questions can help you decide which information deserves the clearest routes.
5. Improving customer service
A well-planned website can reduce avoidable customer service requests by answering common questions clearly and directing people to the right support.
This might involve:
- Clear contact details and opening information
- Delivery, returns or payment guidance
- Account or service instructions
- Troubleshooting information
- Downloadable forms and documents
- A useful FAQ section
The goal is not to prevent customers from contacting you. It is to help them choose the right contact route and arrive with the information they need.
Turn broad ambitions into measurable goals
Once you understand the website’s role, write goals that are specific enough to guide decisions.
A useful format is:
We want to help [audience] do [action] so that [business or customer benefit]. We will review progress using [measure].
For example:
We want to help prospective manufacturing customers understand our specialist services and submit more useful project enquiries. We will review the number and quality of enquiries, the information provided and feedback from the sales team.
This is more useful than:
We want more leads and a better website.
You do not need to predict an exact percentage increase if you do not have reliable historic data. A target that appears precise but is based on guesswork can create unnecessary pressure and lead to poor decisions.
Instead, establish a baseline where possible:
- How many relevant enquiries do you currently receive?
- Which website pages are visited most often?
- How many people complete your current forms?
- Which questions do staff answer repeatedly?
- How long does it take to respond to common requests?
- Where do visitors leave important journeys?
If you have limited data, use the first few months after launch to establish a more reliable baseline. The important thing is to define what you will look at and why.
Separate launch goals from longer-term goals
A website project has two different types of objectives.
Launch goals
These are the things the project needs to deliver before the website goes live. They might include:
- Clear messaging for priority audiences
- A logical page structure
- Accurate and approved content
- Straightforward enquiry routes
- Mobile-friendly layouts
- Accessible content and navigation
- A manageable content editing experience
- Appropriate analytics and form tracking
These goals are largely within the project team’s control.
Longer-term goals
These are outcomes you will work towards after launch:
- More relevant enquiries
- Better visibility for important services
- More completed applications
- Fewer repetitive information requests
- Stronger support for sales conversations
- Increased engagement with key content
Longer-term outcomes usually depend on more than the website itself. Content updates, search optimisation, marketing activity, response times, pricing, service quality and market conditions may all influence performance.
Keeping the two types of goals separate helps you judge the project fairly. A website can launch successfully while still needing time and ongoing activity to deliver its wider commercial contribution.
Prioritise goals when everything seems important
A common problem is trying to make every website objective the top priority. This can make the project unfocused and difficult to manage.
Rank goals using three questions:
- How important is this to the organisation?
- How valuable is it to the customer or visitor?
- How practical is it to deliver and maintain?
A goal that is commercially important, highly useful to visitors and achievable with the available resources should usually come first.
You can also divide goals into:
- Must have: Essential for the website to work properly
- Should have: Valuable improvements that fit the initial project
- Could have: Useful ideas for a later phase
- Not yet: Interesting possibilities without a clear current need
This approach is particularly helpful when budgets, content resources or internal availability are limited. It is better to deliver a focused website that your team can manage than an overloaded website with features nobody maintains.
Make goals realistic for your team
Your website goals must reflect what happens after launch.
If nobody has responsibility for updating vacancies, publishing news, reviewing forms or checking enquiries, those areas may quickly become unreliable. Include ownership in your planning:
- Who approves new content?
- Who receives and responds to enquiries?
- Who reviews analytics?
- Who updates products, services or documents?
- Who checks that key information remains accurate?
- When will goals be reviewed?
A simple monthly or quarterly review is often enough to begin with. Look at the agreed measures, gather feedback from staff and customers, and identify one or two practical improvements.
You may also find that your original goals need to change. That is not necessarily a sign that the project failed. Businesses evolve, customer behaviour changes and new priorities emerge. A useful website should be able to develop with you.
Use goals to guide design and content decisions
Your goals should influence the structure of the website.
If enquiries are the priority, make contact routes clear and provide enough context for visitors to understand what happens next. If sales support is important, organise content around the questions buyers ask. If recruitment matters, make opportunities and employer information easy to find.
Goals can also help resolve disagreements. Instead of debating whether a page or feature “looks better”, ask which option better supports the agreed audience and outcome.
Before approving a design or content decision, ask:
- Does this make the visitor’s next step clearer?
- Does it support one of our main goals?
- Does it build confidence or reduce uncertainty?
- Can our team maintain it?
- Is there a simpler way to achieve the same result?
This keeps the project commercially grounded without reducing it to a set of numbers.
A practical website goals checklist
Before starting your project, make sure you can answer:
- What business problem is the website expected to address?
- Who are the most important audiences?
- What do you want each audience to do?
- Is the main purpose enquiries, sales support, recruitment, information, customer service or a combination?
- Which goals are essential at launch?
- What baseline information is available?
- How will you measure progress?
- Who will own the website after launch?
- When will you review performance?
- Which ideas can wait for a later phase?
For further preparation, see What Should You Prepare Before Starting a Website Project?. If you are planning a WordPress website, How to Plan a WordPress Website That Still Works Five Years Later covers longer-term planning in more detail.
A website is more likely to support your business when its purpose is clear from the beginning. Set a small number of realistic goals, connect them to genuine customer needs and agree how progress will be reviewed. That gives your design, content and technology decisions a clear direction.
There is no fixed number, but a small set of clearly prioritised goals is usually more useful than a long list. Identify the main objective, then add supporting goals for areas such as sales support, recruitment, information or customer service.
Only if you have reliable baseline data and a reasonable basis for the target. Otherwise, define what you will measure and establish a baseline after launch. Avoid false precision based on assumptions.
No. A website can support clearer communication, better customer journeys and more relevant enquiry routes, but commercial outcomes are also affected by your offer, pricing, service, marketing, market conditions and how quickly enquiries are handled.
Review early performance after launch, then establish a regular monthly or quarterly review. Combine analytics with feedback from your team and customers so you understand not only what visitors do, but also whether the resulting enquiries or interactions are useful.
Related Services
Related Projects
Related Insights
- What Should You Prepare Before Starting a Website Project?
- How to Plan a WordPress Website That Still Works Five Years Later
Need help defining your website goals?
If you are planning a new website and are not sure which objectives to prioritise, get in touch with Urbansoul Design. We can talk through your audiences, customer journeys and wider business requirements before you commit to a project.