A WordPress site nobody touches doesn’t stay the way it was. Its plugins age, the security holes found in them get published online, and bots scan the web specifically to find the sites that never updated.
Site owners don’t neglect their sites on purpose. They just believe a few things that sound reasonable and often aren’t true. Here are six of them, and what actually happens.
MYTH 1
“The site works, so there’s no reason to touch it”
A site can look perfect and still be compromised. Patchstack, a security company that tracks WordPress vulnerabilities, found that 91% of the new vulnerabilities discovered in 2025 were in plugins, and only six were in WordPress core itself. When a developer patches a plugin, the details of the hole become public. On your site, it stays open until you update.
And the signs show up late: spam pages in Google under your domain, redirects to strange sites, or a Google warning that your site is dangerous.
MYTH 2
“Automatic updates already take care of it”
By default, WordPress only installs minor core updates on its own. Automatic plugin updates have to be switched on, plugin by plugin. And premium plugins, like page builders and sliders, don’t update at all once their license has expired.
Even when everything updates, someone has to check afterwards. Recently a page builder update wiped the video at the top of one of our clients’ homepages. The site worked, the forms worked, and anyone landing on the homepage saw a grey blank. We caught it while going through our clients’ sites. Nobody had called to complain.
MYTH 3
“My hosting company keeps a backup”
Sometimes it does. But if the backup lives on the same server as the site, it won’t help the day that server goes down. And if only one week of backups is kept, a hack that happened a month ago and was only discovered now is already in every copy.
A good backup is stored off the server, with several copies from different dates. And someone should have tried restoring from it at least once, because otherwise you have no way of knowing it works.

MYTH 4
“It’s a small site. Who would bother hacking it?”
Nobody picks you specifically. Bots scan sites nonstop, looking for one vulnerable version of one plugin. When they find a site running it, they get in. A bot doesn’t care whether it’s a bank or a Pilates studio.
Usually they aren’t after your data at all. They want the server: to send spam from it or to host pages that promote other sites. Sometimes also to send your visitors somewhere else. And when Google flags a site as dangerous, it makes no difference whether the site is small or large.
MYTH 5
“If something breaks, I’ll know”
The problems that cost the most to miss are the quiet ones. A contact form that stopped sending emails looks exactly like one that works. Nobody will message you about an SSL certificate that didn’t renew, a service page that dropped out of Google, or a site that became slow on phones either. Usually you find out only when you notice the inquiries have dropped.
MYTH 6
“I’ll update everything at once when I have time”
The longer you wait, the bigger and riskier the update gets. A plugin that hasn’t been updated for a year jumps several versions at once, and along the way things your site depends on change. When you update twenty plugins together and something breaks, it’s hard to tell which one did it.
Then there’s the server. Hosting companies raise the PHP version over time, and an old plugin that was never updated can take the whole site down the day that happens, without you touching anything. A small monthly update takes half an hour. An update after two years can take several days, and sometimes you discover that some plugins were abandoned and there is nothing to update, only to replace.
What good maintenance includes
Updating plugins, theme and core, always after a backup, and checking the key pages as soon as the update finishes.
A daily backup off the server, so there are always several dates to go back to.
A test submission through the site’s forms, to make sure the emails really arrive.
Keeping an eye on the server’s PHP version. A version that no longer gets security updates leaves the server exposed even without a vulnerable plugin.
Regular checks in Search Console: errors, pages that fell out of the index and security alerts. If important pages disappeared, that’s where you start working out why the site isn’t showing on Google.
Deleting plugins you don’t use. A deactivated plugin still sits on the server.
That’s how it works on the sites we manage: a security check runs on them every night. Every update starts with a backup and ends with a check of the key pages. We also wrote a separate article on 24/7 website monitoring with AI. And if a new site is coming up, we plan maintenance from the website building stage, not after launch.
Your site hasn’t been updated in a while?
We’ll check it and tell you what needs fixing now and what can wait.
Questions about site maintenance
How long does it take to update a site that hasn’t been updated in a year or two?
It depends on how many plugins there are and what shape they’re in. Usually you update in stages on a copy of the site, test, and only then move the changes to the live site. When a plugin’s developer has stopped updating it, it has to be replaced, and that’s the part that takes the longest. On a site that hasn’t been updated for two years, the whole process can take several days.
Should I turn on automatic updates for every plugin?
For simple, well-known plugins, you can. Plugins your site relies on, like the page builder, the shop or the forms, are better updated by hand: back up, update and check the site as soon as the update finishes. That way, if something breaks, you know exactly what broke it.
Isn’t my hosting company responsible for maintenance?
On most plans it’s responsible for the server: that it’s up, fast and updated. What happens inside WordPress (plugins, theme, forms and content) is on you. Some “managed WordPress” plans update plugins too, but even there, usually nobody checks that the site still looks and works right after the update.
How often should I update?
Security updates are worth installing within a few days of their release. The rest can be batched every two weeks or once a month, with a backup before and a check after. On a site with a shop or a lot of inquiries, check for updates at least once a week.
What do I do if my site has already been hacked?
First, don’t panic and don’t start deleting files. Restore from a clean backup from before the hack, change every password, update whatever was vulnerable and check in Search Console that Google hasn’t flagged the site as dangerous. If there’s no clean backup, the site has to be cleaned by hand, and that’s a job for professionals.