A website can feel outdated for several reasons. The service pages might describe work you no longer do. The mobile enquiry form might ask for information customers rarely have on hand. The platform might make it difficult for staff to publish anything without a developer. Those problems call for different scopes, even if they all surface in the same meeting as a request for a redesign.
Before commissioning a website redesign in Melbourne or Richmond, write down what a customer or staff member should be able to do more easily after the work. Then trace what gets in their way today. A short review of the evidence can turn a vague decision about spending into a choice between specific jobs, each with a clear way to tell whether it is finished.
Start with a task someone struggles to complete
Choose a real task, such as checking whether you serve a suburb, comparing two services or requesting an appointment on a phone. Give it to someone unfamiliar with your site and watch where they hesitate. Have them explain what they thought would happen before clicking. A menu that looks tidy to the people who built it can still be confusing to a customer who uses different words for the same service.
Run the same exercise with a staff task. Ask the person who maintains the website to change a service detail and check how it appears across the site. If they have to make the same edit in five places, the problem may be how content is stored and reused. Record the pages involved, who can make the change and which step creates delays. That record gives a supplier enough detail to propose work you can compare.
Pay for targeted updates when the problem is local
Small updates are a good fit when you can point to a handful of pages or a single step in the journey. Examples include fixing a form error that appears on mobile, rewriting a confusing service description or making opening hours consistent on the homepage and contact page. Write a simple acceptance check for each task. For a form fix, that could mean submitting with a phone, checking the confirmation and verifying that the right inbox received the message.
Consider what else depends on the component you are changing. A button reused across twenty pages may be a quick fix in a shared template, followed by checks in several contexts. A page built separately from every other page could require more manual work. Ask the supplier to say which version they found, which pages they intend to touch and how you can review the result before it goes live.
Refresh a shared template when the same issue keeps appearing
There is useful middle ground between isolated edits and a full redesign. A Richmond business with a growing range of services might keep its existing platform and refresh the service page template. That could give each page a consistent place for scope, practical examples and an enquiry link while retaining the underlying content editing process. Test the proposed template on an uncomplicated page and a page with long, dense information before applying it across the site.
Separate the template work from the content work in the quote. A new layout will not supply missing photos, explain service eligibility or decide who responds to enquiries. Assign those jobs to specific people and estimate their time. If one pilot page takes a week to approve because nobody owns the copy, solve the approval problem before scheduling twenty more pages for the same month.
Consider a redesign when the structure or platform limits the work
A redesign is easier to justify when several problems share a cause. For example, a business may have added divisions over time until visitors must choose between menus organised around internal teams. Reworking navigation alone may help, but the right scope could include a new page structure, shared service templates and a way to update recurring information from one place. A rebuild can also be worth assessing when the current platform makes routine upkeep difficult or cannot support a workflow the business needs.
Ask the developer to demonstrate the limitation with your current site, then explain the alternatives. You should understand how the proposed approach changes the daily work of editing pages, managing permissions and testing releases. Request a trial of the editing workflow early. A polished design review tells you how a page looks, while a representative editing task tells you whether your team can keep it accurate next year.
Compare quotes using the same scope and time horizon
Give each supplier the same sample pages, known issues and acceptance checks. Ask them to break out discovery, writing, design, development, migration and launch support where these apply. Confirm who supplies photography, who checks old links and who owns the accounts after launch. Some proposals may include these tasks, while others may expect your team to handle them directly.
Set a time horizon that matches how the business plans its spending. For that period, compare initial work, renewals, hosting, support and the staff time needed to make routine changes. Ask for the assumptions behind any allowances. If a supplier limits migration to ten pages, count the pages you intend to keep and ask what happens to the rest. For a broader budget breakdown, read our guide to small business website costs in Australia.
Protect existing search and enquiry paths during a redesign
Export the current sitemap and check which URLs already attract visitors or have useful external links. Decide which URLs can stay in place. If a page needs to move, map the original address to the closest useful replacement and test a permanent redirect before it is relied on by visitors. Google provides a site move checklist that covers redirect mapping, canonicals and sitemaps when URLs change.
Test the actual jobs people do after landing. Check a contact submission, booking or quote request from a phone and confirm that staff receive what they need. If you track enquiries in analytics, verify that a completed submission records a single event and that a failed submission does not. Save the date of the change alongside your baseline figures so you can tell which reporting periods include the new experience.
Choose the smallest scope you can test
Set a review date and decide who will make the call. For example, after a fortnight, review a sample of enquiries with the staff who handle them. Check whether customers provide enough information to receive an answer and where they still ask for clarification. Keep a short list of issues that recur across several pages. That list can help you decide whether a second round of edits is worth funding.
Write a decision in one sentence. For example, “Update the services template so visitors can check coverage and request a call from a phone.” Attach the pages involved, the person responsible for content and the checks you will use. If the pilot still leaves an important task blocked by the existing platform, use what you learned to set the redesign scope and identify the part that actually needs rebuilding.
CLAB Australia helps businesses assess existing websites and plan changes from Richmond, Melbourne. Bring an example of what is difficult today and the pages involved. Explore our website maintenance service for a focused review, see our website development service for larger changes, or discuss your website priorities with us.
