Website Maintenance — What It Covers and What It Costs [2026]

Website maintenance is an ongoing technical service covering updates, backups, monitoring, security and small tasks — regardless of whether the site runs on WordPress, PrestaShop or custom code. Package prices start at 99–190 PLN net per month for the basic scope and reach 1,500 PLN for stores with on-call support. This guide shows exactly what maintenance covers, how it differs by platform and how to choose a vendor who genuinely looks after the site.

Key takeaway: Website maintenance covers: updates (CMS, plugins/modules, environment), backups with restore tests, availability and security monitoring, incident response within an SLA and small tasks. Packages: 99–190 PLN/month (basic), 300–500 PLN/month (standard), 500–1,500 PLN/month (store with on-call). Maintenance pays off when the site generates leads or sales — downtime costs more than a yearly package. The boundaries of scope (what is maintenance and what is a separate project) must be written into the contract.

What is website maintenance?

Website maintenance is an ongoing collaboration model in which the vendor is responsible for the site's technical condition: they watch updates, backups, security and performance, respond to incidents and perform small tasks. It is not "hosting with tech support" or a series of one-off jobs — it is a subscription to peace of mind: the site is someone's responsibility, not someone's "later" problem.

Maintenance differs from a one-off repair in that it works preventively. A repair is a reaction to an outage that has already happened; maintenance is a set of processes meant to prevent it — and when it happens anyway, to shorten the downtime to a minimum. The difference shows in the bill: a failed update without a backup means rebuilding the site from scratch; the same update within maintenance means a rollback in fifteen minutes.

What does website maintenance cover?

The scope differs in details between platforms, but the foundation is common to every site.

• Updates — the system core (WordPress, PrestaShop), plugins or modules, theme or template, PHP version and database. In a professional variant, through a staging environment (WordPress staging).
• Backups — automatic copies of files and database, stored off-server, with periodic restore tests. A backup without a test is hope, not protection (WordPress backups).
• Monitoring — 24/7 availability, response time, errors, SSL and domain, form behaviour; for stores: payments and orders (website monitoring).
• Security — malware scans, login attempt control, hardening, 2FA, WAF, incident response (WordPress malware removal).
• Performance — caching, images, Core Web Vitals, database housekeeping, a review of plugins that weigh the site down.
• Technical support — a ticket channel, response time and resolution time per the SLA (WordPress technical support).
• Small tasks — content changes, sections, banners, minor appearance fixes within the hourly budget.
• Reporting — a monthly summary: what was done, what was found, recommendations for the next period.
• Periodic audit — a review of the site's condition once a quarter: security, performance, technical SEO (WordPress site audit).

Outside the scope of maintenance are large jobs: rebuilds, migrations, new features, marketing campaigns. That is not a gap in the offer — it is a healthy separation that protects the subscription from scope creep and allows large tasks to be quoted honestly.

Maintenance by platform — WordPress, PrestaShop, custom code

The technical core of maintenance is similar, but the details depend on what the site runs on.

With WordPress the biggest risk is plugins — updated frequently and sometimes conflictually. With PrestaShop — modules and compatibility with new PHP versions. With a custom site, maintenance means primarily dependency and environment updates — without them, after two or three years the project becomes a legacy system.

Packages and prices for website maintenance

The market prices maintenance in three or four tiers. The ranges below reflect the Polish market in 2026.

Five factors affect the price: the number of pages in the site, traffic, the number of plugins/modules, the presence of a store and integrations, and the required response time. A WooCommerce site requires purchase-path tests after every update, and a store with payments and couriers additionally needs transaction monitoring. When comparing offers, look at scope and SLA, not price: a package at 149 PLN with a "within 5 days" response and no backups is not a cheaper version of a 350 PLN package — it is a different service. Full cost breakdown: WordPress website maintenance costs.

SLA — what the contract should guarantee

An SLA (Service Level Agreement) is a written set of vendor commitments. Without it, "maintenance" is a contract for good intentions.

• Response time and resolution time — separately for priorities: critical (site down), high (forms/payments), normal (day-to-day work). A model for a revenue-generating site: 4 h / 8 h / 24–48 h.
• Ticket channel — one, unambiguous, with acknowledgement of receipt.
• On-call — whether failures on weekends and holidays are handled, and within what time.
• Backups — frequency, retention, storage location, restore tests.
• Access and ownership — code and access belong to the client; what happens when the collaboration ends.
• Reporting — what the monthly report contains and when it is delivered.

Model contract clauses — including exclusions and the termination procedure — are collected in the article on WordPress website care; the mechanics are identical for other platforms.

When maintenance pays off, and when it does not

Not every site needs maintenance. The calculation is simple: compare the annual cost of the package with the cost of one serious incident.

Maintenance pays off when:

• the site generates leads or sales — hours of downtime cost more than a monthly subscription,
• you run a store — updating payments without tests can stop sales,
• the site has integrations (CRM, ERP, couriers, marketplaces) — an outage spills over into the whole process,
• there is no technical person in the company and the site matters to the business,
• the site is several years old and was developed "piece by piece" — technical debt grows on its own.

Maintenance can wait when:

• it is a simple brochure site without revenue traffic — a periodic review and backups are enough,
• the site is new and maintained by its author under warranty,
• the budget is zero — then a conscious quarterly review is better than none (though it is a model "on the edge of risk").

An intermediate option is WordPress administration: cheaper, focused on performing activities, without proactive responsibility for the outcome.

How to choose a website maintenance vendor

The criteria that genuinely differentiate offers — in order of importance.

• Scope and exclusions in writing — a list of activities in the package and a list of work outside it; without this, disputes about "that was supposed to be in maintenance" are inevitable.
• SLA with numbers — response times per priority, ticket channel, on-call; generalities like "fast response" mean nothing.
• Backups with tests — ask directly whether the vendor tests restore and how often; an answer of "backups work" without a test is a red flag.
• Update process — through staging or on production? A backup before the change? Rollback possible?
• Reporting — a sample monthly report from another client; no reports means no accountability.
• Access and ownership — code, domain and accounts belong to you; the vendor works on your accounts, not the other way round.
• References and track record — sites under care for more than a year, client reviews, response to questions before signing.

The last test is the simplest: send a ticket before signing and assess the speed and concreteness of the response. If it is slow and vague before the sale, it will not be better after.

Store maintenance vs company site maintenance

A store is a separate maintenance category — not because it is "harder", but because it has different critical points.

• Purchase path tests — after every update: cart, checkout, payment, confirmation email. A payment plugin updated without tests is a bet with someone's money.
• Transaction monitoring — test orders, payment webhooks, stock synchronisation.
• More frequent database backups — orders and customer data change daily; a weekly backup means losing up to seven days of sales.
• SLA with on-call — a store does not sell only during office hours; an outage on Sunday evening means lost orders.

A standard "company site" package will not cover a store's needs — compare scope and choose a package with WooCommerce. If you run a PrestaShop store, the mechanics are analogous.

Frequently asked questions

How much does website maintenance cost?

Maintenance costs from 99–190 PLN net per month for the basic package (updates, backups, monitoring), through 300–500 PLN/month for standard with small tasks and faster response, to 500–1,500 PLN/month for stores and services with on-call. The price depends on the platform, number of plugins, traffic and the required SLA.

What does maintenance cover beyond updates?

Backups with restore tests, availability and security monitoring, incident response per the SLA, malware scans and hardening, performance reviews, small content tasks and monthly reporting. Extended packages add optimisation, a development budget and store support (payment tests, order monitoring).

Does website maintenance include content creation?

No — maintenance covers technical upkeep, not content production. Content changes (small tasks) usually fit within the package's hourly budget, but writing articles, creating graphics or running campaigns are separate services. It is worth writing that boundary into the contract.

What is the difference between website maintenance and website care?

The terms are close and often used interchangeably. "Maintenance" emphasises the technical and cost side (hosting, domain, updates), "care" emphasises the collaboration model with a package, SLA and reporting. If you are comparing costs, see WordPress website care.

Does maintenance include hosting and the domain?

Hosting and the domain remain the client's property — maintenance covers supervision of the environment, configuration, SSL, monitoring renewals and correct DNS. Some companies offer maintenance bundled with hosting (like managed hosting); that is convenient, but check whether it locks you into a long contract and whether access remains yours.

How fast should a maintenance vendor respond?

A model for a revenue-generating site: critical outage (site down) — response within 4 h, form and payment problems — within 8 h, normal work — within 24–48 h. For brochure sites, longer times (24–48 h) are acceptable, provided they are written into the contract. "Fast response" without numbers is not an SLA.

Sources and tools

• WordPress.org — support
• Google Search Central — site maintenance
• web.dev — Core Web Vitals
• OWASP — web application security
• PHP — supported versions

👉 Looking for website maintenance? See technical care with SLA and WordPress development & care — packages with monitoring, backups and response times. Write via the contact form or to kontakt@informatix.com.pl.

📖 See also: WordPress website care, WordPress technical support and website monitoring.