A small business website should help people understand your offer and take the right next step. Start with customer tasks and useful pages, then choose the platform, budget and builder. Before launch, test the whole enquiry, booking or purchase journey. Then agree who keeps the site working.
This guide walks through seven steps. They overlap in practice, so treat the map below as an order of decisions rather than a schedule:
Step 1: Decide what the website must do
A business website has more than one job. New visitors check whether you suit them. Existing customers come back for hours, changes or help.
Visitor task | Useful outcome | Business evidence |
|---|---|---|
Check an unfamiliar supplier | Understands fit and the next step | Useful enquiries and objections |
Buy or book | Completes the order or request | Correct order or booking record |
Visit a venue or appointment | Finds hours, location and access | Details stay current |
Return for help | Finds support or instructions | Requests reach the right owner |
Pick a primary outcome, but don't hide legitimate tasks behind a lead form. Opening hours, a menu or product instructions are useful outcomes in their own right.
Fix the real problem first
If you already have a site, find out what's actually wrong before you rebuild:
information is missing or out of date
the contact route is broken
the platform is unsupported
the business can't respond to the demand
Fix a focused defect if that works. Keep useful pages, brand assets, traffic history and working integrations. A new site won't fix weak demand or poor follow up. A common mistake is rebuilding when only one task is broken.
Define the minimum useful launch
Essential customer tasks and the proof behind them come first. A blog, chat or animation can wait. Give each requirement an owner and a way to check it. Our guide to planning a small business website has the full worksheet.
Step 2: Plan the useful pages
Your page list is a content decision. There's no magic number of pages. A single page can suit a narrow offer. Add pages when they answer a distinct need with enough detail.
Page | What the visitor needs | Useful next action |
|---|---|---|
Homepage | Offer, audience, key paths, proof | Choose a service or main action |
Service or product | Fit, scope, price process, proof | Enquire, book or buy |
About and team | Who's responsible, real identity | Reach the right person |
Contact or booking | Channels, hours, response, access | Make a request or booking |
Work examples | Permissioned work and context | Return to the right offer |
Policies and help | Privacy, terms, returns, support | Resolve a condition or need |
For each important page, note the question it answers, the evidence it needs and the next step. Include likely objections and honest price guidance. A separate proof page is optional when evidence works better beside the service.
Visitors don't always land on the homepage. Search and ads bring people straight to service, product and help pages. Each must stand alone.
That's an example hierarchy for a service business. Combine or adapt pages when that suits the customer tasks better.
Structure the homepage
A homepage helps people understand the business and choose a path. Here's one starting point:
It's a placeholder layout rather than a proven winner. The full page also needs service summaries, your process, evidence and answers to common questions. Our guide to what a homepage should say covers the copy.
Brief each important page
A restaurant menu, a course catalogue and a product page need different details. So brief each important page on its own terms:
Page: [name and purpose]
Customer question: [what the visitor needs]
Offer and scope: [included work and limits]
Evidence: [approved proof]
Price approach: [truthful price or quote process]
Next step: [what the visitor can do]
Owner: [person approving facts and updates]
Our service page guide sets out the service page template in full. Keep navigation clear. Link important pages from inside your content too.
See what changes by industry
The core pages stay similar. What changes is the information each business must get right:
Business type | Important information | Verify before launch |
|---|---|---|
Trades and home services | Services, coverage, credentials | Availability and enquiry receipt |
Professional services | Scope, practitioners, fees, proof | Routing and claim rules |
Healthcare and allied health | Practitioners, fees, appointments | Booking status, privacy, ad rules |
Ecommerce and retail | Product detail, delivery, returns | Payment, order and stock records |
Hospitality and food | Menu, hours, access, bookings | Holiday changes, dietary details |
Real estate and property | Agents, listings, appraisals | Feed freshness and routing |
Finance and fintech | Scope, authorisations, fees | Claims approval, sensitive forms |
Education and training | Courses, dates, costs, entry | Enrolment, capacity, claims |
Treat these as scope prompts, not complete compliance checklists. Ask the right specialist to verify sector claims. A public form shouldn't become a channel for detailed medical or financial records. If you'd like help building one, see our industry pages:
Our sector guides go deeper. They cover what a tradie website needs and professional service website essentials. There's also one on what a restaurant website needs.
Step 3: Make each page clear and usable
Clear pages answer the visitor's questions in the order they ask them. Start with a quick test of the message.
Run the ten second clarity exercise
Show a relevant page to someone who doesn't know the business, for about ten seconds. Then ask them four questions:
What's on offer?
Who or where does it serve?
What makes it trustworthy?
What would you do next?
Note what they remember and where they hesitate. It's an informal check that surfaces questions to investigate. It isn't a validated conversion score or a proven deadline for leaving.
If the message is unclear, revise the heading, labels or order. Then repeat it with someone else. A clear homepage doesn't prove the booking works, so test the task itself next.
Design for clarity
Good design comes from clear hierarchy, readable type and enough contrast. Consistent components and a visible next action help too. Trends don't make design modern.
UX is the whole experience of completing a task. UI is the interface people use to do it. Both matter, and neither is decoration.
Write copy that says something
Swap vague lines for specific ones:
Vague copy | Useful replacement direction |
|---|---|
Welcome to our website | Name the offer and the customer or area |
We deliver quality solutions | Explain the work and a supported reason to choose it |
Contact us today | Use a truthful action, like Request a quote |
Fastest, best and guaranteed | Use a verifiable claim with its conditions, or cut it |
Welcome to our website. Quality solutions for everyone.
Bookkeeping for cafes and retailers. See what's included, then book a call for a quote.
That's an example rewrite with no claimed conversion effect. Keep who, what and where when location matters. Then say what happens next. Don't promise free, fixed price or same day service unless it's approved and available. Our guide to writing clear website copy goes deeper.
Use genuine reviews and current credentials, with photos that show real context. The ACCC's Online reviews for product and services guidance makes two points. It's against the law for a business to create fake or misleading reviews. A business may also mislead consumers if it suppresses or edits negative reviews, or removes genuine ones.
Stock or AI illustrations are fine when they don't pretend to show real people, work or results. Our guide to using genuine reviews covers collecting them. Content can come from the business, a copywriter or the agency after an interview. Assign who supplies the facts, who approves them and who keeps them current.
Make mobile use and accessibility testable
Test core tasks on real phones and desktop browsers. Check keyboard access, zoom and error messages. Offer a second way to make contact. Don't let call buttons, chat or consent layers cover content or the submit button. Keep entered details after a correctable error, and ask only for what you need at that stage.
WCAG 2.2 is the main set of web accessibility guidelines. The Australian Human Rights Commission says organisations should meet Level AA at a minimum. Tap targets have their own criteria in CSS pixels, a layout unit that doesn't shrink on sharper screens:
the Level AA minimum is 24 by 24 CSS pixels, with exceptions
the 44 by 44 pixel size is the enhanced Level AAA criterion, WCAG's highest level
Larger controls can still be a sensible design choice. The Digital Inclusion Standard guides government digital services. It isn't the test for every private site. A quick check, including our accessibility quick check, isn't a full audit or legal certification. Our guide to website accessibility for Australian businesses covers the full set of checks.
Check speed the right way
Speed tools report two kinds of data. Read them differently:
Measure | How to read it |
|---|---|
Lighthouse performance score | A lab diagnostic, not a sales score |
Field data | Real visits over the previous 28 days |
Origin data | Your whole site's data, used when a page lacks its own |
No field data | Too few samples, so neither a pass nor a fail |
Google's Lighthouse bands put 0 to 49 as poor and 50 to 89 as needs improvement. Scores of 90 to 100 count as good. PageSpeed Insights shows both lab and field data, so check what each report describes.
The 75th percentile means three in four visits meet the number or do better. These thresholds from web.dev cover loading (LCP), responsiveness (INP) and visual stability (CLS). The field Core Web Vitals are what Google's ranking systems use. They aren't Lighthouse bands or conversion targets.
Check important page types on phones and desktops, not just the homepage. Investigate oversized images, heavy third party scripts and slow delivery. Our guides to diagnosing a slow website and Core Web Vitals explained cover the fixes.
Step 4: Choose the build and keep control
Who builds the site matters less than who owns each job afterwards. Compare the routes on responsibility:
Build route | Can fit when | What still needs an owner |
|---|---|---|
DIY | You can learn, test and run it | Content, setup, access and care |
Freelancer | One specialist can cover the work | Cover for absence, handover |
Agency | The work needs several skills | Named people, approvals, support |
These are delivery models, not a quality ranking. DIY doesn't always miss SEO basics. A big agency doesn't guarantee results either. Ask for relevant work, a scoped quote and clear acceptance criteria.
Our guide lists the questions to ask a web designer. Those questions apply to our web design services too.
Choose a platform from your requirements
Match the platform to the work:
a hosted builder, like Squarespace or Wix, for manageable standard needs
WordPress, where its content system and plugins fit
Webflow, where its design workflow fits
Shopify or WooCommerce for the commerce you need
custom development when a real requirement justifies it
Which platform is always best for a small business?
Which option supports our editing, customer journey, integrations, costs, care and exit needs?
Ask the supplier to demonstrate the real work, like editing an important page or completing a booking. Find out which features are native, paid extensions or custom work. Try the website platform comparison tool first. It can't confirm your integrations, skills or total cost.
Our website platform comparison covers the wider shortlist. Store owners can compare Shopify and WooCommerce for Australian stores.
AI can draft layouts, copy and code. A generated site still needs checks on facts, rights and accessibility.
Never fake photos, reviews or case studies. Keep confidential customer details out of AI prompts.
Understand domains, rights and access
Several services often get bought together. They're still different things:
the domain, which is the name
DNS, the records that route the name
hosting or the hosted platform that delivers the site
the content management system (CMS) where you edit
email, which may be a separate service
Moving a website doesn't always mean moving the domain or email. Map the existing services before anyone changes records. Our explainer on what a CMS does covers the editing side.
A .com.au licence needs an Australian commercial entity, commonly with an ABN or ACN. The name must connect to your business. Names under .au direct need a validated Australian presence instead. Either way, registration is a renewable licence rather than ownership or a trade mark.
If a developer registers the name for you, they should use your business's details with your written permission. A password alone doesn't make you the licence holder. A common mistake is letting a developer register it in their own name.
That's an example responsibility map, not a statement of who owns what by law. Collect this evidence for each piece:
Asset or service | Evidence to obtain |
|---|---|
Domain and DNS | Correct registrant, recovery access and a record list |
Hosting or platform | Business access, renewal terms and export limits |
CMS and integrations | Named accounts, suitable roles and a removal process |
Analytics and Search Console | Business admin access and documented permissions |
Design, content and code | Written assignment or licence, files and restrictions |
Email and operations | Routing records, provider, tests and a continuity plan |
Intellectual property (IP) a contractor creates belongs to the contractor unless the agreement says otherwise. IP Australia confirms it, so agree rights before work starts. Licensed fonts, photos and plugins carry their own terms.
Keep an administrator and recovery route in the business. Give staff and contractors only the access their role needs, with multi factor authentication where available. Our website handover checklist covers a full transfer.
Step 5: Agree the budget and build plan
Here are our published build prices, checked in October 2026. They're provider offers in AUD excluding GST, not Australian averages:
Published offer | Price, excluding GST | Scope direction |
|---|---|---|
Starter website | $2,400 to $5,000 | 5 to 10 pages |
Business website | $5,000 to $12,000 | 10 to 20 pages, custom features |
Ecommerce store | $8,000 to $20,000 or more | Catalogue, payments, shipping |
Landing page | $800 to $2,000 | One focused page |
SourceElev8d web design page, checked in October 2026
Ecommerce starts at $8,000 and can pass $20,000. That's why it stays in the table. Confirm what each quote includes, from content to training. Our web design page offers copy help. That doesn't mean every package includes unlimited copy.
Budget for one off work, running costs and usage charges. Record what's bundled so hosting and backups aren't counted twice. Label each line's currency, tax and term.
Care is optional and set out separately before you sign. Our guide to website costs including running costs has the worked budget. The website cost estimator helps you plan before a quote.
Business and audience: [who you serve]
Essential tasks: [what people must be able to do]
Pages and evidence: [required content]
Systems and access: [existing dependencies]
Budget and timing: [scope and constraints]
Approval owner: [decision maker]
Launch evidence: [critical tests]
Later improvements: [deliberately deferred work]
Our web design page quotes 4 to 8 weeks for Starter, Business and ecommerce builds. Content and feedback affect the pace. Bigger projects can take longer.
Work can overlap when dependencies allow. Set review windows and one decision owner. Agree how scope changes get priced. Here's an example six week plan, not our promised schedule:
DAYS 1–7Agree scope
Deliverable: customer tasks, pages, budget and acceptance criteria
Owners: the business and provider agree the brief and inputs
DAYS 8–14Plan content
Deliverable: sitemap, wireframes, page copy and evidence
Owners: named content owners supply facts and approve claims
DAYS 15–28Design and build
Deliverable: working layouts, content and required integrations
Owners: the provider demonstrates tasks and the business gives feedback
DAYS 29–35Test and approve
Deliverable: completed tests and resolved critical defects
Owners: the business owner approves with evidence
DAYS 36–42Launch and hand over
Deliverable: live checks, access, training and responsibilities
Owners: both confirm the business can run the site
Plan a redesign carefully
For a redesign, keep the old site and backups until the transition checks pass. Inventory important URLs, forms and email records first. Note the tracking setup too.
Agree a fallback if launch fails. Reconcile any orders or enquiries received after cutover before rolling back. Our redesign checks before and after launch cover the detail.
Step 6: Test before you launch
Critical failures can't be averaged away by a good score elsewhere. Agree who approves launch and which defects must be fixed. Minor items can wait, as long as each has an owner and a date.
Primary enquiry or transaction
A permitted test reaches the right record and person
Errors and alternatives
Failed forms and payments give a useful next step
Mobile and accessibility
Key journeys work on devices, keyboard and zoom
Content and claims
Identity, offer, prices and proof are correct
Security and recovery
HTTPS, access, recovery contacts and a usable backup
Migration and discovery
URL mapping, public settings, no staging blocks
Measurement and privacy
Actions tested and personal data handled properly
Business operation
Training, a response owner and running costs accepted
The checklist is manual. It doesn't inspect the site or guarantee readiness. A failed essential check caps the readiness score. A broken core task still blocks launch, whatever the score says.
Cover the search foundations
Build these in from the start:
useful original content
logical headings and navigation
descriptive titles and URLs
useful image alternative text
crawlable internal links and correct public settings
Google's SEO Starter Guide covers the basics. A crawlable, indexable site still isn't guaranteed to rank. For a redesign, map old URLs to relevant new pages with permanent redirects. Don't send every removed page to the homepage.
Google's site move guidance says to expect temporary ranking changes during a move. Set up Search Console access in the business's name. In URL Inspection, a live test only confirms Google can access the page. No test guarantees indexing.
Keep local details accurate, including real service areas. Don't build near identical pages for every suburb. Ongoing SEO and promotion are separate work. Our small business SEO guide covers that strategy.
Test privacy, delivery and continuity
Run a real enquiry test before launch:
submit permitted test details
check the confirmation
find the record at its destination
ask the assigned staff member to find it too
A thank you message only proves what the system actually completed. For bookings, separate a request from a confirmed slot. For stores, reconcile the payment, order and stock records. Our ecommerce launch checks go further.
Trace where forms, analytics, chat and uploads send data. Collect only what you need and limit staff access. State why you collect each detail and how long you keep it.
Keep marketing permission separate from what you need to answer a request. Never force a newsletter sign up. The Privacy Act doesn't cover every website. It isn't only for businesses over $3 million either. Some smaller businesses are covered, including health service providers, as the OAIC's small business guidance explains.
Don't send names, emails or enquiry text to analytics events or page URLs. Google's Analytics rules prohibit identifying data. Our website compliance checks and guide to privacy policy and website terms cover the wording.
Protect email and access
Before changing DNS or hosting, preserve the records your email uses. After launch, check that business email still sends and arrives. Keep a known support contact and a second way for customers to reach you. A common mistake is changing DNS and silently breaking business email.
Don't share one administrator password. Revoke contractor access you no longer need. Store credentials securely. The ACSC's small business guide covers multi factor authentication, updates and backups.
Step 7: Measure results and maintain the site
Write a short measurement plan before launch. For each important task, name the event or record, its source, an owner and the decision it informs.
GA4 key events mark the actions that matter most to the business. An event name doesn't prove a successful enquiry, though. A phone link click isn't a connected call. A form event can fire before delivery, or twice.
Question | Evidence to request | What it can't prove alone |
|---|---|---|
Which pages are reached? | Defined views, period and source | That content was read |
Which pages support enquiries? | Entry page, action page and source | That the last page caused it |
Which enquiries are useful? | Valid records and outcomes | That more forms mean more work |
Does it support results? | Mature outcomes, value and costs | Causation |
Exits and bounces need care. GA4's bounce rate is the share of sessions that weren't engaged. An engaged session lasts over 10 seconds, has a key event or has two or more page views. A page with many exits may simply have answered the question.
Compare like for like periods. Allow for low traffic too. Device differences can reflect intent and traffic mix as well as usability. Our guide to using GA4 for a small business covers setup.
Name who receives and qualifies requests, and who replies during stated hours. Say what happens when that person is away. An acknowledgement isn't a confirmed appointment.
Record suitable enquiries, booked work and completed paid work separately. Remove duplicates, spam and repeat contacts before you call an enquiry valid. Note cancellations and your capacity too.
Do the advertising maths honestly
Paid traffic turns page quality into a cost question. Take, say, a $5 click price and 100 clicks. That's $500 of ad spend:
Click to enquiry rate | Valid enquiries | Ad spend per enquiry |
|---|---|---|
1% | 1 | $500.00 |
3% | 3 | $166.67 |
5% | 5 | $100.00 |
8% | 8 | $62.50 |
10% | 10 | $50.00 |
The rates are assumptions, not page grades or benchmarks. These are ad costs only, before build, management and delivery costs. Volume isn't everything either:
Example outcome | Scenario A | Scenario B |
|---|---|---|
Ad spend, 100 clicks each | $500 | $500 |
Valid enquiries | 10 | 5 |
Qualified enquiries | 4 | 4 |
New customers | 1 | 2 |
Ad spend per valid enquiry | $50 | $100 |
Ad spend per customer | $500 | $250 |
Here the lower enquiry rate produces more customers. Suitability and follow up matter. It doesn't show that a page caused the difference.
Say each customer contributes $300 after variable delivery costs. Scenario A then leaves minus $200 after ad spend. Scenario B leaves $100. That's before website and management costs, so don't call it net profit.
Send paid traffic to a page that matches the offer. A dedicated landing page can suit, but removing navigation isn't a universal rule. Our guide to choosing a landing page or homepage for ads covers that call. Check targeting, the offer and sales handling before blaming the website.
Keep the site working after launch
Assign the ongoing jobs before launch:
software updates and access
content accuracy and contact checks
backups and recovery
renewals and response handling
Urgent security updates shouldn't wait for a monthly calendar. Hosted platforms reduce some infrastructure work. Content, accounts and apps still need owners.
Confirm what a backup contains and who can restore it. Keep website files separate from orders, bookings and enquiry records. Our guides to what to budget for after launch and website backup and recovery cover schedules and costs.
Set the actual intervals by business need and risk. Keep a small evidence register for claims, prices and credentials. Give each claim, price and privacy notice a review date. Each integration needs a backup owner.
A short website self audit
Use this as triage, not a full accessibility, security or conversion audit:
Clarity and evidence
A new visitor can name the offer and find real proof
Main task
Customers can enquire, book, buy or get support
Usability
The key path works on a phone and with a keyboard
Control and recovery
You can access key services and recover from failure
Speed and stability
Key pages load and stay stable on a phone
Measurement and next action
Records mean something, with one owned priority
Deal with critical failures first, then evidence backed improvements. Our guide to why a site gets traffic but no enquiries covers the next layer.
There's no automatic rebuild recommendation here. Pick the route that fits the problem you actually have.
Our free audit is a short, prioritised read on what to fix first.
What we recommend at Elev8d
Start with the tasks your customers need to complete. Plan the pages that support them, then choose the platform. Test the full journey before launch, and name who keeps it working.
Our care plans start from $120 a month excluding GST. You can also look after the site yourself, with everything in your name.
Frequently asked questions
Is a one page website enough?
It can be, for a narrow offer with few questions. Add pages when customers need more detail.
Which pages should launch first?
The pages behind your essential tasks: home, main services, contact and proof.
Do I need a blog?
Not at launch. Add articles when you can answer real customer questions well.
Can I build it myself?
Yes, if the scope is manageable. You'll need to test and maintain it too. Budget your time as well as the tools.
Should I use an AI builder?
It can speed up a first draft. Check every fact, image right and integration before launch.
Which platform is right?
The one that supports your editing, customer journeys, integrations and budget. Test the real tasks first.
Do I need .com.au or .au?
A .com.au suits an Australian business with an ABN or ACN. Names under .au direct are open to anyone with a validated Australian presence.
How much should I budget?
Start with the published bands above, then add running costs. The cost guide linked above has the full method.
How long will it take?
Our web design page quotes 4 to 8 weeks for our main builds. Content and feedback affect the pace.
Should I fix or rebuild?
Fix the specific fault if that solves the need. Our guide to when a site needs a redesign helps you decide.
What should I receive at handover?
Business controlled access, the agreed files and licences, training and a recovery route.
What if my developer is unresponsive?
Check what access you hold, then follow the handover checklist above. Keep the domain and email working while you switch.
Does a new website include ongoing SEO?
No. A build covers technical foundations. Ongoing content and promotion are separate work.
How will I know it helps the business?
Track suitable enquiries and completed work, not just clicks or page views.
Next steps
Fix a known fault first
Repair the broken task, then test the whole journey.
Draft your core requirements
List the tasks, pages and evidence the site needs.
Get a scoped proposal
Compare providers on the same brief and acceptance tests.
