How Much Does Website Maintenance Cost: Domain, Hosting and Labour?
Website maintenance costs also include labour: someone updates the software, backs up the site and checks that it works. We explain how to calculate annual spending.
How much does website maintenance cost? Our clients pay €1,500–9,000 a year for maintenance work on a small business WordPress website: the lower end covers only critical updates and minimal maintenance, while the upper end includes new features, because we do exactly what the client requests. Domains, hosting and paid licences cost extra, but these are usually smaller items, as most of the cost is human labour: updates, checking them and taking action when something goes wrong. To understand the cost for your own website, budget separately for the domain, hosting, paid licences and labour, and establish which item covers certificate renewal, backups and uptime monitoring. Our managed hosting starts from €45 a month, while website maintenance work costs €50 an hour excluding VAT.
Imagine opening next year's invoice: you recognise the domain name and remember hosting from the previous payment, but alongside them are a plugin licence and maintenance hours whose purpose the invoice alone does not explain. It is understandable to wonder which items you could remove. We suggest starting with a different check: beside each amount, write down what the provider does for it, who receives notifications and who acts when something goes wrong, so that a cheaper quote really means lower spending rather than work your team will have to do itself.
How much does website maintenance cost per year?
Our clients spend €1,500–9,000 a year on labour, but the overall annual cost consists of two different things: services that generate an invoice, and work that generates an invoice only if someone does it. That is why domain and hosting bills usually make up a smaller part of the budget. For a practical calculation, we recommend using the breakdown below: first fill in the rows for which you already have an invoice, then establish who is responsible for the rest. The table's references to invoice issuers are matters to check in your agreements, rather than a claim that every provider works in the same way. Take particular care to avoid double counting: if uptime monitoring is already included in hosting, do not add the same work to the annual budget again.
| Item | What you pay for | Who to check the invoice with | Basis for annual costs | What to check before cancelling |
|---|---|---|---|---|
| Domain | Renewal of the right to use the name | Registrar or registry | The invoice for the specific domain | When the right of use expires |
| Hosting | Hosting the website and the agreed management | Hosting provider | Our managed hosting starts from €540 a year | Where the website will be hosted afterwards |
| TLS certificate | A certificate for an HTTPS connection | Issuer; person carrying out the work | Let's Encrypt certificate €0; included in our hosting, check elsewhere | Who will ensure renewal |
| Backups | Backups and agreed backup restore tests | Hosting or website maintenance provider | Daily backups and backup restore tests included in our hosting | How you will restore the website |
| Uptime monitoring | Monitoring agreed operational indicators | Hosting or website maintenance provider | Included in our hosting | Who will notice a problem |
| Paid licences | A subscription for a specific product | Plugin or theme vendor | €100–1,000 a year for our clients | What the licence expiry terms stipulate |
| Update work | Changes, checks and necessary fixes | Website maintenance provider | Hours worked × €50 excluding VAT | Who will take over these tasks |
The certificate issuance item can be €0, because Let's Encrypt issues trusted HTTPS certificates free of charge, but that amount says nothing about the work needed to ensure their renewal. Meanwhile, paid plugin and theme licences for our clients' websites cost €100–1,000 a year, depending on the features required. We suggest using this range from our experience as a reason to review actual subscriptions rather than automatically entering the lowest amount in your budget, because you will pay for a specific licence under its vendor's terms, and even a licence that seems inexpensive when purchased is a separate commitment with its own expiry date.
In your annual calculation, distinguish recurring payments from work whose scope still needs to be defined: multiplying our hosting starting price by twelve months gives a total starting from €540 a year, but an hourly rate alone cannot give an annual total without the expected workload. If a quote shows only an overall website maintenance fee, ask whether it includes WordPress updates, licence payments and backup restore tests, and how you will approve additional work, because otherwise two similarly named quotes still lack the clarity needed for comparison.
Domains: a small bill and important rights of use
Do not confuse a domain's retail price with the registry fee: Verisign's annual wholesale fee for .com is US$10.97 from 1 November 2026, while ICANN's approved registrar transaction fee for the 2027 financial year is US$0.20 per transaction year. Check the price on your invoice with your chosen registrar, because these figures describe individual fees rather than an offer to the end customer, so your budget needs the actual renewal amount and payee, while the first domain management check is who holds the registered rights.
ICANN calls the person holding the rights to a name the registrant. Our clients register domains themselves in their own names, and we do not hold them in our company's name. For a business website, we recommend naming the business itself as the registrant and choosing the technical service provider separately, so that changing developers does not first require you to resolve who has the authority to make decisions about the domain.
Country-code domains: price and late payment
Use the renewal amount on the invoice for your specific domain in the budget. For a generic domain, fees, the registration term and renewal conditions come from your agreement with the registrar. The registrar must disclose its renewal, post-expiry and redemption fees; a registry's wholesale charge is not that invoice. ICANN describes registration terms as typically one to ten years, and you must renew before expiry to keep the name. For a country-code domain, the operator's own prices and terms apply; this page does not restate them. The registrant holds the rights to the domain: the business itself should be the registrant, and a developer should act only as someone it authorises. A transfer or other change follows instructions from the holder or the holder's authorised agent. For a missed generic-domain payment, see the expiry sequence below, and also check who receives reminders.
Generic domains and transfers
For a generic domain, you should not rely on a fixed amount of extra time after expiry: ICANN's ERRP policy allows deletion after expiry while requiring renewal to be permitted during the specified period of DNS interruption. The Redemption Grace Period described by ICANN lasts 30 days after deletion, followed by five days in pendingDelete status if the domain is not restored, but do not confuse this sequence with a guaranteed opportunity for free renewal: prepare the budget and payment instruction before the original expiry date.
An Auth-Code is required to transfer to another registrar; where self-service is unavailable, the registrar must issue the code within five calendar days of the request. ICANN's transfer policy provides for a 60-day transfer restriction after a change of registrant; you can opt out before requesting the change if the registrar offers that option, so plan the change of registrant and transfer together, checking the particular registrar's procedure before making changes.
A domain dispute is not an ordinary renewal. The UDRP procedure explained by WIPO requires a trademark rights holder to prove that the domain is identical or confusingly similar to their trademark, that the registrant has no rights or legitimate interests, and that the domain was registered and is being used in bad faith; the fee for one domain with a single panellist is US$1,500, but this is not an automatic solution to disagreements with a developer, so the safest starting point is correct registration and access controlled by the business.
The UDRP adopted by ICANN is the dispute policy used by every ICANN-accredited registrar for the generic domains it sponsors. For a country-code domain, it applies only if the registration agreement incorporates it; operators may use the UDRP, a variation or a different policy. Read the policy named in your domain's agreement. Where the UDRP applies, the complainant must prove all three elements: the domain is identical or confusingly similar to a trademark or service mark in which the complainant has rights; the registrant has no rights or legitimate interests in the domain; and the domain was registered and is being used in bad faith. Both registration and use in bad faith are required. WIPO administers cases under this policy and accepts complaints based on registered trademarks or adequately supported claims to unregistered trademark rights. A business name appearing in a domain does not, by itself, give the business a right to recover it. This is a trademark holder's complaint against the registrant, not the registrar, and the procedure does not replace a court.
What do you get for the monthly hosting fee?
Our managed hosting starts from €45 a month and includes operating system updates, daily backups retained for 30 days with regular backup restore tests, SSL certificates, round-the-clock uptime monitoring and one person responsible. With our managed hosting, you therefore also pay for specific server maintenance tasks, so we recommend starting your price assessment with the division of responsibilities: who updates the environment, who looks after backups and who receives uptime monitoring notifications. The service name alone is not enough. If one quote includes these tasks while another leaves them to your employee, the comparison also needs to account for that workload; otherwise, the cheaper invoice tells you nothing about the total website maintenance costs or which task still has nobody assigned to it.
This list describes specific service contents against which you can check a quote, while you should budget separately for fixing WordPress plugins and checking website functions unless these are included in your agreements, because the server tasks listed do not themselves define the scope of such work. We regularly test data restores in our hosting; agree a separate website check to establish whether your forms or orders also work after a restore.
If your question concerns the hosting setup itself, you will find the reasoning behind the options in our article on shared hosting, VPS (virtual private server) and cloud servers, while our article on choosing hosting helps you check a quote's terms.
We would not recommend changing hosting simply to receive every website maintenance item on one invoice if your current environment suits you and responsibilities are clearly assigned, so first identify the problem you are paying to solve. If you lack someone to look after the server, assess a management service; if checks of WordPress functions after changes are missing, agree website maintenance work, because in both cases the budget is justified by the task and the person carrying it out; also ask for the quote to specify who approves additional work and how you will be informed of its expected cost.
WordPress updates: what are the hours spent on?
When budgeting for website maintenance work, we recommend allowing time both to install updates and to check that the website still performs the actions you have agreed with the maintenance provider, and it is the description of those checks that makes the hours understandable: for a website with an enquiry form, ask for a submission test, while for an online store, also agree an order test. If the quote mentions only installing updates, add these tasks so that both parties share an understanding of completed work and you can compare delivery against the agreement in the following month's report.
The WordPress version history shows three major releases in 2024 and two in 2025, but this count alone does not tell you how many hours your website needs for maintenance. Meanwhile, minor WordPress core updates have been installed automatically by default since version 3.7, a useful mechanism that should not be ignored when calculating labour, but before reaching an agreement, check the particular website's settings and specify which actions someone will test after an update. We recommend paying for clearly described checks and necessary fixes rather than allocating the same number of hours to every release regardless of what changes on the website.
The staging site described by WordPress is a copy where updates, plugins and themes can be tested before changes reach the live website; we recommend using it for checks whose outcome you want to see before publication. Create the copy for a specific task. Agree which forms or ordering steps you will test, how you will record the result and what you will do if a test fails, and define the rollback procedure in advance so that the person doing the work has an agreed action plan; this description also helps distinguish a technical installation from a tested change without requiring you to read the plugin's code yourself.
The PHP runtime is a separate planning task: PHP's support model provides two years of active support followed by another two years of fixes for critical security issues only, and on 4 November 2026 the supported release branches are 8.2, 8.3, 8.4 and 8.5. This list alone cannot establish the migration workload for your website, so ask for the annual plan to identify the runtime assessment and any necessary migration separately; we have covered an old PHP or Node.js version in a separate article; the main point for the website maintenance calculation is to allow for the work rather than automatically assuming the hosting payment covers it.
In our experience, updating and maintaining a small business WordPress website takes 3–15 hours a month, depending on its complexity and custom plugins. At our rate of €50 an hour excluding VAT, this work makes up the annual amount mentioned at the start of the article, and its scope depends on whether you need only critical updates or new features as well. This is a planning estimate rather than a fixed fee for every website: the quote must specify the expected tasks, while our hourly model gives you a monthly hours report without a long-term commitment; we recommend distinguishing maintenance from new features in that report so that, when reviewing annual spending later, you do not confuse looking after the existing website with developing it further. If you are comparing this with a fixed monthly plan costing considerably less, ask it to specify which actions someone tests after updates and whether fixes are included: our hours include precisely these checks and necessary fixes.
Paid licences: what remains after a subscription expires?
Licence expiry must be assessed against the specific product's terms, because the right to continue using an installed plugin and access to its future updates can be different things. For example, a Gravity Forms Basic licence for one website with standard support has a listed price of US$59 a year, while the licence expiry terms allow the installed product to keep working but end access to updates, including security fixes, and technical support. A working form alone should therefore not justify removing the licence from your budget: first decide how you will maintain that function in future, then make the subscription decision.
| Product and plan | Price | Websites | Continues after subscription expiry | Ends after subscription expiry |
|---|---|---|---|---|
| Gravity Forms Basic | US$59 a year | 1 | The installed plugin | Updates, including security fixes, and support |
| ACF PRO Personal | US$49 a year | 1 | Editing existing PRO fields | Creating new PRO fields and updates |
| WPML Multilingual Blog | €39 with updates for one year | 1 | Use on registered websites | Updates and support |
The ACF PRO Personal price list specifies US$49 a year for one website, and the vendor's explanation of subscription licence renewal links the annual payment to continued access to updates and PRO features. There is also a specific limit: after an activated subscription expires, existing PRO field definitions can be edited, but new PRO fields cannot be created. If your website development plan includes changes involving this plugin, show them to your maintenance provider when discussing the budget so that the subscription licence renewal decision rests on the function you need, because one subscription's terms cannot reliably tell you what happens when every other website subscription expires.
The WPML Multilingual Blog offer costs €39 and includes one production website, plus support and updates for one year; this is the price of that particular offer rather than a promise about the future renewal cost of any licence. WPML's subscription terms allow continued use on already registered websites after expiry but end updates and support, so before entering the price in your calculation, also check whether the chosen plan suits your website: the cheapest named licence is not proof that it will cover every feature you want, and these examples are not a recommendation to buy all the products named.
For a practical licence inventory, we recommend recording each paid product's name, plan, account holder, next payment date and intended website, then comparing this inventory with the website maintenance quote. In particular, establish whether you pay for the subscription yourself or whether it is included in the developer's invoice, and what will happen to the access you need if the relationship ends, because this depends on your agreement. We do not recommend saving money by simply stopping payments and leaving plugins without a plan; if a function is no longer needed, first agree its removal or replacement as a specific task with a clear outcome.
Certificates, backups and uptime monitoring
A free certificate removes the cost of purchasing the certificate, but we recommend that the website maintenance agreement separately identify who is responsible for its renewal and verification. The default Let's Encrypt certificate lifetime on 4 November 2026 is 90 days, while the announced change from 10 February 2027 provides for a 64-day lifetime for certificates issued or renewed from that date. The annual budgeting question is therefore how renewal will be ensured throughout the period, and we recommend that the contract also describe how you will learn of a failed renewal and who will act in that situation.
The subsequent Let's Encrypt schedule provides for 45-day certificates under the default classic profile from 16 February 2028, and the issuer advises against relying on manual renewal. Meanwhile, CA/Browser Forum requirements limit the maximum validity of newly issued publicly trusted TLS certificates to 200 days from 15 March 2026, 100 days from 15 March 2027 and 47 days from 15 March 2029, and these are different schedules: the first describes a particular issuer, while the second sets the maximum permitted lifetime, so check the actual terms for your certificate.
We recommend automatic certificate renewal with a person checking whether it succeeded, while also agreeing who receives alerts when the main person responsible is unavailable. Automation describes how the task is performed under this agreement rather than replacing the responsible person. SSL certificates are included in our managed hosting; elsewhere, clarify your budget by asking whether configuring automatic certificate renewal and checking it afterwards are already included in hosting or will be agreed separately; the statement “certificate included” would not be enough for us to recommend removing all related work from your budget; request a description for your own website rather than assuming that this task is handled elsewhere.
For backups, we would recommend agreeing a practical backup restore test whose result the person responsible can demonstrate, because a backup service entered in the budget does not yet describe such a test, while the UK's NCSC recommends separately stored offline backups or a cloud service designed for this purpose, together with the ability to restore files and regular restore trials. Applying this advice to your website, ask for the backup storage location, access procedure and latest test result, and leave room in the website maintenance labour calculation for the trial itself rather than merely confirming that a backup mechanism exists.
At the start of a monitoring agreement, we recommend specifying exactly what you want to check: whether the website is reachable, whether certificate renewal succeeded and whether a selected important action produces the expected result, and these checks need separate descriptions so that neither party has to guess what a general promise that “everything is monitored” means. Then agree who receives the notification, when it must be assessed and how any necessary fix is paid for, because the service's value in your budget also depends on whether a specific response is planned after a notification. Do not treat round-the-clock uptime monitoring alone as a promise to fix every problem within a specified time.
What does deferred website maintenance cost?
The cost of deferred website maintenance usually appears as recovery work: our listed rate for hacked website recovery is €90 an hour, compared with €50 an hour for planned website maintenance work (both rates excluding VAT). However, the total cost of deferred maintenance for a particular website cannot be established from its hosting price alone, and we would not recommend basing a budget on the assumption that every incident will necessarily cost more than every website maintenance plan. A specific assessment of the work is needed. First identify what the proposed service does about updates, backups and alerts, then consider how your business would respond if the website became unusable, because this lets you compare the quote's contents with your need for business continuity; you are assessing verifiable tasks rather than buying a security promise whose contents you cannot explain.
In Patchstack's report on newly discovered vulnerabilities in the WordPress ecosystem in 2025, 91% relate to plugins and 9% to themes, while six of the total 11,334 vulnerabilities were recorded in the WordPress core, and the report's percentages are rounded, so they should not be read as a claim that there were no WordPress core issues at all. These data describe newly discovered vulnerabilities rather than the proportion of websites hacked or the probability of your website being hacked; we conclude that website maintenance discussions must also cover plugins and themes, because focusing only on WordPress core updates would leave most of the issues described in this report undiscussed.
There is also a specific tool for spotting alerts: Google Search Console notifies verified website owners if Google suspects hacking and lets them view the security issues report, while Chrome can display a red warning about a dangerous website in cases involving phishing, malicious or unwanted software and social engineering, and Google advises against visiting such a website. We therefore recommend assigning someone to receive Search Console notifications and defining a response procedure, because responsibility for reviewing an alert is a practical website maintenance task you can request in a quote without accepting a promise that the tool will detect absolutely every problem.
If a problem has already occurred, we recommend separating the immediate recovery required from the subsequent website maintenance plan and first describing what needs investigating, what needs restoring and how the result will be checked, so that recovery work does not become an unclear monthly payment. Our article on a hacked WordPress website sets out specific actions. We recommend handing over the restored website with an agreement on future updates and the person responsible, while keeping emergency work separate from routine maintenance in the annual spending review, so that next year's decision rests on a clear breakdown rather than a single overall invoice that merges recovery and everyday tasks.
How should you budget for website maintenance?
Start with an annual cost breakdown and a clearly stated workload assumption, then compare it with the particular website's tasks and checks. The following table is a sample calculation rather than three ready-made website maintenance offers: for illustration, it uses three labour hours a month for a business website with forms and two languages, and fifteen for an online store, without claiming that every such website needs exactly that amount. Annual hours for a simple brochure website need to be determined separately, while both monthly figures come from our observed workload range, but assigning them to particular website types is only a budgeting example.
| Website type | Labour assumption | Annual labour at €50 an hour excluding VAT | Annual hosting | Annual licences | Annual domain |
|---|---|---|---|---|---|
| Brochure website | Agreed annual hours | Annual hours × €50 | Shared plan price or our hosting from €540 | Total actual subscriptions | Actual renewal fee |
| Business website with forms and two languages | 3 hours a month in this example | €1,800 in this example | Starting from €540 | Total actual subscriptions | Actual renewal fee |
| Online store | 15 hours a month in this example | €9,000 in this example | Starting from €540 | Total actual subscriptions | Actual renewal fee |
The hosting column uses the starting price of our managed hosting and server service, which does not confirm that the entry-level plan will suit every online store; the final calculation must use the price of the service chosen for your website and separately agreed checks. The labour amounts are also conditional. If the expected hours change or your team does some of the work itself, recalculate the labour column, but take domain and licence amounts from actual quotes rather than replacing them with an average of the examples in this article, and do not add backups and uptime monitoring already included in our hosting again as the same service.
For a simple brochure website, we would also suggest considering an inexpensive shared hosting plan with a few agreed labour hours a year, if an assessment of that particular website confirms that this is sufficient and someone takes responsibility for the remaining duties. This is usually a fair solution when the website has no enquiry forms, orders or custom plugins, its content changes infrequently, and someone on your team receives alerts and checks the website after updates. For comparison, request the actual hosting quote and a description of the work, then compare it with the managed service's contents while keeping your own employees' time in the budget too. Until this has been checked, treat “a few hours a year” as an assumption to discuss rather than a promise on which to base a full year's spending.
To prepare a calculation for your website, send us its address, the available hosting quote and the names of the paid plugins you use, and describe the actions you definitely want tested after changes. Specify separately which duties your team handles itself and whether you plan new features next year, so that the scope under discussion can distinguish routine website maintenance from development; if a licence or domain is held in someone else's account, mention that in your description too, so that the responsible person and necessary access arrangements can be established before further work is agreed.
Frequently asked questions.
How much does website maintenance cost per month?
For our clients, website maintenance work usually takes 3–15 hours a month, which at €50 an hour excluding VAT comes to €150–750, and our managed hosting starts from €45 a month. The monthly total depends on the agreed scope of work, chosen hosting and paid licences; domain and annual subscription expenses can be spread across months in the budget to show all the items together. Before agreeing, ask for included work to be distinguished from additional tasks and establish who checks the website's operation after updates.
Is hosting alone enough for website maintenance?
Paying for hosting alone is not enough if website updates and checks are neither included nor assigned to someone else. Our managed hosting includes operating system updates, daily backups and uptime monitoring, but the scope of work on WordPress plugins must be agreed separately. If your team handles these duties itself, there is no need to buy an external website maintenance service simply for its name; we recommend clearly recording who does the work, which actions are tested and what happens if a problem occurs.
What happens if you do not renew your domain name?
No single non-renewal timetable applies to every domain. Under ICANN's consensus policy for generic domains, the registrar must send expiry warnings about one month and about one week before expiry. If the name has been neither renewed nor deleted, it must send at least one further notice with renewal instructions within five days after expiry. The registrar may delete the name at any time after expiry, but must allow the former holder to renew from expiry through the DNS-interruption period. This is a required opportunity to renew, not a fixed number of free days. After deletion, generic registries other than sponsored ones must offer a 30-day redemption period, during which the registrar that deleted the name can restore it at the former holder's request; an extra fee may apply. If that period was offered and the name was not restored, ICANN's registrant FAQ describes five further days in PendingDelete status before someone else can register it. Country-code domains follow their operator's own deletion and recovery rules, which this page does not restate. If payment is late, contact your registrar immediately and establish the domain's current status. Keep your contact details current so notices can arrive; the registrar must use a method, such as email, that does not require you to log in to its system to collect them. ICANN recommends a second mailbox outside the expiring domain so reminders can still reach you.
In whose name should a business domain be registered?
We recommend registering a business domain in the business's own name and assigning technical management duties to your chosen provider. Our clients register domains themselves, and we do not hold them in our company's name. Check the registered registrant's details and the business's account access rather than relying solely on who pays the invoice, and agree who receives reminders. If the domain is already registered in someone else's name, establish the relevant registrar's change of registrant procedure before making changes.
Can WordPress plugins be updated automatically?
Yes, an administrator can enable automatic updates for each plugin and theme individually. WordPress has offered this option since version 5.5, but the setting itself does not specify who will test the actions important to you after changes. We recommend combining this choice with backups, a restore procedure and someone responsible for checks; for more complex changes, first allow for a trial on a staging site, meaning a separate copy of the website. For paid plugins, also check the licence terms and access to updates.
Servers, hosting and maintenance in the EU — Frankfurt, Helsinki or Riga, with 24/7 monitoring. Full management: updates, security and performance, automated backups with tested restores, SSL certificates, CDN and DDoS protection. We migrate you from your current host with no downtime and scale with the load.