Nobody should charge you for clicking Update - you pay for what happens before and after that click. When someone searches for “WordPress update cost”, they are usually in one of two situations: either the dashboard has been showing red numbers for months and they are afraid to touch it, or they already clicked and the site stopped working. In both cases the question is the same - how much does it cost to have someone who knows what they are doing handle it, and is it worth paying for at all.
There is no shortage of “how to update WordPress” guides. Almost none of them say what it costs when a professional does it, where that price comes from, and when postponing an update stops being a saving and starts being a risk. That is what this post is about. The figures come from my own price list, not from thin air, and the procedure is the one I use for clients under ongoing care.
What a WordPress update costs - one-off and on a subscription
Let me start with what people want to know first. There are two models, and they differ less in the amount than in what you get for it.
A one-off clean-up is a job along the lines of “the site has not been updated in a year, do it safely”. There is no single price, because there is no single site: a brochure site with five plugins is a completely different job from a store with a payment gateway, a courier integration, invoicing and a theme somebody once edited by hand. So I price that kind of job after looking at the site, for a closed scope, in writing within 24 hours - not “from X”. The quote always contains the same things: a backup, updates done one at a time, a check of the key paths and, for a store, a test order. If someone gives you a price for an update without asking a single question about the site, they are pricing a click, not the work.
A subscription, meaning ongoing care, is the model where updates are one part of a monthly package. I run three plans: Basic from PLN 1,000 net a month, Pro from PLN 2,000 and Premium from PLN 3,500 net. Basic covers updates of WordPress, plugins and the theme, backups, uptime monitoring and a small pool of time for minor fixes. The higher plans add more development hours and a shorter response time. The full comparison is on the ongoing support page - that is also where you will find what I am not repeating here, namely exactly what each plan includes.
Which model makes sense? A simple rule: if the site is a brochure where nothing ever happens, a one-off clean-up every so often is enough. If the site or store genuinely works for the business and every hour of downtime has a price, a subscription comes out cheaper than one serious outage caused by an outdated plugin - I wrote about how that calculation adds up in the post on website maintenance cost.
What helps: before you ask for a quote, check three things in the dashboard: how many updates are waiting, when the last one was done and whether you have any backup at all. Those three answers decide the price more than anything else, and the contractor will ask about them anyway.
What you are actually paying for
People are often surprised that “a few clicks” costs as much as a few hours of work. Because they are not clicks. Here is what sits inside that price, so you can see where the money goes.
- A backup beforehand. Full, fresh, files and database, and verified to restore. Without it every update is a gamble. How to make a backup that actually restores is covered in my post on WordPress backups.
- A review of what is about to be updated. Which plugins declare compatibility with the new version, which have not been maintained for years, whether the theme carries custom edits an update will overwrite. That review takes time, but it is what separates “I’ll update and we’ll see” from “I know what is going to change”.
- Updates one at a time. Core first, then WooCommerce, then the plugins critical for sales, then the rest, the theme last. A check of the site after every step. Slower than “select all”, but when something breaks you know immediately what did it.
- A test afterwards. Home page, contact form and, in a store, the full purchase path through to the order confirmation and the email. A post-update failure almost never sits on the home page - it sits on the last step of checkout.
- A fix, if something broke. This is the part a “per click” price does not include, and which comes back later as a separate, more expensive invoice.
On a subscription the same steps happen quietly every month, plus a report: what was updated, from which version to which, whether anything broke and how it was fixed. I described that in the post on what WordPress maintenance includes.
What breaks during an update and how I prevent it
I will not repeat the full procedure here - it lives in a separate safe WooCommerce updates checklist. This section is about something else: what I actually see at clients after a careless update, and what that means for the price.
The most common failure is a plugin that did not keep up. The author abandoned the project or is running late, the new WooCommerce changes something underneath, and checkout stops accepting payments. The home page looks normal, the products are there, the cart works - and the customer sees an error on the final step. The owner finds out two days later from the drop in orders.
Second in line is a theme with custom edits. Someone once tweaked the product page layout or added a button directly in the theme files, without a child theme. A theme update overwrites those changes and suddenly the site looks different, or an element needed for selling is missing.
Third is a white screen or a critical error right after the update, when two plugins, or a plugin and the PHP version on the server, stop getting along. It sounds scary, but it is usually reversible within an hour - provided there is a backup and you know what was updated last. The plan of action is in my post on the WordPress critical error.
I prevent all this in a boring way, and it is precisely that boredom you are paying for: backup, compatibility review, staging where the site deserves it, one element at a time, a checkout test. None of these steps is complicated. Together they are the difference between an update after which nothing happens and one after which the phone rings.
What helps: if you update yourself, do one thing at a time and open the site after each. When something breaks, you have one suspect, not twelve. It is the cheapest insurance there is, and it costs nothing but a quarter of an hour.
When an update cannot wait
Not every update is urgent, and it is only fair to say so. A new editor feature or a cosmetic fix in the theme can happily wait for the next scheduled review. There are, however, three situations where postponing stops being a saving.
A security patch in a plugin you use. When a plugin author releases an update described as a security fix, the information about that vulnerability is already public. From that moment on, bots scan the internet for sites running the outdated version - not because anyone is targeting your company, but because you are on the list. That kind of update should go in within days, not within the next quarter. This applies especially to plugins handling forms, logins and file uploads.
End of support for the PHP version on your server. WordPress runs on PHP, and every PHP version has a date after which it no longer receives security fixes. Hosting providers usually warn before switching an old version off, and that is when you need to check whether the theme and plugins work on the new one. This is an update best planned in advance, because if the host switches the version on its own and one old plugin does not support it, the site goes down at a random moment.
A plugin that handles money. The payment gateway, the courier integration, invoicing. When their provider changes the API and announces that the old plugin version will stop working from a specific date, that is not a suggestion. After that date, customers will not be able to pay.
Everything else - minor fixes, new features, translation updates - can go in at a calm, regular rhythm. And that is the strongest argument for rhythm over bursts: a site updated every two weeks in small steps almost never has an urgent case, because the gap between versions is small. A site updated once a year jumps a dozen versions at a time, and every such jump is a lottery.
How this works with me in practice
When someone comes to me with a neglected site, I start with a free review: I check how many updates are waiting, which plugins are abandoned, whether the theme has custom edits and whether a restorable backup exists. Based on that you get a written quote for a closed scope. If the site is to stay under ongoing care after the clean-up, the initial tidy-up usually becomes part of the start of the contract, and from then on updates happen regularly and without your involvement - with a backup before, a test after and a report once a month.
One thing worth saying plainly: ongoing care is not for everyone. If you have a brochure site with a contact form and five plugins, a one-off clean-up every six months plus your own clicks in between is enough, and I will not push a subscription. A subscription starts paying off when the site earns money or brings in customers, and downtime costs more than the monthly fee.
Summary
Updating WordPress and WooCommerce costs as much as the work around it: backup, review, updates one at a time, testing and a fix if needed. I price a one-off clean-up after seeing the site, per scope, in writing. On a subscription, updates are part of a package from PLN 1,000 net a month, together with backups and monitoring. Three things are urgent: security patches, end of PHP support and the plugins that money flows through - the rest can go in at a regular rhythm.
If you do not know what state your site is in, or whether clicking Update is safe for you, send me the link. I will do a free review and tell you plainly what to update first, what to handle carefully and what it will cost.
Frequently asked questions
How much does a one-off WordPress update cost? It depends on how many updates are waiting and how complex the site is - a brochure site is a different job from a store with payments and integrations. I quote after a free review, for a closed scope, in writing within 24 hours. The price always includes a backup before, updates one at a time and a test after.
Are updates included in ongoing care? Yes. The lowest plan, at PLN 1,000 net a month, covers updates of WordPress, plugins and the theme, backups, monitoring and a small pool of time for minor fixes. The higher plans add more hours and a shorter response time.
Can I update the site myself to avoid paying? You can, and for a simple site it makes sense. Two conditions: a fresh backup before every update, and updating one element at a time with a check of the site after each. What gets expensive is not the updating itself, but the repair after an update done without a backup.
What if the site is already down after an update? Do not reinstall anything and do not keep clicking. If there is a backup, restore it. If there is not, disabling the most recently updated plugin is usually enough - the step-by-step procedure is in my post on the critical error. If you would rather someone else did it, send me the link; I treat those repairs as a priority.
Would rather not watch over it every month yourself? I take sites and stores under ongoing care - backups, updates, monitoring, and priority when something breaks. Tell me what you run and I will send back scope and price.