WordPress maintenance services are the recurring work that keeps a WordPress site updated, backed up, secure and checked: core, plugin and theme updates, a supported PHP version, tested backups, and a named person who notices when a form stops sending. This guide is for owners and small marketing teams in the Twin Cities East Metro, the St. Croix Valley and western Wisconsin who run on WordPress and want to know what a care plan should cover before they sign one.
One limit up front. McKinney Creative Ventures does not sell WordPress maintenance plans or WordPress hosting, so nothing below is a pitch for one. We describe the work the way WordPress's own documentation does and say at the end what we do for sites that have outgrown WordPress.
What WordPress maintenance services include
The work falls into five groups. Each has a source in WordPress's documentation, and each is a line a provider should be willing to name in writing.
Core, plugin and theme updates
WordPress's documentation on updating WordPress says you should always update to the latest version, and that before updating you should check that your plugins and themes are compatible with the version you are installing. It also says there is no single update order that works for every site: some plugins need an update before WordPress, and others need a newer WordPress first. In our reading, that is why updates need a person who reads release notes and checks the site afterward, since an automatic setting does neither.
Automatic updates exist. The developer handbook's page on upgrading WordPress says automatic background updates were introduced in WordPress 3.7 and are enabled by default on most sites. Since WordPress 5.6, new installations also get major core updates by default unless WordPress detects a version control checkout, while existing installations keep the earlier behavior unless a site administrator, a constant or a filter turns major core auto-updates on. Plugin updates are a per-plugin choice. The page on managing plugins describes an Enable auto-updates link next to each plugin on the Installed Plugins screen.
PHP version and hosting requirements
WordPress's requirements page says, as of November 2026, that it recommends a host support PHP 8.3 or greater, MariaDB 10.11 or greater or MySQL 8.0 or greater, and HTTPS. It adds that older PHP 7.4 and MySQL 5.5.5 setups still work but have reached end of life and may expose a site to security vulnerabilities. A plan should say who watches the PHP version and who asks the host to change it.
Backups and restore tests
The handbook's backup page says a typical WordPress site needs two backups, the files and the database, because the database lives outside the WordPress directory. It says to back up the database regularly and always before an upgrade, suggests weekly backups for smaller sites and daily backups for high-activity sites, and recommends keeping at least three to five recent backups in different locations. It also recommends a manual backup of the automatic backups once in a while, to confirm the process is working. Ask a provider for a restore test: load a backup onto a test copy and confirm the site comes up.
Security basics
The handbook's hardening page says to keep plugins updated, to delete any plugin you are not using, and to take plugins and themes only from the WordPress.org repository or well known companies. Google's page on preventing malware infection tells owners to keep a list of all the software and plug-ins on the site with version numbers, and calls it a common pitfall to install a forum or blog and then forget about it. Our post on protecting a website from hacks covers passwords, two-step sign-in and what to do after a compromise.
Monitoring and form checks
WordPress includes a Site Health screen under Tools. Its status tab groups findings as critical issues, recommended improvements and passed tests, and the critical issues it lists include plugins waiting to be updated, an outdated PHP version and background updates that are not working as expected. Site Health cannot tell you that a contact form emails an inbox nobody reads, so a plan should also name the person who submits a test lead and confirms it arrives.
What a WordPress care plan should list in writing
A WordPress care plan, a website care plan and a maintenance plan are all names for a written scope. Without one, two quotes cannot be compared and nobody can tell later whether a task was skipped. The table lines up each task, what WordPress's documentation says about it, and what to look for in a plan.
Scroll to see all columns
| Task | What WordPress's documentation says | What to check in a plan |
|---|---|---|
| Core updates | Update to the latest version, back up first, check plugin and theme compatibility | Who approves updates, how often, and whether they are tried on a copy first |
| Plugin and theme updates | Keep plugins updated and delete unused ones | A named list of installed plugins and who holds each license |
| PHP and database | PHP 8.3 or greater and MariaDB 10.11 or greater or MySQL 8.0 or greater are recommended | Who tracks the version and who asks the host to change it |
| Backups | Back up files and database, before every upgrade, kept in different locations | Frequency, where copies are stored, and the date of the last restore test |
| Security | Update plugins, use trusted sources, use strong passwords | Named user accounts, two-step sign-in and a written contact for an incident |
| Monitoring | Site Health flags an outdated PHP version and pending plugin updates | Uptime alerts, a form test and a short written report each month |
| Support and edits | Not covered by the documentation | Response time, support hours and what counts as an edit |
Price is the last line to compare, because two plans at the same price can cover different work. Ask each provider to price the same list, with response time and restore time in writing. That is the practical way to find an affordable plan. Our post on website maintenance cost for a small business goes through the cost components in general terms.
WordPress hosting and maintenance: where one ends and the other begins
WordPress hosting and maintenance are separate jobs, and many sites have a gap between them. Hosting is the server: its operating system, PHP version, database and network. Maintenance is the WordPress software on top of it: core, plugins, themes, users and content. Google's malware page draws the same line. It says a site may still be vulnerable if the web host has not installed the most recent operating system patches, even when the owner keeps every website component updated.
Some hosts bundle updates and backups into a managed WordPress plan. The upgrade page notes that some hosting control panels can run updates for you, so what a given host does depends on the plan you bought. Ask the host these questions and keep the answers:
- Who patches the server, and how are you told when it happens?
- Where are backups stored, how long are they kept, and are they stored in the same account as the site? The backup page recommends different locations.
- Whose name is on the hosting account and the domain registration?
Questions to ask a WordPress maintenance provider
The questions do not depend on where the provider sits. We are a Woodbury, Minnesota agency, and a business anywhere in the metro, from Minneapolis to Hudson, can use the same list. Ask whether support hours follow Central time and who answers on a Saturday in your busy season.
- Who has administrator access, under which names? Every person and company should have their own account, so access can be removed without changing a shared password.
- How are updates tested? Ask whether a backup is taken first and whether the forms, phone links and checkout are tested afterward.
- How fast is a restore, and when was the last test? Ask for a time in writing, and for the date a restore was last tried.
- Who owns the hosting, domain and backup accounts? They should be in your business's name, with the provider added as a user.
- What happens when an update goes wrong? WordPress documents one case: if a failed update leaves the site stuck in maintenance mode, check whether a .maintenance file remains in the WordPress root directory. A provider should know that and many other cases.
- What is the plan if the site is hacked, and who pays for cleanup? The answer belongs in the scope, not in a conversation after the fact.
If you run a retail shop or any site that takes payments, the list is longer. Our post on e-commerce website maintenance covers checkout, payment security and shop settings.
How a small marketing team splits WordPress maintenance
In our experience, maintenance on a small team holds up when each job has a name beside it.
- One approver for updates. This person picks the update window. For a heating, snow removal or lawn care site in Minnesota, that window should not land in the first week of the busy season.
- One tester. After each batch of updates, one person submits the contact form, taps the phone link and checks the booking button on a phone.
- Named accounts, with the right role. WordPress's roles page lists six roles and says Administrators on a single site have access to all administration features. It lists capabilities such as updating core and plugins and installing plugins among those held only by Administrators on a single site, In our reading, that means most of the team can work as Editors or Authors.
- One shared inbox for alerts. Uptime and backup notices should reach a team address.
- A written handoff. When a team member leaves, remove the account the same day and keep a record of plugins, licenses and renewals.
When the maintenance burden is a reason to rebuild
Maintenance has a ceiling. In our experience, these are signs that a site has reached it: a long list of plugins nobody can explain, updates that break the layout each time, a theme that holds the site on an unsupported PHP version, and a care bill that buys very little change. Google's malware page says that many tools make building a website easy, but each one adds some risk of being exploited. Fewer moving parts means fewer things to keep current.
McKinney Creative Ventures rebuilds sites off WordPress. Our website service covers design, rebuilds, hosting, ongoing management and custom web apps, and our default build is Astro on Cloudflare Pages. We host and manage what we build, and we run automated weekly checks across the sites we manage for broken links, missing images, dead forms and blocked crawlers. On a rebuild, every URL on the old site is crawled and mapped to its replacement with a permanent redirect before launch. A rebuild is not the right move for every WordPress site. A heavy editorial operation, for example, may be better off staying put under a good care plan. If you want to see how we work, start with our website design and rebuild service.
If you are weighing a care plan against a rebuild, contact us and we will give you a straight read on which fits your site.