WordPress maintenance in Switzerland typically costs CHF 49–150 per month for a small business website, CHF 150–300 for an active or multilingual site, and CHF 300–600+ for WooCommerce or business-critical installations. The useful comparison is not “how many updates are included?” It is who checks the site after an update, who can restore it, how quickly they respond, and whether that recovery work is covered. A cheap plan that only clicks Update may leave the expensive part—diagnosis and repair—with you.

This guide is for Swiss SMEs comparing an agency care plan, a freelancer, managed hosting or a do-it-yourself routine. The price examples were checked in July 2026 against publicly advertised Swiss offers. They are reference points, not quotes from Clear Design, and they are not perfectly like-for-like. That imperfection is the lesson: the same word, maintenance, is used for very different levels of responsibility.

WordPress maintenance prices in Switzerland at a glance

Public examples illustrate the range. Digistarter advertises website maintenance at CHF 49 per month, covering updates, backups and security. onlineKarma lists plans at CHF 82 and CHF 100 per month, with its highest tier starting at CHF 617; its notes distinguish routine maintenance from separately billed troubleshooting. O’Matic lists CHF 100, CHF 250 and CHF 500 monthly packages, with staging, support hours and retention increasing by tier. All three quote prices excluding VAT or specify annual billing conditions. These examples show market shape; they do not establish a universal “correct” price.

The price is a proxy for transferred responsibility

A WordPress site is a small software supply chain. WordPress core, the theme, plugins, PHP, the database, DNS, email delivery, consent tools and third-party services change independently. Maintenance reduces the chance that those moving parts drift into an unsafe or incompatible state. More importantly, it defines who notices and who acts.

Clicking an update button is inexpensive. Maintaining a safe restore point, checking a representative set of pages, diagnosing a conflict and returning a revenue-producing site to service require skilled time. This is why a credible care plan costs more than the hosting account itself. For the same reason, Swiss WordPress hosting and WordPress maintenance should be evaluated together but not confused: hosting keeps infrastructure available; maintenance keeps the application dependable.

Choose a realistic maintenance level

What a proper WordPress maintenance plan should include

1. Updates with a pre-update restore point

WordPress core, theme and plugin updates should be applied on a defined schedule, with critical security updates treated according to urgency. WordPress itself recommends backing up before updating because the upgrade process changes application files. The plan should say whether the provider tests only the homepage or also checks forms, navigation, key templates, language switching, search, checkout and account functions.

For a simple brochure site, a careful production update may be proportionate. For custom code, WooCommerce or integrations, staging is usually worth the extra cost. “All updates included” is incomplete language unless the contract also explains compatibility work when an update exposes an existing problem.

2. Backups that can actually leave the server

A backup stored only beside the live site shares too much of the same risk. Ask whether files and database are both covered, where copies are stored, how long they are retained and whether you can receive them if the contract ends. The Swiss NCSC recommends regular backups and checking that they function. A green “backup completed” email is evidence of a job, not proof of a successful restoration.

Frequency should follow how much data the business can afford to lose. A static company site may tolerate a daily backup. A shop taking orders throughout the day may need more frequent or transaction-aware protection. This is a business decision expressed as a technical schedule.

3. Uptime, security and functional monitoring

Uptime monitoring answers, “Does the server return a page?” It does not necessarily answer, “Can a prospect submit the form?” Better plans combine availability checks with security scanning and periodic functional tests. If leads depend on email, test delivery as well as form submission. A perfectly online website with a silent mailbox failure is still commercially down.

4. Recovery ownership and response terms

Every plan should name the response channel and distinguish acknowledgement from resolution. “Priority support” may mean the ticket is read first; it does not necessarily promise restoration within a fixed period. Ask what happens outside office hours, whether emergency work has a surcharge and who decides to roll back.

What maintenance usually does not include

This is where many budget surprises begin. Routine maintenance and website development are different services. A care plan may include a small allowance for text or image changes, but it rarely includes a redesign, new feature, substantial SEO work or rebuilding an obsolete plugin.

Read the exclusions beside the inclusions. If update-related troubleshooting is billed separately, model that possibility into the annual budget. The overall cost of a website in Switzerland is clearer when build, hosting, maintenance, licences and growth work occupy separate lines.

How site type changes the maintenance cost

Plugin quantity is a rough signal, not a pricing formula. Ten well-maintained plugins may be easier to support than one abandoned bespoke extension. Complexity comes from dependencies, data flows and the cost of failure. Many of the most expensive website mistakes Swiss businesses make begin with unclear ownership rather than dramatic technical errors.

DIY, freelancer, agency or managed host?

DIY maintenance

DIY can be rational for a low-risk site if someone has protected time, administrator access and the confidence to restore it. Price your time honestly. A recurring 90-minute monthly routine is 18 hours per year before any incident. The more dangerous cost is interruption: maintenance done “when things are quiet” tends to disappear when the business is busy.

Freelancer

A good freelancer can offer close knowledge of the site and excellent value. Ask about holiday cover, credential documentation and what happens if they are unavailable. Concentrated knowledge is efficient until it becomes a single point of failure.

Agency care plan

An agency normally costs more because it can provide shared documentation, a wider skill set and continuity across absences. The advantage is strongest when the plan includes diagnosis and recovery, not merely a branded dashboard report. Check whether the work is performed by the named Swiss team or handed to an unknown third party.

Managed WordPress host

Managed hosting can automate backups, core updates, caching and infrastructure security. That is valuable, but it may not cover the application layer: testing your form, repairing a theme conflict or checking a language switcher. Ask where the host’s responsibility ends and yours begins.

Twelve questions to ask before signing

1. Which updates are automatic, reviewed or tested on staging?
2. How quickly are critical security updates assessed?
3. Are both database and files backed up?
4. Is at least one backup stored away from the live hosting account?
5. How often has the restore process been tested?
6. Which pages, forms, languages and transactions are checked after updates?
7. What exactly triggers an alert, and who receives it?
8. What response time applies during and outside business hours?
9. Is troubleshooting after a routine update included or billed hourly?
10. Who owns the domain, hosting, licences, analytics and administrator credentials?
11. What data and backups will be handed over when the contract ends?
12. Which work is excluded, and what are the hourly and emergency rates?

A sensible maintenance rhythm for a Swiss SME

The rhythm should adapt to the site rather than follow ritual. A campaign launch, major WordPress release or new payment extension may justify an extra staging cycle. A stable brochure site does not need theatre; it needs consistent evidence that the basics work.

Frequently asked questions

Is WordPress maintenance mandatory in Switzerland?

There is no general rule requiring a business to buy a WordPress care plan. The business is still responsible for appropriate security, continuity and handling of personal data. Maintenance is one practical way to organise those responsibilities and document who does what.

Can automatic updates replace a maintenance plan?

They can reduce routine work, particularly for minor core and security releases, but they do not confirm that forms, checkout, languages or integrations still work. Automation is a component of maintenance, not ownership of the result.

How often should a WordPress site be updated?

There is no safe universal calendar. Critical security fixes should be assessed promptly; routine releases can follow a scheduled review appropriate to the site’s risk. Back up before significant changes and test the functions that matter to the business.

Does maintenance include hosting?

Sometimes, but not automatically. Bundles are convenient, yet the proposal should separate infrastructure, application care, licences and support allowances so you can compare scope and retain access if the supplier changes.

Is Swiss backup storage necessary?

Swiss storage can support procurement, latency or data-governance preferences, but location alone does not make a backup useful. Access control, encryption, retention, separation from the live environment and tested restoration all matter. Confirm the actual storage and subprocessors rather than relying on a Swiss brand name.

How much should a small Swiss business budget each year?

For a straightforward WordPress brochure site, CHF 600–1,800 per year is a useful starting range. An active, multilingual or lead-critical site often needs CHF 1,800–3,600. Shops and operational platforms commonly require CHF 3,600–7,200 or more. VAT, licences, hosting and major changes may sit outside those figures.

Sources and methodology

Prices and inclusions were checked on 4 July 2026 from the published pages of Digistarter, onlineKarma and O’Matic. Operational guidance was cross-checked against WordPress update documentation and the Swiss NCSC’s cybersecurity guidance for SMEs. Provider packages can change; request a current written scope before buying.