Melbourne Accountant: Website Changes Over Three Months

A Melbourne accountant had been running the business for eight years. They were doing okay. Steady client base through referrals and networking. The kind of work where word of mouth actually works, at least for a while. They weren’t struggling to pay rent or anything like that.

When we first talked, they mentioned their website basically didn’t exist as far as Google was concerned. Not in a self-aware way, more like they’d just noticed they weren’t getting any inquiries through it. They’d tried fixing it before. Hired someone to improve it. Posted some articles about accounting topics. Nothing shifted. The inquiries still came from the same places they always had. Referrals from clients. Connections through their local network. The site just sat there.

What stood out talking to them was how little frustration there actually was. Eight years of a website doing nothing for the business, and their response wasn’t anger, it was closer to resignation. They’d tried once, it hadn’t worked, and they’d more or less filed the whole thing under “not something that works for us” rather than “not something that was done properly.” That’s a common pattern with service businesses that have a working referral network already. The website’s failure doesn’t threaten the business, so there’s less urgency to actually diagnose why it failed the first time.

I looked at the site to see what was happening. The homepage was generic. The kind of thing that could’ve been written for any accountant anywhere. It talked about services in vague terms. Bookkeeping. Tax. Financial planning. But it didn’t really explain who they worked with best or what made them different. More importantly, technically it was a mess. Missing the basics that Google uses to understand what a website’s about. No proper sitemap. Schema markup wasn’t there. Articles existed but they were scattered all over the place, not connected to anything. Each one felt isolated.

The previous attempt at fixing this had focused entirely on content, more blog posts, without touching any of the technical foundation underneath it. That’s a common mistake, and an understandable one, since content is the visible, tangible part of SEO work, the part a client can actually read and evaluate. Sitemap configuration and schema markup are invisible unless something’s actively broken, so they’re easy to skip past even when they’re the actual blocker.

We started with what felt most straightforward. Rewrote the homepage so it actually said who they worked with. We made it specific. Accounting for small business owners in Melbourne. That kind of thing. Then we fixed the technical foundation. Proper sitemap. Schema markup. Mobile optimisation. The boring stuff that nobody notices but Google cares about. If you’re curious about what that process actually involves, there’s a guide on setting up your website for rankings that walks through the technical side.

The sitemap issue specifically turned out to be simpler than expected but more consequential than expected too. The site had one, technically, but it hadn’t been updated in years and referenced several pages that no longer existed while missing most of what had actually been added since. Google was working off a map that didn’t match the territory, which is roughly as useful as it sounds. Regenerating it properly and resubmitting it through Search Console took an afternoon. The schema markup took longer, mostly because it meant going through every service page individually and making sure the structured data actually described what was on the page rather than a generic template that had been copy-pasted across all of them without adjustment.

Then came the content. We wrote twelve articles. Not random topics. All connected to accounting and business finance. Bookkeeping best practices. Tax planning for small business. Entity selection. Cash flow management. Things that business owners actually search for when they’re trying to figure stuff out. And we linked them together. Not forced, but natural connections. This article mentions that concept, so it links to the article that explores it more. That creates what search engines call topical clustering. Shows Google that the site knows about accounting as a subject. The idea is that if you’re writing about a topic from multiple angles and connecting them, Google starts to treat you differently than a site that just has random articles everywhere.

Picking the twelve topics took longer than writing any individual one. The temptation is to write about whatever seems interesting or whatever the accountant personally finds engaging, but that’s a different exercise from writing about what an actual searching business owner types into Google at eleven at night trying to work out whether they need a bookkeeper or an accountant, or whether their side business needs to register for GST yet. Those specific, slightly anxious, practical questions turned out to be the ones worth answering.

The first month felt like nothing was happening. We did the technical work. Rewrote the homepage. Started publishing articles. The accountant asked if they should see results yet. I said probably not. Google takes time to notice changes. Sometimes weeks. Sometimes longer. They seemed to accept that but you could tell they were wondering if this was actually going to do anything.

That first month is genuinely the hardest part of a project like this to manage, not technically, but in terms of the relationship. There’s nothing to show. No traffic graph moving. No new inquiries. Just a promise that the invisible groundwork will eventually surface, based on a process the client generally has to take on faith since they can’t see search engine crawling and indexing happening behind the scenes.

Month two was when things started shifting. The new articles were getting indexed. We started seeing them show up in search results, but for specific, longer keyword phrases. Long-tail stuff. The kind of search where someone’s already pretty far along in figuring out what they need. “Tax deductions for small business owners” or “bookkeeping for retail business”. Not the broad searches. But inquiries started coming through the contact form which honestly surprised me given how long it took to get even that much momentum. If you’re wondering why sites don’t rank at all before they start ranking for anything, there’s some context on what usually stops websites from appearing in search that might make this timeline make more sense.

The accountant mentioned they were noticing more emails. People asking questions about their services. Most of them came from Google search now. That was new. For years the emails had come from networking events or referrals. Suddenly there were people they’d never met finding them online because they’d searched for something specific and the website showed up.

By month three, the traffic had shifted noticeably. We were looking at somewhere around 150 visitors a month from Google. That doesn’t sound like a lot if you’re thinking about consumer websites with thousands of visitors. But for a local accounting business, that’s a steady stream of qualified people. People actively searching for accountants. Ranking for maybe 30 different keywords instead of zero. The site was showing up in searches.

The inquiries kept coming. I didn’t track whether those inquiries actually turned into clients. That wasn’t my part of it. What the accountant actually converted into paying customers depends on a lot of things. How they respond to inquiries. Whether they’re a good fit for each other. The price they quote. How they follow up. All of that’s outside the website.

What I knew was that Google was now sending them people when previously nobody was finding them that way. For eight years the website had generated essentially nothing. Now it was generating a steady trickle of inquiries. Whether that translates to revenue is something only they could answer. But the basic thing changed. The website went from invisible to visible.

Why did this work in this case? It’s hard to isolate. The technical setup meant Google could understand the site. The clarity on the homepage helped. The volume of content gave Google more pages to index and rank. The topic clustering showed expertise in accounting specifically. All of that happened at the same time so separating out which part mattered most would be guessing. If you want to know how these pieces usually fit together, there’s a fuller breakdown of how search visibility actually builds that covers the general approach.

If I had to guess at a ranking of what mattered most, purely a guess, I’d put the technical foundation first. Without a sitemap Google could parse and schema markup it could read, none of the content work would have had anywhere to land. The homepage clarity probably mattered second, since it’s what determines whether a visitor who does arrive actually understands what they’re looking at. The content volume and clustering feel like they mattered most for the specific long-tail rankings that started showing up in month two, since generic content doesn’t tend to rank for the more clearly specific searches that were bringing inquiries in.

What I can say is that they changed multiple things at once and the traffic changed. Whether the same approach would work the same way for a different business in a different situation, I don’t know. This was a local service business. Mature. Established reputation. So Google starting to send them traffic meant qualified inquiries. For a different type of business the whole equation might be different.

It’s also worth being honest about what three months doesn’t tell you. Search visibility that appears quickly can sometimes fade just as quickly if the underlying content doesn’t hold up over time, or if a competitor makes a similar move and starts competing for the same long-tail terms. Three months is enough to say something changed. It’s not enough to say the change is permanent, and I’d be cautious about anyone who claims otherwise after a timeframe this short. The honest version of this case study ends with a question mark on durability, not a guarantee.

The accountant seemed satisfied. They got what they were looking for. A website that actually contributed to their business instead of just existing. Whether it becomes a major source of new clients, that’s their story to write. But at least now it’s not invisible.

Looking back, the one thing I’d change is how the previous failed attempt got handled at the start. I spent very little time actually understanding what that first agency did and didn’t do, mostly because the accountant themselves wasn’t entirely sure either, just that “nothing worked.” A more thorough audit of the previous work before starting fresh might have surfaced the missing sitemap and schema issues in week one instead of them turning up as part of the general technical review. Not a big miss, but the kind of thing worth doing more deliberately next time rather than assuming a clean slate is the safer starting assumption. It’s also a reminder that “nothing worked” from a client rarely means literally nothing changed, it usually means nothing changed enough to notice, which is a different and more diagnosable problem.