Website maintenance for a small business site is the recurring work of keeping the software patched, the certificates valid, the backups restorable, the pages fast, and the content accurate. In practice that means a short list of jobs on a fixed schedule: update the platform and its plugins, watch for security disclosures, renew TLS certificates, test restores, monitor performance against measurable targets, and fix broken links and stale pages. What separates a real maintenance plan from an invoice is cadence and evidence. Most of the risk on a small business site comes from third-party plugins and from waiting too long to apply a patch, so a plan that checks in monthly is a different product from one that checks in daily — even if both say "updates included.".
Table of Contents
- The core update work, and why it is not automatic
- Plugin inventory is the real workload
- How fast does a patch need to be applied?
- Certificates are becoming a frequent chore
- Performance and content checks on a measurable basis
- Frequently Asked Questions
The core update work, and why it is not automatic
The platform itself is the first line item. PHP — the language WordPress, Drupal and most CMS platforms run on — moves on a fixed schedule: each branch gets two years of active support plus two more of security-only fixes. Per the PHP Group's supported-versions page, 8.2 receives security fixes only until 31 December 2026, 8.3 until 31 December 2027, and 8.4 until 31 December 2028, with 8.6 having shipped on 19 November 2026. A site still on 8.1 or older is running unpatched code today, and that is a hosting-level fix, not a plugin update. On WordPress, the common assumption that "it updates itself" is only partly true.
The WordPress upgrade documentation states that automatic background updates cover minor core releases and translation files on most existing installs; plugin and theme auto-updates stay off unless an administrator turns them on per item, with the single exception of forced security patches pushed by the WordPress.org API. So the plugins — the part carrying most of the risk — sit still by default. Core is not exempt either. Patchstack reported that the WordPress 7.1.4 security release fixed 22 vulnerabilities across 17 advisories, and 7.0.3 fixed 12. Updates are a standing job, not a one-time cleanup.
Plugin inventory is the real workload
If you only fund one maintenance activity, fund plugin control. Patchstack's 2026 WordPress vulnerability statistics attribute 8,658 disclosed issues — 89% of the total — to plugins, against 11% for themes and under 1% for core. Cross-site scripting (31.28%) and broken access control (19.92%) lead the categories. That shifts the job description.
Keeping a count of what is installed, who maintains it, when it was last released, and whether anything still needs it matters more than clicking "update all" on core. Every plugin a small site does not actually use is pure added surface. There is a hard limit worth knowing before you buy a plan advertised on updates alone. In the same 2026 data set, 2,240 of the published vulnerabilities — 23% — had no patch available at all. For those, updating is not an option; the response is removing or replacing the abandoned plugin, or running a web application firewall that virtual-patches the specific request pattern.
How fast does a patch need to be applied?
Fast. Patchstack logged more than 65,000 blocked exploitation attempts against two core flaws within days of disclosure.
Attacks cluster in the window immediately after a vulnerability becomes public, which is exactly the window a monthly maintenance visit leaves open. That gives you a concrete question to ask any provider, and a concrete thing to build if you handle it yourself: A sensible compromise for a small budget: auto-update the low-risk, well-maintained plugins, keep manual control of the two or three that touch checkout, forms or membership, and put a firewall in front of everything.
- How quickly are security releases applied — same day, or at the next scheduled window?
- Is there a staging copy where an update is tested before it reaches the live site?
- Who gets alerted when a vulnerability is disclosed for a plugin this site runs?
- Is there a firewall in front of the site that can block an exploit before a patch exists?
- Is there a tested restore path if an update breaks something, not just a backup file?
Certificates are becoming a frequent chore
TLS certificate renewal used to be an annual afterthought. Under CA/Browser Forum ballot SC-081v3, adopted 11 April 2025, the maximum certificate lifetime falls to 200 days for certificates issued from 15 March 2026, 100 days from 15 March 2027, and 47 days from 15 March 2029, with domain-validation data reuse shrinking alongside it.
Do the arithmetic on that last figure: a site owner renewing by hand would be doing it roughly eight times a year by 2029. The practical answer is automated issuance and renewal at the host or CDN level, plus monitoring that alerts before expiry rather than after. An expired certificate throws a full-page browser warning, so this is one of the few maintenance failures that stops traffic outright.
Performance and content checks on a measurable basis
Performance monitoring belongs in maintenance because it has fixed pass marks rather than opinions. Google's Core Web Vitals guidance rates a page "good" at Largest Contentful Paint of 2.5 seconds or less, Interaction to Next Paint of 200 ms or less, and Cumulative Layout Shift of 0.1 or less — assessed at the 75th percentile of real visits, not a single lab run. One timing detail changes how you review the work.
Those field numbers come from the Chrome User Experience Report over a rolling 28-day window, which Google's PageSpeed Insights documentation describes, so a fix made today may take up to four weeks to show in the site's assessment. Judge an optimisation by a lab measurement immediately and by field data a month later; expecting the dashboard to move the same week produces a lot of pointless re-work. Around that sit the unglamorous content jobs: checking contact forms actually deliver, fixing broken internal and outbound links, correcting prices and hours, and removing pages for services no longer offered. These rarely cause an outage, which is precisely why they drift for years.
Frequently Asked Questions
Is a monthly maintenance plan enough for a small business site?
For content fixes and backups, yes. For security it is thin: exploitation attempts spike within days of a disclosure, so security releases need same-day handling or a firewall covering the gap.
Should I just turn on auto-updates for everything and skip the plan?
Auto-updates close the easy cases but not the 23% of 2026-disclosed vulnerabilities with no patch available, and they can break a site with no one watching. Pair them with staging and a tested restore.
Who handles the PHP version — me or my host?
Your host controls which PHP versions are available; you choose from them, usually in the hosting control panel. Confirm the version in use against the PHP Group's support dates before assuming it is current.




