Existing sites · No rebuild

Improve the Site You Already Have

You do not need a new website. You need the one you have to be better — more content, cleaner design, faster pages, and search visibility that holds up now that half your buyers ask an AI before they ask Google. We work on existing WordPress sites a few hours at a time, starting with the changes that cannot cost you a ranking.

Tell us what is on your list

Australian team

Based here, working your hours — not a timezone away

144+ projects delivered

Over 10+ years building and maintaining sites for Australian businesses

One developer, start to finish

The same person every time — no re-explaining your site

Straight answers, on your terms

We only take work we can finish. Ask us anything first — no obligation

If your site is fine and you just need it kept updated, backed up and online, that is a maintenance plan rather than this. If you are trying to win rankings you do not have yet, our SEO page is the better fit. And if the site genuinely is past saving, we will say so — a rebuild starts around $2,500 AUD and we would rather tell you that on the first call than three months in.

Every engagement opens with an audit you have to approve

Before anything on the site changes we go through it end to end and send you a written report — the technical SEO position, the structured data, the page speed, the indexation, and the part most audits leave out: where visitors are losing interest and enquiries are going missing. It comes with a priority list, an estimate of hours against each item, and a record of where you currently rank so that everything after it can be measured against something. Then you decide what gets done. Nothing is touched until you have signed it off, and anything capable of moving an existing ranking is marked as such so you can rule it out on its own.

Nothing that ranks gets its address changed

This is how redesigns actually lose traffic. Not through worse content — through URLs that quietly moved, a slug tidied up, a page folded into another one, a category prefix removed because it looked untidy. Every one of those is survivable with a mapped 301 and fatal without one. So the rule here is simple: a ranking URL does not move, and if it truly has to, the redirect is written before the change, not after somebody notices.

The safe fixes come first, deliberately

There is always a category of work that can only help: an empty or missing XML sitemap, a robots.txt throttling crawlers, images with no alt text, missing width and height attributes making the layout jump, an analytics script loading on pages that have no use for it. None of it touches your copy, your URLs or your titles, so none of it can cost you a position. We do all of that first. It builds the evidence that the arrangement works before we go anywhere near the pages you care about.

Title tags and headings get changed one page at a time, and measured

Older sites usually carry title tags written for a version of Google that stopped existing a decade ago — long keyword lists, city names stacked at the end, the business name last. They often still rank, which makes them genuinely risky to touch: the page is performing despite the title, not because of it. So they change in small batches on lower-value pages first, with the before-and-after positions watched for a fortnight, and the ones earning your best traffic go last or not at all. Rewriting all of them in one afternoon is how a good intention becomes an incident.

Design changes happen on a copy of your site, not on the live one

You see the new version on a private staging URL, on your phone and your laptop, and it goes live when you say so. That matters more on an established site than a new one, because there is traffic arriving the whole time the work is happening. It also means design work stops being a series of small live experiments your customers get to watch, which is what "tidying things up" usually turns into when it is done directly on production.

Being findable by AI answers is a different job from ranking

When someone asks ChatGPT or Google's AI overview about your category, the answer is assembled from sources it can parse and trust — which rewards clear structured data, unambiguous facts about who you are and what you sell, and self-contained passages that can be quoted without the surrounding page. Most WordPress sites emit a generic Organization block and nothing else, so there is nothing for a model to work with. Adding proper Product, Service and FAQ markup is invisible to your existing rankings and is the highest-leverage AI-visibility work available on a site that already has authority.

Adding products, videos and case studies should not need a developer

Growing businesses add things, and on most sites each addition is a small custom build because the last one was. The fix is to make each content type a repeatable pattern — one layout for a product, one for a case study, one for a video — so the tenth is the same amount of work as the second, and your team can add it without opening a ticket. Getting there is a few hours of setup that pays for itself the first time you launch something at short notice.

What ongoing work costs

Improvement work is bought in prepaid hours, not projects: $750 for a five-hour block or $1,400 for ten, drawn down against whatever you need that month and itemised so you can see where it went. Ad hoc work outside a block is $165 an hour. If you also want the site monitored, backed up and updated between pieces of work, care plans start at $159/mo. There is no minimum term on any of it — the arrangement should survive because it is working, not because you signed something.

What people ask before they let anyone touch a working site

What is in the onboarding audit, and does it cost extra?

It is included, it is the first thing that happens, and it does not come out of your development hours. Two halves: the search side — technical SEO, structured data, page speed, indexation, and where you currently rank — and the conversion side, which most audits skip: how people move through the site, which pages lose them, and where an enquiry that was going to happen quietly does not. You get it as a written report with a priority list and an estimate of hours against each item, it is yours to keep, and no work starts until you have picked what you want done.

We have rankings we cannot afford to lose. What actually protects them?

Three things, in order: the baseline snapshot taken before any work starts, a standing rule that ranking URLs do not move without a mapped redirect, and changes shipped in small batches so a drop can be traced to one change rather than forty. The honest part of this answer is that no one can promise a position — Google moves them for reasons that have nothing to do with your site. What we can promise is that you will always be able to tell which kind of movement you are looking at, and that anything we did can be reversed.

Do you need to move us off our current host, theme or page builder?

No. Changing any of those on a site with established rankings is a large risk taken for a benefit the client usually cannot see, and it is normally a supplier preference rather than a business need. We work in what you have. If your setup is genuinely holding you back we will show you the specific cost of staying, in numbers, and let you decide.

We are on Elementor. Is that a problem?

It is a constraint, not a problem. Page builders load more CSS and JavaScript than hand-built templates and that shows up in your loading times, but rebuilding away from one is a project, not an improvement. Most of the speed available on a builder site comes from things the builder is not responsible for anyway — oversized images, scripts loading on pages that do not use them, no caching layer — and all of that is fixable without touching how your pages are edited.

How will we know the work actually improved anything?

Because the baseline exists. Each block of hours ends with what changed, what it was before, and what it is now — positions, loading times, whichever measure the work was aimed at. Some of it will not move the number, and we would rather tell you that than describe activity. Hours you can see the results of are the only reason an arrangement like this lasts years instead of months.

Can you work on a site somebody else built?

That is most of what we do. You do not need your previous developer's cooperation and you do not need to explain why they are no longer involved. We need admin access, hosting access and, ideally, whatever documentation exists — and where none exists, the first block of hours includes working out how the site is actually put together, which is a real cost and gets stated up front rather than absorbed quietly.

What if some months we need almost nothing?

Then you spend almost nothing. Prepaid hours do not expire at the end of the month, and there is no retainer you are paying to keep a seat warm. Businesses that add products or case studies in bursts should not be on a fixed monthly developer plan — that only makes sense once you are reliably using the hours, and we will tell you when you are, because at that point it is cheaper for you.

How quickly do you respond?

Same business day for anything that is broken, and within a day for everything else. This matters more than it sounds on an arrangement like this: the reason ongoing relationships end is almost never the quality of the work, it is waiting four days for an answer to a question that took ten minutes to resolve.

Tell us what is on your list

A short call, a fixed quote, and no obligation either way.

Get a fixed quote

Other ways we work with existing sites

Why CloudyWP

You have rankings you cannot afford to lose. We improve existing WordPress sites a few hours at a time — content, speed, design, AI search — starting with what cannot cost you a position. From $750.

Get a fixed quote

02 — How we work

From first call to live — four steps, no surprises.

Every CloudyWP project runs the same way, whether it is a one-page site or a store with a thousand SKUs. Here is exactly what happens.

01

We map what you actually need.

A single scoping call, then a written plan: what gets built, what it costs, and when it ships. No discovery-phase invoices, no moving targets.

Typically 48 hours

02

We design and build it properly.

Custom WordPress or Shopify on clean code you own outright. Every build ships fast, passes Core Web Vitals, and is handed over documented.

2–6 weeks typical

03

We automate the busywork.

Your site talks to the tools you already run — CRM, invoicing, email, stock. The repetitive admin stops being someone's job and starts running itself.

Average 15 hrs saved weekly

Scope A fixed quote, in writing

Deliverables, price and dates agreed before a line of code is written.

  • Free scoping call
  • Written scope document
  • Fixed price, no hourly creep

48 hrs to your quote

Get a quote