
Most business owners remember website maintenance when something breaks. The form stops working, the site won't open, or the browser shows a security warning. What gets done at that point isn't maintenance anymore, it's repair, and repair usually costs more.
What happens to an unmaintained site?
A website doesn't stay the way it was on launch day. The software it runs on (the content management system, plugins, the server's PHP version, libraries) is updated constantly. Holes in outdated software become public knowledge over time, and automated bots scan for them.
Situations commonly seen on unmaintained sites: a site that hasn't been updated in a long time may wake up one morning with spam links added to it. A contact form may have been broken for months without anyone noticing, because it shows a 'sent' message while the emails go nowhere. If the SSL certificate isn't renewed, browsers show visitors a 'not secure' warning. The hosting company upgrades PHP on the server, an old plugin isn't compatible, and part of the site may show blank pages.
None of these is a huge disaster. But each can lose customers until you notice.
The cost difference is clear too. Cleaning up a hacked site, finding and removing malicious code, changing passwords and getting Google's warning lifted often takes several days, during which the site is either down or greets visitors with a warning screen. Regular updates and backups for the same site often cost less than a single cleanup. And after the cleanup, maintenance is still needed.
Thinking of maintenance as insurance isn't quite right either. With insurance, if nothing happens, the money seems to have bought nothing. With maintenance, concrete work gets done every month: updates installed, backups taken, a broken link fixed, outdated information refreshed.
Weekly checks
Setting aside 10 to 15 minutes a week is enough:
- Open the site on your phone and computer, and check that the homepage and a few key pages look right.
- Send yourself a test message through the contact form and confirm the email actually arrives.
- Tap the WhatsApp button and phone link, if you have them.
- Check when the backup last ran.
The form test is the most important item on this list. A broken form is a fault that silently costs you leads; neither you nor the visitor sees an error.
Monthly checks
Once a month, a slightly more technical round is needed. These are usually done by whoever provides maintenance, but you should know what is being done:
- Update the platform and plugins. Take a backup first and, if possible, test in a staging environment.
- Delete unused plugins and themes. Deactivating may not be enough; an undeleted plugin can still be a security hole.
- Check Search Console for new errors, security warnings or pages dropping out of the index.
- Measure site speed with PageSpeed Insights and compare with last month.
- Scan for broken links.
- Review the admin user list: is the account of an employee who left, or an outside team whose project ended, still active?
- Look at how much spam comes through forms and tighten protection if needed.
- Test restoring from backup, even if only every three months.
The last item is the easiest to skip. Backups that were taken but can't be restored, or turn out incomplete, are common. An untested backup isn't a backup, it's a hope. We covered how to plan backups in a separate article.
Yearly checks
Once a year, look at the whole site with a wider lens:
- Domain and hosting renewal dates. Is auto-renew on, and is the saved card still valid?
- How the SSL certificate is renewed.
- Is all the text on the site still accurate: prices, service list, team, address, opening hours, legal texts?
- Are the software versions on the server still supported?
- Overall performance: visitors, forms and calls compared with last year.
The content check matters in particular. Businesses with a price list from three years ago, or a former employee still on the team page, tell visitors 'nobody really looks after this place'.
Do it yourself or get support?
You can and should do the weekly checks yourself; nobody knows the site better than you. The monthly technical work needs more care. If you don't know how to roll back when an update breaks the site, doing updates yourself is risky.
Ask yourself: what would we lose if the site were down for a day? If something breaks after an update, is there someone who can fix it? Do we really have time to do these checks every month? If any answer is 'no', a regular maintenance service can cost less than repair bills.
We covered what drives maintenance pricing in a separate article, and collected security measures in another. Kodyva's monthly maintenance package covers software updates, regular backups, security and performance checks, and small content changes. The price range is 2,500 to 7,500 TL a month; the exact price is set in the quote based on scope. Whether you take a package or not, adding the list above to a calendar reminder is a good start.
Frequently Asked Questions
Does a static or simple site need maintenance too?
Less, but not zero. Domain and SSL renewals, form tests, content accuracy and server updates apply to every site.
Is it safe to run updates automatically?
For small security updates, usually yes. For major version updates, take a backup first and check the result; an automatic update can break the site without anyone noticing.
Does maintenance include content changes?
It depends on the package. Many maintenance services cover small text and image changes; adding new pages or sections is usually priced separately. Ask for this to be written clearly in the contract.
Blog posts are for general information only and are not a substitute for legal, financial or technical advice.