Do I need a new website or is my old one actually fine?

Agencies that sell rebuilds tend to recommend rebuilds. Funny, that. Most websites don't need replacing because they've had a few birthdays. Keep yours if customers use it successfully, the details are right and enquiries arrive. Fix the broken bits. Rebuild when the platform keeps blocking work the business needs.

In short: A website's age tells you very little. Keep it when it does the job, repair contained faults and rebuild when the underlying setup keeps getting in the way. The problem decides the scope.

When should a business redesign its website?

Redesign when the site stops customers doing something important or makes updates a wrestling match. Start with the failed task, not the year in the footer.

When an owner asks “do I need a new website”, I want the fault list. Does the mobile menu open? Does the contact form reach the right inbox? Are the services and opening hours correct? Write down anything staff can't update without breaking the page.

Mobile deserves a test. The Australian Communications and Media Authority reported that 97% of Australian adults accessed the internet through a mobile phone in 2025, up from 95% in 2024. Turn off the office Wi-Fi, stand in the car park on 4G and try the main customer task. That'll tell you more than a designer's monitor will.

Accuracy isn't decorative. The Australian Competition and Consumer Commission says claims about products and services on websites must be accurate and truthful. Wrong service details or availability need fixing now. They don't automatically justify throwing out the whole site.

If several important tasks fail and each repair uncovers another platform limit, a redesign has a job to do. Our custom website design for Brisbane businesses covers new builds, careful rebuilds and approved additions to suitable custom-coded sites. We look at the fault before deciding what belongs on the quote.

Do I need a new website if mine still works?

No. If customers use it without trouble and your team isn't frightened to update it, keep it working.

Use this keep, fix or rebuild test against what the site actually does.

Say you run a plumbing business and the site was built in 2016. The phone number is right, the services are clear and the contact form works on 4G in a car park. Leave it alone.

Now change one thing. The form works, but the mobile call button sits under a cookie banner. That's a fix. Move the button, test it on a few phones and check the enquiry arrives. The fault has clear edges.

Change the foundations and the answer changes. The owner needs separate pages for emergency plumbing and hot-water work, but the old builder can't create them without copying broken layouts. Updating the menu triggers a plugin error, and the last backup has never been restored successfully. The website hasn't become a rebuild candidate because it turned ten. The setup is blocking ordinary work.

Screenshots don't decide that job. Test the customer path, make an ordinary update and ask for the maintenance record. Two tired websites look similar yet need different scopes. The fault list decides.

Age doesn't tell you which job you're looking at. Tests do. Use the evidence, not whatever date appears in the footer.

Open the pages customers use, send an enquiry and tap through the navigation on a small screen. Analytics shows where visits stop. It won't tell you that the form email has landed in an abandoned inbox since February, so test that too.

A rebuild creates work even when it goes well. Content needs checking and search engines process changed pages. The design industry will survive if you don't replace a functioning homepage this quarter. Put a date in the calendar to run the test again, then get back to today's business problem.

Can I fix my old website instead of replacing it?

Yes, if the problem has edges. Repair it.

Fix the unclear service page, enquiry form, mobile layout or analytics, then test the work. If visibility is the real complaint, SEO services in Australia might be the right job. If people arrive but don't enquire, check these conversion-killing mistakes before blaming the codebase.

A new colour palette won't repair a dead contact form. It'll make the dead contact form prettier.

The calculation changes when the builder, theme or WordPress plugin stack blocks the work. Another workaround looks cheap until routine updates knock over unrelated pages and nobody remembers which plugin holds the lot together. At that point, replace the underlying setup instead of adding another layer.

At LUNA Systems, we build custom-coded sites rather than Wix, Squarespace, WordPress, purchased themes or general page builders. That doesn't mean we'll tell everyone on those platforms to rebuild. A maintained site with no defined customer failure is a poor rebuild candidate. So is one whose real trouble is weak photography, muddy copy, slow follow-up or an offer people don't want. New code won't fix those.

For plenty of businesses asking “do I need a new website”, the answer is a repair list with an owner and a test beside each item. Finish the list and stop. If the setup keeps blocking the work, you've got evidence for a rebuild.

Is an old website a security risk?

It might be. The useful test is whether the software remains supported, patches are applied, access is controlled and recovery has been tested.

On 9 July 2026, the Australian Signals Directorate's Australian Cyber Security Centre warned of a large-scale campaign targeting website content management systems. Its table named 17 affected products, including 11 WordPress plugins, and said publicly known vulnerabilities with available patches were being exploited. That's a maintenance warning. It doesn't prove every old website or every content management system is unsafe.

Ask whoever maintains the site for evidence:

• Which software components still receive updates?
• Who patches and checks the site?
• Who has administrator access, and do they still need it?
• When did someone last restore a backup successfully?

Good answers strengthen the case for keeping the site. Unsupported software, unknown administrators or a backup nobody has tested strengthen the case for change. A rebuild doesn't remove the job. The new system still needs controlled access, maintenance, monitoring and working backups.

Don't rush the handover either. The domain, content, analytics and approved connected accounts should stay with the client. LUNA Systems clients own all four. That keeps responsibility visible while the work changes hands and leaves the business in control of its own property.

What changes for a healthcare website redesign?

Use the same test, with stricter checks around patient access, advertising claims and the route into the clinic. A polished home page doesn't excuse confusing patient information.

Accessibility belongs in the main job. The Australian Bureau of Statistics reported that 5.5 million Australians, or 21.4% of the population, had disability in 2022. Among people aged 65 and over, the figure was 52.3%. Check readable text, useful headings, keyboard access and forms that explain errors in plain English.

Say a clinic receptionist changes opening hours twice a year, but one edit knocks the booking button sideways on mobile. That's a contained fault if the rest of the site behaves. Fix it and test it. If the page builder makes every routine change risky, the underlying setup is now part of the problem.

Test patient tasks on a phone. Someone should find the address, opening details, patient information and contact route without decoding the menu. The form should ask for information the clinic genuinely needs. These jobs belong inside medical clinic web design, not on a tidy-up list after the pages are built.

Advertising content needs a separate review. A website compliance check helps identify pages that need attention, while the clinic remains responsible for what it publishes. This article doesn't assess individual health claims or practitioner credentials.

Keep the clinic site if patients use it and staff maintain it safely. Fix contained faults. Rebuild when the structure prevents accurate, accessible information from being maintained reliably.

Will a new website hurt my Google rankings?

Rankings can move during a rebuild. Good migration work reduces avoidable risk, but nobody guarantees every position will stay put.

Before changing anything, list the URLs that already bring useful visits, enquiries, links or rankings. Keep the ones that still make sense. If a URL has to change, redirect it to the closest relevant replacement instead of tipping everything onto the home page. Preserve useful internal links, page titles, descriptions and canonical tags when they're still accurate.

We treat migration as part of a LUNA Systems rebuild. The work includes:

• inventorying valuable URLs before the build starts
• keeping those URLs when they still make sense and mapping redirects when they change
• checking internal links, metadata and canonical tags
• connecting analytics so activity remains measurable
• checking indexation after launch

A handsome homepage won't rescue a valuable service page lost in migration. Rankings might still move after those checks. You should hear that before approving the rebuild.

If the site needs a visual tidy-up, changing the URL structure creates needless work. If the structure is genuinely poor, preserving every old path preserves some of the problem. Judge each page on its value now.

What should I do after the test?

Write down the failures and put each one under keep, fix or rebuild. If the evidence is mixed, get the existing site reviewed before anyone scopes a replacement.

Bring the real problems. Note which customer tasks fail, which updates staff can't make, what maintenance evidence is missing and which pages already matter to the business. A broken booking path is a customer task. Unsupported software needs prompt maintenance, one responsible owner and a backup somebody has actually tested. An outdated service page is a content problem. They don't all need the same answer.

Use that list to brief whoever reviews the site. The review should say what stays, what needs work and why. If rebuilding is the right call, it should also identify the migration work before pages start moving.

Ask for the smallest scope that fixes those failures. If a repair does it, stop there. If the platform blocks the repair, make the rebuild scope include migration, ownership and the checks after launch. The scope should trace back to the fault list.

If your answer to “do I need a new website” is still uncertain, Book a discovery call or Send us a message. We review the existing website before every LUNA Systems discovery call, and that call usually takes 15 to 30 minutes.