Website Maintenance Cost [2026]: What You Pay For, and Why

website maintenance cost — what it means

Website maintenance cost is the collective term for what it takes to keep a published site running: the domain, the server, CMS and tool subscriptions, maintenance work, and update services.

Hi, I’m Masato, a Webflow specialist. I run Webharu, a web production company in Shiogama, Miyagi, Japan.

“Can you explain what the maintenance fee you pay every month actually buys?”

Ask a production company about website maintenance costs and the answer is often vague. Being told “maintenance, all in, ¥20,000 a month” tells you nothing about what sits inside that line, so you have no way to judge whether it is expensive or cheap. And until you know what is safe to cut and what is dangerous to cut, you cannot even start a review.

The conclusion first.

Once you can break down what you are paying for and how much, you can judge for yourself whether your website maintenance cost is fair. The going rate runs from almost ¥0 to over ¥30,000 a month depending on the technical setup, and most of that gap comes not from how hard you negotiate but from how the site was built. This article lays out the cost items like a dictionary, then covers the going rates, how to audit your invoice, and the setup that lowers maintenance structurally.

A dictionary of website maintenance costs

We say “maintenance cost” as if it were one thing, but it is the sum of several costs of very different natures. Start by sorting out what the money is actually for.

Item	What the cost is for	What happens without it
Domain	The cost of holding your site’s address, such as example.com. It has to be renewed every year	Stop renewing and you lose the URL itself — a third party can pick it up
Server / hosting	The cost of the place that stores your site’s data and serves it to visitors	If it stops, the site stops appearing
SSL certificate	The cost of encrypting traffic and serving over https. Most services now include it free, renewed automatically	When it expires the browser shows a warning, which costs you visitors and trust
CMS and tool subscriptions	Subscription fees for continuing to use the production tools themselves — WordPress plugins, Webflow, and the like	Stop paying and you may lose the ability to edit or publish at all
Maintenance work	Backups, system updates, security monitoring — the work that keeps the site from breaking or being hijacked	Left alone, vulnerabilities pile up and the risk of defacement or broken layouts rises
Update service	The cost of asking your production company to handle day-to-day updates such as swapping text and images	If you cannot update it yourself, the information on your site sits there going stale

What matters here is that these are, by nature, six independent costs. Most contracts bundle them into a single line called “maintenance” or “management,” which hides which of the six you are actually paying for.

More than that, it is natural for the six to be billed by different parties. The domain comes from a registrar, the server from a hosting company, the CMS and tools from the tool vendor, and the maintenance and update work from the production company. Separate payees are the normal state of affairs, so when everything is consolidated into one company it is worth confirming the what-and-how-much in your contract.

Some of the six you can control yourselves to a degree. Putting the domain renewal date in your calendar, or simply using the SSL that now ships as standard with most hosting, takes no special skill. Maintenance work such as security monitoring and system updates is specialist territory, though, and I would not recommend taking it in-house. Drawing a line around what you can handle yourselves makes it clear what to hand outside.

One more thing that gets missed: the mismatch in billing cycles. Domains, SSL, and CMS or tool subscriptions are usually billed annually, while maintenance and update work are billed monthly. Staring at invoices with the two mixed together gives you no common axis. When you review, divide the annual items by 12 and add them to the monthly ones so everything lines up as a real monthly figure — that makes comparison against other vendors or other setups far easier.

What the going rates look like

Honestly, the going rate for maintenance moves by several multiples depending on how the website was built. Here are the numbers I can speak to, by technical setup.

Setup	Is maintenance work required?	Rough maintenance cost
WordPress	The core, themes and plugins need continuous updating, plus backups	Maintenance fees center on ¥10,000–30,000 a month (¥120,000–360,000 a year). Domain and server costs come on top
Subscription tools such as Webflow	The vendor handles backups and patching collectively, so maintenance work itself rarely arises	Under the pricing revised in May 2026, the tool fee is the main cost: $15/month for Basic and $25/month for Premium with the CMS on annual billing (roughly $180–300 a year)
Static site	With no page-assembly program on the server, maintenance work barely arises	On our own site the real figure is the domain alone: ¥1,500 a year

WordPress maintenance sits in that ¥10,000–30,000 band because updating the core, themes and plugins, taking backups and monitoring security keep coming round. The flip side of open-source freedom is that a neglected site becomes an easy target, and that maintenance work has become a specialist job in its own right.

The cost of a subscription tool like Webflow is a slightly different animal. It is less a fee for maintenance work than a license to keep using the tool. Because the vendor handles backups and security patches collectively, the maintenance work that lands on the user shrinks. I have written up Webflow’s plans in detail in our article on Webflow pricing (the current official prices are on Webflow’s pricing page).

From here on it is my own experience. In July 2026 we gave our own site a full rebuild with AI (Claude Code) and moved it to a static setup that simply serves pre-built HTML files. Maintenance is now the domain fee alone: ¥1,500 a year. Back in our Webflow days it ran to nearly ¥100,000 a year including localization, so changing the setup alone cut maintenance to about one sixtieth. The next chapter digs into how that works.

Stretch the timeframe and the difference gets easier to feel. Over three years, running on WordPress costs ¥360,000–1,080,000 in maintenance fees alone (domain and server on top). A static site, in our own case, costs ¥4,500 — three years of domain fees. The right setup depends on the features and purpose your site needs, so this is not a simple better-or-worse comparison; treat it as a sense of the scale the gap can reach.

So why not make everything a static site?

Reading this far you might think “then just make everything static,” but it is not that simple. Sites that need data to change on every visit — member logins, a booking system tied to live inventory — need a dynamic mechanism in the first place. Static sites keep maintenance low for corporate sites, recruitment sites and blogs, where post-launch updates are mostly swapping content and no complex real-time processing is required. Work backwards from your functional requirements to decide which camp your site is in.

The difference in maintenance cost is almost entirely a difference in technical setup, not in how skillfully you negotiate a contract. The same word — “website” — covers something that assembles pages on the server on every visit, something riding on a subscription tool, and something that just serves finished HTML, and the work and cost involved are completely different. It is not a question of good and bad; the dividing line is whether the setup matches the site’s purpose and scale.

What is actually in that maintenance fee? How to check

If you are paying a maintenance fee now, take out the invoice and the contract and check the following. I would recommend deliberately creating a moment to review this at least once a year. Circumstances change after signing, but without a review the contents never get updated.

1. Is the work described in concrete words?: An invoice that says only “maintenance, all in” or “management fee,” with no explanation of what is being done, deserves attention. Ask them to describe the included work in words — backups, system updates, monitoring, minor fixes.
2. Scope and monthly limits: Confirm the conditions: how many text fixes per month, whether incident response is included in the fee or billed separately. If there is no limit, that should be reflected in the price.
3. How often the work is actually performed: Is it scheduled monthly work, or does it only happen when you ask? If they advertise round-the-clock monitoring, it is worth asking how (automated or human).
4. Whose name is on the domain and server: Whether they are inside the maintenance fee or billed separately, and whether they are registered in your own company’s name, connects directly to the switching question below.
5. Will they show you the work history?: Whether they will show you a record of what was done and when — update logs, backup timestamps — is also evidence of whether the work is real.
6. Continuity of the team: Is one individual responsible, or a team? If you have hired a sole trader, factor in the risk that maintenance stops suddenly if they fall ill or change direction.

Asking your current provider this may feel awkward, but an equal business partner should have no trouble answering. In fact, whether they answer carefully is itself a signal about whether to keep working with them.

A template you can send as-is

If you are not sure what to ask, ask these three.

• “Could you list, item by item, the work included in our current maintenance fee?”
• “Are the domain and server contracts registered in your name or in ours?”
• “If we cancel, in what format would we receive the full set of data?”

How concretely they answer those three tells you a great deal about how transparent the provider is.

To be blunt, invoices issued as a “management fee” with almost no actual work behind them do exist in this industry. That is not always malice. In plenty of cases the explanation was vague at signing and the billing simply carried on without the contents ever being updated. If your contact cannot answer the questions above concretely and immediately, a review is worth considering.

On the other hand, a high maintenance fee is not in itself a bad thing. For a site carrying complex systems — member features, inventory integration — a near-dedicated team and a higher fee are entirely reasonable. The question is not the size of the number but whether work matching it is actually being done.

The “¥300,000 a month for almost nothing” maintenance deal I heard about

Here is something I was told first-hand. I have heard of a peer earning ¥300,000 a month maintaining another company’s site. Managing sites for large firms or hospitals, there really are clients paying around that much. But by their own account, almost nothing was actually being done.

It is not good form to reveal this much about the industry, but frankly, that is a rip-off. Paying that kind of money for maintenance nobody can explain is something I would advise against. ¥300,000 a month is ¥3.6 million a year — enough to rebuild the whole site and get change back.

To avoid any misunderstanding: ¥300,000 a month for maintenance is not always unreasonable. For a large e-commerce site, or a project that includes 24-hour monitoring, security requirements and regulatory compliance, there is substance to match that number. The issue is not the number but whether the substance can be explained. A ¥300,000 you cannot explain and a ¥300,000 you can are, to my mind, entirely different things. If you are paying that much, run through the checklist in the previous chapter — is the work described in words, is the work history disclosed?

The setup that brings maintenance close to ¥0

The table above said a static site can cost the domain fee alone. Let me dig into why that is possible.

A site like WordPress pulls information out of a database on the server every time a visitor arrives and assembles the page on the spot. Keeping that assembly mechanism running safely is what requires the continuous work — server administration, program updates, security patches. Most of a maintenance fee is payment for that work.

The analogy is a restaurant that cooks every order from raw ingredients versus a shop that reheats dishes prepared in advance. The first has to keep a full prep-and-cook operation running at all times; the second, once the prep is done, only has to hand things out.

A static site, by contrast, builds the finished HTML files before any visitor arrives and simply delivers them through a CDN (a delivery network of servers placed around the world). Because there is no page-assembly program on the server, there is no program to update and no plugin to break into. The reason almost no fixed cost arises beyond the domain fee is this structural difference. Our own site runs on ¥1,500 a year not because of any special cost-cutting effort, but because of that choice of setup.

For context, a CDN places copies of your files at multiple locations worldwide in advance and serves each visitor from the nearest one. Display speed tends to be steadier as a side effect, but that is a speed story rather than a maintenance-cost story, so I will not go deeper here.

There is one thing I want to say honestly at this point. “Maintenance is close to ¥0” is not the same as “there is nothing to do.” Technical maintenance work shrinks, but work that is required regardless of setup remains.

• Keeping information current (price changes, new services, added case studies — the freshness of the content itself)
• Improvements driven by traffic data (which pages get read, where people leave, and doing something about it)
• Regular checks that the contact form and external integrations still work

Even if you succeed in lowering maintenance structurally, stopping the updates leaves you with a site that merely runs while its information goes stale. That has to be separated from technical maintenance cost and thought about on its own. “Cheap to maintain” and “fine to neglect” are different things.

What to check when you cancel or switch

When you review your maintenance costs, or switch production companies, there are things to confirm beyond the price.

Is the domain registered in your own company’s name?

Where the production company handles domain registration and management on your behalf, the name on the record is sometimes theirs rather than yours. Switch in that state and you can end up letting go of the domain along with the provider. It is worth confirming that the domain is in your name before signing — or right now.

Will they hand over the data?

Confirm in what format the design files, copy, image assets and the site content itself will be handed over on cancellation. Under a contract where the data exists only inside the production company’s admin panel, your next provider has to rebuild from zero, which costs more money and more time in the end.

Some contracts mean the site disappears when you cancel

If the site is built on a subscription tool, publication itself can stop the moment the license lapses. That is not a matter of the tool or the provider being good or bad; it is a fact about the contract that you should understand up front. Before cancelling or switching, always confirm what state the site will actually be in.

Contract term and auto-renewal clauses

Annual maintenance contracts and tools often carry a clause that renews for another year automatically unless you give notice. Checking the cancellation clause in advance — how many months of notice are required before the date you want to stop — avoids paying for a year you did not intend to buy.

The real cost of a “¥0 setup fee” arrives when you leave

I have never personally had a dispute over the domain registrant or the handover of data. But it is a common story on other projects.

Be careful especially with the outfits advertising “budget” deals — ¥0 websites, subscription models. The setup fee is ¥0, but the moment you say you want to bring management in-house, a site migration fee of several hundred thousand yen — sometimes more than the setup fee would have been — is very commonly charged.

And the sites you can build under a ¥0 deal are, for the most part, a customized template. They cannot really do the work of bringing in customers, and they do not build a brand either. Companies charging ¥500,000 to ¥1,000,000 for exactly that exist as a matter of routine.

I have also heard of a peer charging around ¥200,000 simply to hand over a domain. I would rather not call them peers at all; their business model is securing the rights first, getting a contract signed, and binding you with clauses nobody understands, so this is something I sound the alarm about loudly.

Which is why the thing to confirm before signing is not the price so much as what happens when you leave. Whose name is the domain in? If we cancel, will we get the data? Will there be extra fees to migrate? Confirm those three in writing before signing and nobody can hold you hostage later. If they are reluctant to answer, that in itself is information.

For what it is worth, the migration work at the receiving end normally costs money too. In our case, migrating from an existing site is a +¥80,000 option. When you are considering a switch in order to lower maintenance, include that migration cost and work out how many years it takes to pay back — it keeps the decision steady.

Confirm the three points — registrant, data, contract clauses — and not just the price, and switching becomes a move to a better position. Skip them and an attempt to lower maintenance can generate extra work and extra spending instead.

How we do it

Finally, here are our own maintenance-related prices, stated as fact.

Our Site Care Plan starts at ¥15,000/month. What it contains: a single point of contact for post-launch updates and maintenance, where fixes and additions are reflected just by sending an email, paired with continuous improvement proposals. What you can ask for is mostly the small day-to-day work — swapping text, reflecting a price change, adding a new announcement.

¥15,000 is the figure for a minimum configuration; the actual monthly fee is proposed individually after we hear about the content and frequency of your updates. On the applicable plans we include a mechanism where posting to Instagram automatically updates the news on your site (built on our own operations platform). It is designed to reduce the situation where you pay a maintenance fee and still end up writing the text and sending it over yourself.

What we actually do each month

For the companies whose sites we operate, what we mainly do is a traffic report and a monthly meeting. That is where we decide the marketing direction.

Honestly, our monthly fee sits well at the budget end. Even so, holding a meeting with each client and presenting a clear direction is, I believe, why it is trusted as an honest engagement rather than as mere maintenance or operations.

On top of that: our own CMS features, AI-driven traffic analysis reports, and continuously tracking the latest developments and passing them on — we put weight on delivering the newest technology with the newest AI built in, so that is part of the monthly meeting too.

One thing to state honestly: the cheapest plan does not include meetings. Meetings start with the ¥50,000/month plan. Put the other way round, on the ¥50,000/month plan we catch up on the latest in AI every month and apply it to your site on our own initiative. The client has to do nothing. For ¥50,000 a month you get a website kept in its latest state, managed with the latest AI — that is the design.

Measured against the going rate for maintenance, that is not at the expensive end. What makes it different from the “¥300,000 a month for almost nothing” case above comes down to one thing, I think: every month, what was done and what comes next is put into words and left on the record.

The most wasteful thing about maintenance costs is judging them as “feels expensive” or “feels cheap” without knowing the breakdown.

If you are at the stage of not knowing whether what you pay now is high or fair, that conversation is welcome too. We are happy to go through the invoice for a site currently contracted elsewhere. The full picture of our pricing is on the pricing page, and the structural difference from WordPress is covered in our Webflow vs WordPress comparison. The rough setup and maintenance costs of a rebuild are on the pricing page as well. Start with a free consultation and we will break down your current invoice together.

FAQ

What does website maintenance cost on average?

It runs from almost ¥0 to over ¥30,000 a month depending on the technical setup, so no single average describes reality. WordPress centers on ¥10,000–30,000 a month in maintenance fees alone, while a static site can be the domain fee only — ¥1,500 a year in our own case. Confirming how your site is built comes first.

Do I always need a maintenance contract?

It depends on the setup. A site with a dynamic mechanism accumulates vulnerabilities if neglected, so a maintenance contract is effectively necessary. A static site, by contrast, generates little maintenance work, so going without a contract carries much less risk.

What happens to my site if I cancel the maintenance contract?

It depends on the contract. If the site is built on a subscription tool, publication can stop the moment you cancel. Before cancelling, always confirm whose name the domain is in, in what format the data will be handed over, and what happens to the published site.

What is the single most effective way to lower maintenance costs?

Reviewing the technical setup itself, rather than negotiating the maintenance fee. Work out whether you really need a mechanism that assembles pages dynamically; if you do not, moving to something like a static site lowers maintenance structurally.