WordPress is the most common content management system for business websites, in Finland as elsewhere. Its strength is extensibility: there is a plugin for almost any need. The same feature is also the biggest maintenance challenge. A typical business website consists of the WordPress core, a theme and 10–30 plugins, each developed by a different party at its own pace.
This guide explains how to maintain a WordPress website in a controlled way in 2026.
What gets updated in WordPress?
A WordPress website has four layers that need updating:
- The WordPress core. Major versions are released a few times a year, and security fixes arrive as minor releases when needed.
- Plugins. Most vulnerabilities in WordPress websites are found in plugins, not in the core.
- The theme. Commercial themes and the page builders bundled with them in particular need updates.
- The server environment: PHP, the database (MySQL or MariaDB) and the web server. The hosting provider usually takes care of these, but the choice of PHP version is often left to the customer.
The purpose of updates is not to get new features but to fix known vulnerabilities. Once a vulnerability is published, automated scanners often start looking for it across the internet the same day.
The right order of updates
A controlled update always follows the same order:
- Backup of the files and the database. Check that it completed.
- Plugins one at a time or in small batches, so that the culprit is easy to identify if something breaks.
- The theme and the compatibility of its child theme.
- The core, once the plugins support the new version.
- Check: the home page, the key service pages, the contact form (send a test message) and, for an online shop, a test order and login.
Testing the form is an important step. A broken contact form does not show in the site's appearance, but it cuts off the flow of leads, and the fault can go unnoticed for weeks.
PHP version in 2026
WordPress 7.0 was released in spring 2026. At the same time the minimum requirement rose to PHP 7.4, and support for PHP 7.2 and 7.3 ended. WordPress nevertheless recommends PHP 8.3 or newer. The minimum requirement only tells you which version WordPress still runs on. It does not mean the version is secure.
| PHP version | Status in November 2026 | Recommendation |
|---|---|---|
| 7.4 and older | No security support (support for 7.4 ended in 2022) | Update now |
| 8.0 and 8.1 | No security support | Update now |
| 8.2 | Security support ends on 31 December 2026 | Plan the update now |
| 8.3 | Security fixes until the end of 2027 | A good choice |
| 8.4 and 8.5 | Active support | Recommended if your plugins support them |
Updating the PHP version is one of the most effective maintenance tasks: it improves security and often speed too. Before switching, check that the theme and plugins support the new version. A staging environment is the best place to do that.
Managing plugins
Every plugin brings code to your site that someone else maintains. There are three principles for managing plugins.
Remove unused plugins
A deleted plugin cannot be a vulnerability. Deactivating is not enough, because the files of a deactivated plugin remain on the server. Review your plugins at least once a year and ask of each one: is this still needed, and could a plugin that is already installed do the same job?
Check that a plugin is alive
Before installing, and in the annual review, check the plugin's last update, the WordPress version it has been tested with and the number of active installations in the WordPress.org directory. If the plugin has not been updated for over a year or has been removed from the directory, find a replacement.
Avoid overlap
Two caching plugins, two SEO plugins or a page builder on top of the theme's own builder cause conflicts and slow the site down.
Staging environment
A staging environment is a copy of the website where updates and changes are tried out before they go into production. Many hosting providers let you create one with a single click. Use a staging environment at least in the following situations:
- a major WordPress version update
- a change of PHP version
- a major version update of the theme or page builder
- updates to an online shop's payment or shipping plugins.
Remember to block indexing of the staging environment so that Google does not find two copies of the site.
The Site Health tool
WordPress's own Site Health tool (Tools → Site Health) is a good starting point for a monthly check. Among other things, it tells you:
- the PHP version and whether it is recommended
- whether HTTPS is in use
- whether scheduled tasks are running
- whether the site has inactive plugins or themes that should be removed
- whether the REST API and loopback requests are working.
The tool does not replace a security scan, but it quickly reveals the most common oversights.
Administrator accounts and permissions
Maintenance also covers user management. WordPress has built-in roles, and the principle is that everyone gets only the permissions they need:
- Administrator only for those responsible for technical maintenance
- Editor for those responsible for content
- Author or Contributor for occasional content producers.
Turn on two-factor authentication for administrator accounts, and remove the accounts of former employees and suppliers as soon as the cooperation ends. Read more in Website security.
Maintenance checklist
Weekly
- Update plugins, the theme and the core after taking a backup.
- Test the contact form and the most important pages.
Monthly
- Go through the Site Health view.
- Check the reports of the security plugin or the server's malware scan.
- Follow the indexing and performance reports in Search Console.
Annually
- Trim the plugins and check that they are still maintained.
- Check the PHP version and its support period.
- Review user accounts and roles.
The big picture of maintenance is covered in Website maintenance, and backup practices in the backup guide.
Frequently asked questions
Should I turn on automatic WordPress updates?
Minor security releases of the core are automatic by default, and they should stay on. Automatic plugin updates suit simple websites with few plugins and a working backup. For online shops and integrated sites, a controlled update through a staging environment is safer.
Where can I see my site's PHP version?
In the WordPress dashboard under Tools → Site Health → Info → Server. The Site Health view also warns you if the PHP version is outdated. The PHP version is usually changed in the hosting control panel.
How many plugins can a WordPress site have?
There is no exact limit. What matters is the quality of the plugins: are they actively updated, do they have many users and are they really needed? Ten well-maintained plugins are better than three abandoned ones.
What should I do if an update breaks the site?
Restore the last working state from a backup, or disable the problematic plugin by renaming its folder on the server. When a critical error occurs, WordPress recovery mode sends the administrator an email with a link that gives access to the dashboard to fix the problem.