What happens when a WordPress site is left alone
A neglected site keeps loading while the software under it ages. Patchstack's report on WordPress security counted 11,334 new vulnerabilities in 2025, with 91% of them in plugins. WordPress's own hardening guide says older versions of WordPress receive no security updates.
A hacked site can look normal to its owner. Our post on what a hacked WordPress site looks like walks through a real cleanup. Once Google detects the hack, your pages can carry a warning label in search results.
Updates to core, plugins and themes, with a staging copy for risky ones
WordPress applies minor and security releases by itself on most sites. Plugins and themes work another way: their automatic updates are opt-in, and an administrator switches them on one plugin or theme at a time. So a site can run current WordPress beside plugins that are years old.
We update all three on a schedule. WordPress's update instructions begin with a backup, and so do we. We read the release notes before each update, and we check your key pages and forms afterward.
After each round you get a short note. It lists what we updated, what we held back and why, and anything that needs your decision, such as a plugin its author has abandoned.
Some updates carry more risk: a new major version of a page builder, of WooCommerce, or of PHP on the server. We apply those to a staging copy first, which is a private duplicate of your site. If the copy breaks, your visitors see nothing, and we fix the cause before we touch the live site.
Backups you can restore from
A WordPress backup has two parts, the database and the files. WordPress's backup guide says you need both to restore a site, and advises keeping three to five recent backups in different locations.
We go one step further and restore a backup to the staging copy. Until someone restores a backup, nobody knows whether it works.
Uptime and malware checks
An automated check loads your site at regular intervals and alerts us when it stops answering. For malware, we compare your files against clean copies, review the list of administrator accounts and read the Security issues report in Search Console. That report shows what Google found if it judges a site hacked or harmful to visitors.
Removing what you do not use
The hardening guide is blunt about spare plugins: "if you are not using a specific plugin, delete it from the system." WordPress treats deactivating and deleting a plugin as two separate steps, and a deactivated plugin keeps its files on the server. We remove unused plugins, spare themes and administrator accounts that belong to nobody.
Who needs WordPress maintenance services, and who does not
You may not need us if your host runs updates and backups for you and someone on your team logs in each week. Put two questions to that host: do the backups include the database, and has anyone restored one?
You do need a plan if the site takes orders or inquiries and nobody owns its upkeep. A store has more at stake, and we cover that under WooCommerce development. If the site is too old to update safely, a full redesign may cost less than repair.
We work from New York and look after sites for owners elsewhere too, including sites we did not build.
Maintenance keeps a site healthy. New features, rewritten pages and design changes fall outside it, and we scope that work on its own.
What we need from you to start
- An administrator login for WordPress.
- Access to your hosting account, so we can reach files, the database and backups.
- The name of whoever built the site, if you know it, and any paid plugin licenses.
- A list of the pages and forms your business depends on, which become our checks after each update.