How To Plan A Small Business Website

Knowing how to plan a small business website before design begins is what separates a useful sales asset from an expensive online brochure. The strongest websites are not created by opening a page builder and deciding which sections look good. They are planned around the business, the customer, search demand and the action the website needs people to take.

This is the part of a website project that visitors never see. It includes commercial goals, audience research, keyword mapping, the sitemap, page responsibilities, content, proof, functionality, technical requirements and measurement. When those decisions are made properly, design becomes more focused and development becomes easier to control.

When they are skipped, the project usually becomes slower and more expensive. Pages are added late, content does not fit the layouts, SEO is treated as a final check and nobody can clearly explain whether the finished website is working.

This guide explains how to plan a small business website using the complete pre-build process we apply before design and development begin.

Website planning starts before the homepage

Many small businesses start a website project with a list of visual preferences: colours, competitor websites, animations and homepage ideas. Those details matter eventually, but they are not the foundation of the project.

The first questions are commercial:

• What should the website help the business achieve?
• Which customers and services are most valuable?
• How will the right people find the website?
• What information will they need before taking action?
• What counts as a useful conversion?
• Who will own content, approvals and ongoing improvements?

A professional website planning process answers those questions before layouts are approved. If you are still deciding on the fundamental pages and features, start with our guide to what a small business website should include. This article goes one level deeper and explains how those parts should be planned as one commercial system.

1. Define the commercial job of the website

“We need a better website” is not a project objective. It describes dissatisfaction, but it does not define success.

A website might need to generate qualified enquiries, increase booked consultations, support local visibility, reduce repetitive sales questions, sell products, recruit employees or give an existing business more credibility. One website can support several outcomes, but it still needs a clear primary job.

For a service business, a useful objective could be:

Generate more qualified enquiries for our three highest-margin services from businesses within the West Midlands.

That objective immediately affects the sitemap, content, local landing pages, calls to action and reporting. It is far more useful than asking the designer to make the website look modern.

Define the primary conversion and any meaningful secondary conversions. These might include completed enquiry forms, tracked phone calls, booked consultations, quote requests, brochure downloads or email sign-ups. Avoid treating page views, time on site or social clicks as business outcomes unless they connect to a real commercial journey.

The measurement does not need to be complicated. At minimum, decide:

• The action you want visitors to take
• The number and quality of enquiries currently generated
• The approximate value of a qualified lead or sale
• The services or products that matter most commercially
• The result that would make the project worthwhile

This gives the project a decision filter. If a proposed page, feature or effect does not support the objective, it should have to justify its cost.

2. Identify the priority customer and buying situation

A website written for “anyone who might need us” normally communicates with nobody clearly. Planning requires a more precise view of the customer.

Do not stop at age, location and job title. Those details can be useful, but the buying situation matters more:

• What problem has caused the person to search now?
• What outcome are they trying to reach?
• What alternatives are they comparing?
• What would make them distrust a supplier?
• What evidence would reduce that risk?
• Who else is involved in the decision?
• Are they ready to buy, or still trying to understand the problem?

A homeowner looking for an emergency electrician behaves differently from a facilities manager sourcing a maintenance contractor. Both may need an electrician, but they need different content, proof and contact routes.

Map the main customer groups against the services they buy and the questions they ask. If two audiences have genuinely different needs, they may require separate journeys or landing pages. If the differences are superficial, keep the structure simple.

3. Research search demand before creating the sitemap

SEO should influence the structure of a website before pages are designed. Adding keywords to finished copy is not the same as planning for search.

Start by identifying how potential customers describe the service, problem, product and location. Look at commercial searches, supporting questions and local variations. Then group terms by intent rather than creating one page for every slightly different keyword.

For example, “accountant Birmingham”, “Birmingham accountants” and “accountancy firm Birmingham” may belong to the same core page. “Payroll services Birmingham” represents a more specific need and could justify its own service page if the business genuinely offers and prioritises it.

Each important page should have a clear search purpose. That prevents several pages from competing for the same topic and makes it easier to write useful titles, headings, URLs and internal links. Google’s SEO Starter Guide explains that SEO helps search engines understand content while helping users decide whether to visit it.

Keyword data still needs commercial judgement. A high-volume phrase is not automatically valuable. Prioritise relevance, buying intent, geographic fit, competitiveness and the value of the service. For local service businesses, our approach to local SEO in Birmingham connects these search decisions with location signals and local visibility.

4. Build a sitemap around services, intent and journeys

The sitemap is the structural plan for the website. It shows which pages will exist, how they relate and where visitors can move next. It should not be copied from a competitor or inherited automatically from the existing navigation.

A typical service-business sitemap might include:

• Homepage
• Individual service pages
• Sector or audience pages where the needs are materially different
• About page
• Work or case studies
• Resources or blog
• Contact page
• Privacy, cookie and other required policy pages

The exact number of pages is less important than whether each page has a distinct job. One weak services page is often too broad to rank or convert well. Twenty near-duplicate location pages are not a strategy either.

Use a simple rule: create a separate page when the topic represents a distinct customer need, search intent, offer or decision. Keep topics together when separating them would produce thin or repetitive content.

Plan the hierarchy and URLs at the same time. Google recommends simple, descriptive URL structures that people can understand. A logical structure might use /services/payroll/ rather than /page-id-248/. Read Google’s guidance on URL structure before development locks those decisions in.

Worked example: a Birmingham accountancy firm

Suppose an accountancy firm wants more enquiries from established owner-managed businesses. Its first sitemap draft might be:

• Home
• Accountancy services
• Annual accounts
• Management accounts
• Payroll services
• Tax planning
• Accountants for construction businesses
• Accountants for professional services
• About
• Case studies
• Guides
• Contact

This is stronger than a five-page brochure because the main services and priority audiences have room to answer specific questions. It also creates clearer landing pages for search and paid campaigns.

The final structure should still be based on evidence. If a proposed sector page has no distinct offer, expertise or proof, it may be better handled within a service page until the business can support it properly.

5. Give every page one primary responsibility

Once the sitemap exists, create a page plan. Every page should have one main audience, intent, message and next action.

Record the following for each page:

• Page purpose
• Primary audience
• Main search intent and target topic
• Core promise or message
• Questions and objections to answer
• Required proof
• Primary call to action
• Relevant internal links
• Content owner and approval status

This prevents pages from becoming collections of disconnected sections. It also exposes duplication before design begins. If two pages have the same audience, keyword target, message and call to action, they may not need to be separate.

Internal linking should be planned here, not added randomly after launch. Google recommends descriptive anchor text and says every important page should be linked from at least one other page. Its link best-practices guide is worth following when the content map is created.

6. Plan the conversion journey, not just the navigation

Navigation explains where information lives. A conversion journey explains how a visitor moves from uncertainty to action.

Someone landing on a service page may need to understand the offer, recognise that it fits their situation, see evidence, resolve a concern and then choose a contact route. The page should support that sequence without forcing every visitor through the homepage.

For each important landing page, map:

1. Entry: What search, advert, referral or direct visit brought them here?
2. Recognition: How quickly can they confirm that the page matches their need?
3. Understanding: Is the service, process or product explained clearly?
4. Confidence: What proof reduces the perceived risk?
5. Action: Is the next step obvious and proportionate?

The call to action must fit the commitment level. “Buy now” may suit a simple product. “Request a quote” may suit a defined service. “Book a discovery call” can work for a complex project. Giving every visitor five equal choices usually weakens all of them.

Our main guide to small business website design explains how clarity, trust and action work together on the finished website.

7. Plan content before designing finished pages

Content is not material used to fill a layout. It determines the hierarchy, page length, proof requirements and calls to action. Designing finished screens around placeholder copy usually creates rework when the real content arrives.

Create a content brief for every priority page. It should identify the key message, supporting points, customer questions, proof, search topic and desired action. Then decide who will write, review and approve the copy.

Good service-page content normally explains:

• What the service is and who it is for
• The problem or outcome it addresses
• What is included and excluded
• How the process works
• Why the business is credible
• Common questions or risks
• What the visitor should do next

Clear content is more valuable than inflated marketing language. Replace claims such as “leading solutions” and “unmatched quality” with specifics: experience, process, standards, response times, results, guarantees or relevant qualifications.

Content readiness is also a project-management issue. Set deadlines for copy, photography, case studies, team biographies, policies, downloads and product data. If the client owns those tasks, put them in the timeline and make the effect of delays explicit.

8. Map proof to the point of doubt

Trust should not be confined to a testimonials page. Different claims require different evidence, and that evidence should appear near the decision it supports.

Useful proof can include:

• Relevant case studies with a clear problem, approach and outcome
• Named testimonials and independent reviews
• Photographs of real work, premises or people
• Accreditations, memberships and certifications
• Measured results with enough context to be credible
• Guarantees, warranties or documented service standards
• A clear process that reduces uncertainty

Plan proof page by page. A visitor considering payroll services may care about accuracy, deadlines, software and support. A visitor choosing a brand designer may care more about the quality and relevance of previous work.

Avoid placing every logo and testimonial in one carousel. Select the strongest evidence for the claim being made. Veon Media’s website design work demonstrates how project examples can support broader service claims.

9. Define functionality and integrations before quoting the build

Features are often where website scope expands. “A booking system” or “CRM integration” can describe anything from a simple embedded tool to a custom two-way data flow with permissions, automation and error handling.

For every feature, document:

• The user who needs it
• The task it must complete
• The data collected or displayed
• The systems it connects to
• Required notifications and automations
• User roles and permissions
• Failure states and manual fallbacks
• Ownership, subscriptions and ongoing support
• How success will be tested

This applies to forms, ecommerce, bookings, memberships, gated downloads, calculators, live chat, multilingual content, job listings and third-party integrations.

Do not add functionality because it appears modern. Every feature creates build cost, maintenance, security exposure and potential friction. The best solution is the simplest reliable system that supports the required customer and business process.

10. Choose the platform from the requirements

The content-management system should be chosen after the content model, editing needs, integrations and growth plans are understood.

Questions to resolve include:

• Who will update the website and how often?
• Which content types need repeatable templates?
• Does the business need ecommerce, memberships or multilingual content?
• Which systems must integrate with the site?
• What level of performance, security and availability is required?
• Who owns hosting, updates, backups and technical support?
• How easy must it be to move supplier later?

WordPress is often a strong fit for content-led service websites because it is flexible and widely supported, but the quality of the build matters more than the platform name. Bloated themes and unnecessary plugins can create performance, editing and maintenance problems. Our WordPress web design service explains how we approach clean, scalable builds.

The platform decision should be documented. That prevents technology preference from overriding the commercial requirements.

11. Build technical SEO into the specification

Technical SEO is easier to protect before development begins than to repair after launch. The specification should cover:

• Crawlable navigation and internal links
• Descriptive URLs
• One clear H1 and a logical heading hierarchy
• Editable page titles and meta descriptions
• Canonical URL handling
• XML sitemap and robots.txt behaviour
• Image compression and meaningful alt text
• Redirect requirements for changed or removed URLs
• Structured data where it accurately represents visible content
• Indexing controls for thin, private or duplicate areas
• Search Console and analytics access

If the project replaces an existing website, export the current URLs before changing anything. Record pages that receive organic traffic, links or conversions. Then create a redirect map from every valuable old URL to the most relevant new destination. Redirecting everything to the homepage wastes relevance and creates a poor user experience.

This work should sit inside the build scope, not appear as an optional “SEO plugin setup” at the end. Veon Media’s search engine optimisation work connects technical foundations with ongoing content and authority development.

12. Set standards for mobile, performance and accessibility

“Responsive” is too vague to be a useful acceptance criterion. Define the experience that must work on real devices: navigation, forms, calls, booking, checkout, tables, downloads and any interactive features.

Set a performance budget before visual effects and third-party scripts accumulate. Google’s current Core Web Vitals measure loading performance, responsiveness and visual stability through LCP, INP and CLS. The web.dev guidance describes good thresholds of 2.5 seconds or less for LCP, 200 milliseconds or less for INP and 0.1 or less for CLS, measured at the 75th percentile.

Accessibility also belongs in planning. Colour contrast, keyboard operation, focus states, labels, error messages, heading structure, text resizing, alternative text and motion preferences affect both design and development. The W3C overview of WCAG 2.2 provides the recognised standard and supporting guidance.

Do not promise a perfect automated accessibility score. Automated tools can identify some failures, but they cannot replace keyboard testing, screen-reader checks and human judgement.

13. Plan privacy, security and ownership

A business website can collect personal information through forms, analytics, accounts, payments, booking tools and marketing integrations. Decide what data is collected, why it is needed, where it is sent, how long it is retained and who can access it.

UK organisations should plan privacy information and cookie controls before tracking scripts are installed. The Information Commissioner’s Office provides a privacy notice generator for smaller organisations and explains that non-essential cookies require appropriate information and agreement in its cookie guidance.

The project should also define:

• Domain and DNS ownership
• Hosting responsibility
• SSL, backups and recovery
• Software and plugin updates
• Administrator access and multi-factor authentication
• Form-spam protection
• Security monitoring and incident response
• Ownership of design, code, copy, photography and licences
• What happens if the supplier relationship ends

These details are rarely visible in a mock-up, but they determine whether the website is a durable business asset.

14. Control scope, responsibilities and approval gates

Most website projects do not fail because somebody chose the wrong shade of blue. They lose time and margin because responsibilities and decisions remain vague.

The pre-build plan should define:

• Included pages, templates and features
• Content and asset responsibilities
• Named decision-makers
• Feedback rounds and approval deadlines
• Browser and device testing scope
• Migration and redirect responsibilities
• Training and handover
• Hosting, maintenance and post-launch support
• What counts as a change request

Use approval gates between discovery, sitemap, content, wireframes, design and development. Each gate closes a set of decisions before the next phase begins. If an approved sitemap changes after development starts, treat that as a scope change rather than absorbing it invisibly.

The same discipline makes pricing more meaningful. Our guide to website cost in Birmingham explains why strategy, content, integrations and testing create very different products even when two websites have a similar page count.

15. Define measurement before launch

Analytics should answer business questions, not merely report traffic. Create a measurement plan alongside the website specification.

At minimum, identify:

• Primary conversions and their values where known
• Form submissions and successful form completions
• Click-to-call and email actions
• Booking or checkout completion
• Important service-page entry points
• Organic landing pages and search queries
• Consent requirements for analytics and advertising tags
• Who reviews performance and how often

Document the event name, trigger and reporting destination for each conversion. Test tracking before launch and again after the production domain is live.

The first version of a website is a controlled starting point, not the final answer. Search data, sales feedback, conversion behaviour and customer questions should inform future improvements. Without measurement, redesign decisions eventually return to taste and guesswork.

How to plan a small business website: the pre-build checklist

Before design begins, confirm that the following decisions are documented:

• The website’s primary commercial objective
• Priority services, products and customer groups
• Primary and secondary conversions
• Search demand and page-level keyword intent
• Sitemap, hierarchy and proposed URLs
• Page purpose, message, proof and call to action
• Content, photography and asset responsibilities
• Conversion journeys for important landing pages
• Functionality, integrations and acceptance tests
• Platform, hosting and support responsibilities
• Technical SEO and redirect requirements
• Mobile, performance and accessibility standards
• Privacy, cookie, security and ownership requirements
• Scope, approvals, timeline and change-control process
• Analytics, conversion tracking and review cadence

If several of these remain undecided, the project is not ready for polished design. A wireframe or discovery prototype may still be useful, but approving finished layouts would create false progress.

Common website planning mistakes

Copying a competitor’s sitemap

A competitor may target different customers, services or locations. Use competitors for research, not as a substitute for strategy.

Designing around placeholder content

Lorem ipsum hides real content problems. The actual message, proof and call to action should influence the layout.

Creating one page for every keyword variation

This produces thin, repetitive pages and internal competition. Group closely related searches by intent.

Treating SEO as metadata

Page titles matter, but SEO also depends on structure, content, internal links, crawlability, performance and authority.

Adding features without defining the workflow

A feature is not properly scoped until the users, data, integrations, permissions, errors and support responsibilities are understood.

Allowing unlimited decision-makers

Consolidated feedback and named approval authority protect both the timeline and the quality of the work.

Launching without a measurement plan

If conversions are not tracked from the start, nobody can distinguish a design problem from a traffic, targeting or sales-process problem.

Frequently asked questions

How long should website planning take?

For a straightforward small-business website, focused discovery and planning may take one to three weeks. A larger site with multiple audiences, content migration, integrations or complex approvals will take longer. The real variable is not page count alone; it is the number of commercial, content and technical decisions that must be resolved.

Should website content be written before design?

The priority messages, page structure and approximate content should be known before polished design begins. Copy can still be refined during the project, but designing every page around placeholder text creates avoidable rework.

How many pages does a small business website need?

There is no universal number. The website needs enough pages to explain the priority offers, answer distinct search intents, build trust and support the required customer journeys. Every page should have a clear purpose; page count should not be used as a proxy for value.

Can I plan a business website myself?

Yes, particularly if the offer, customer and content are straightforward. The risk is overlooking search demand, conversion journeys, migration requirements or technical dependencies. A professional planning phase becomes more valuable as the commercial stakes and project complexity increase.

What should I give a web designer before the project starts?

Provide the business objectives, priority services, target customers, brand assets, current analytics access, domain and hosting details, examples of previous work, testimonials, required functionality, known integrations, content ownership and a clear approval process. A good designer should challenge and refine the brief rather than simply accept it.

Plan first, then design with confidence

A well-planned website is easier to price, write, design, build and measure. More importantly, it has a better chance of becoming useful commercial infrastructure rather than another brochure that needs replacing in two years.

The practical answer to how to plan a small business website is to connect business objectives, customer needs, search demand, content, proof, technology and measurement. Once those decisions are aligned, visual design can do its real job: making the strategy clear, usable and credible.

If you are planning a new website or replacing one that no longer supports the business, Veon Media provides professional web design in Birmingham with SEO, performance and conversion requirements built into the project from the start. Review our work, then start your project when you are ready to turn the plan into a website.

Last Updated on 1 month ago by Ben