Maintaining a WordPress site in Marbella is not about pressing "update all" every so often. It is about deciding what gets updated, when, with which backup behind it and who takes responsibility if something breaks. For local businesses, most incidents do not come from a sophisticated attack but from an abandoned plugin, an update without prior testing or access details nobody can account for. This guide separates what can be handled from the WordPress dashboard from what requires server access, and explains what each decision costs before you hire maintenance.
What it means to maintain WordPress without breaking it
Maintaining a WordPress site means holding four fronts at once: controlled updates, backups that can actually be restored, live plugins and clear access. If one fails, the other three will not save the site. An update without a recent backup is a gamble; a backup that has never been tested is a dead file.
For a local business in Marbella, with a high season and enquiries arriving by WhatsApp, the website is often the first record a customer sees. That is why maintenance does not aim to have the newest version of everything, but to keep the site working on the day it is used most. That criterion guides every decision below.
- Name one person responsible for approving updates, even if they do not run them
- Set a low-traffic window for updates
- Document which plugins are essential and which can be removed
Updates: what to update and in what order
Order matters more than frequency. First update WordPress and security plugins with a prior backup; then content plugins and the theme; finally anything that affects sales or bookings. Updating everything at once makes it impossible to tell what caused a failure when it appears.
Major WordPress versions often bring changes that affect the editor and some plugins. It is wise not to apply them on release day or during a campaign. A reasonable practice is to wait a few days, read the release notes and test on a copy if the business depends on forms or payments.
| Update type | Usual risk | When to do it |
|---|---|---|
| Core security | Low with a backup | As soon as a critical notice appears |
| Form or payment plugins | Medium-high | With prior testing on a copy |
| Theme and layout | Medium | Outside campaigns and with a backup |
| Major WordPress version | Medium | After a few days of observation |
| Content plugins | Low | In the usual window |
Backups that are actually useful
A useful backup includes files, database and configuration, is stored outside the same server and can be restored in a reasonable time. Keeping backups only on the hosting does not protect against most incidents affecting the hosting itself. The backup needs a date and a person who knows how to restore it.
You do not need an hourly backup for a local business site without continuous sales. A daily backup or one before each relevant change, with several weeks of retention, is enough. What matters is testing restoration at least once and noting how long it takes: that figure defines how long the site can stay down.
Hosting backup
Convenient and fast, but it lives with the same provider. It is a first layer, not the only one.
External backup
Downloaded to separate storage. Protects against hosting errors and accidental deletion.
Restoration test
Without a test you do not know if the backup works. Run it in a separate environment so you do not touch the live site.
Abandoned plugins: how to spot them
An abandoned plugin is one that has not been updated for over a year, no longer receives support or whose author has closed the project. It does not always break the site, but it accumulates security and compatibility risk with new WordPress versions. The plugins screen shows the last update, although not always the real state of the project.
The review should be plugin by plugin, not in bulk. For each one, you need to know what function it covers, whether it is really used and what would happen if it were deactivated. Many businesses accumulate old test plugins nobody remembers, which only add failure surface.
- Note what each plugin does and which page uses it
- Check whether the function is already covered by another plugin or by WordPress itself
- Deactivate one at a time and review the site before deleting
- Replace before removing when the plugin handles data
Who holds access
Access is the area that causes the most problems and gets the least review. There are often old administrator accounts belonging to a previous agency, a designer, a relative or someone who no longer works in the business. Every high-permission account is an open door and a diffuse responsibility.
The minimum is one administrator account per person, with an identifiable name, and a managed password. Access to the WordPress dashboard, hosting, domain and email should sit with the business owner, even if a provider manages them. If the domain is in a third party's name, the business does not control its own website.
Business owner
Must be able to recover control of the domain and hosting without depending on anyone.
Maintenance provider
Works with its own account, with sufficient permissions and without sharing passwords by message.
Old accounts
Reviewed, downgraded or removed. A forgotten administrator account is a real risk.
Dashboard, server and hosting: who does what
Not everything is fixed from the WordPress dashboard. Changing the PHP version, adjusting memory limits, configuring outgoing email or applying server-level cache rules requires hosting access. The WordPress dashboard is for content, users, plugins and theme settings; the server is touched with different responsibility and different risk.
Before hiring maintenance, clarify what each part includes. A plan that only updates plugins from the dashboard will not solve a certificate, DNS or resource-limit problem. And a provider who touches the server without documenting changes can leave the site in a state that is hard to reproduce.
| Task | Handled in the dashboard | Requires server access |
|---|---|---|
| Update plugins | Yes | No, unless there is a failure |
| Create and restore backups | Depends on the plugin | Often yes, for external backups |
| Change PHP version | No | Yes |
| Configure outgoing email | No | Yes, or at the email provider |
| Manage users | Yes | No |
| Certificate and DNS | No | Yes, at the relevant provider |
Common mistakes in local businesses
The most common mistake is updating without a backup and without knowing what was updated. The second is installing a plugin for every small need until the site is heavy and fragile. The third is not reviewing anything for months and doing everything together the week before high season, when any failure costs more.
Ownership mistakes also appear: a domain in a provider's name, email managed by someone who no longer serves the business, passwords shared by message. And judgement mistakes: deactivating security plugins because they "did strange things" or changing the theme to try it without a prior backup. Almost all are avoided with order and records.
- Do not update everything on the same day without a recent backup
- Do not install a plugin without noting what function it covers
- Do not leave the domain in a third party's name
- Do not change theme in production without testing on a copy
What each maintenance decision costs
Cost is not only the monthly fee. It is the time it takes to restore, the hours of someone who understands the problem and the opportunities lost if the site fails at the wrong moment. Cheap maintenance that excludes external backups or plugin review shifts that cost to the business when the incident happens.
At Solaris, SEO from €150/month + VAT covers only the Google Maps listing; from €250/month + VAT it adds articles. It does not include WordPress maintenance. The website is quoted separately: €180 + VAT for one page, €350 + VAT for up to five pages and €450 + VAT for a shop. Any server work, external backups or ongoing support is assessed as additional scope.
| Decision | What it prevents | Cost to assess |
|---|---|---|
| Updating with a backup | A site down with no way back | Testing and restoration time |
| Reviewing plugins | Accumulated security risk | Review and replacement hours |
| External backups | Loss from hosting failure | Storage and configuration |
| Tidying access | Lockouts from third-party accounts | Management and documentation |
| Ad hoc support | Solving without your own criteria | Quote according to scope |
How to organise maintenance in practice
A simple calendar works better than a complex plan. A monthly review of updates and plugins, a daily automatic backup, a quarterly restoration test and an annual review of access and domain ownership. That rhythm covers most needs of a local business without generating unnecessary work.
Put in writing who does what and how relevant changes are reported. If the business manages content and a provider manages technical work, notices must be clear: what was touched, when and what needs checking. Without that record, every incident is investigated from scratch.
- Monthly review of updates and plugins
- Daily automatic backup with several weeks of retention
- Quarterly restoration test
- Annual review of access, domain and hosting