One morning, a business owner in Bandar Lampung opens his company website to send a link to a prospective client. The page loads slowly. A few seconds later, a blank page appears with the words "Error 500." He refreshes: still the same. He opens it on his phone: still the same. Eventually he sends the link anyway, hoping the prospect doesn't bother clicking.
The website that was "already finished" turns out to never really be finished. It's an expensive lesson many businesses learn: a website is a living asset that needs routine care, just like a physical store that needs cleaning, repairs, and tidying to stay worth visiting.
This article covers website maintenance completely: what actually needs maintaining, how often, realistic costs in Indonesia, signs your website is getting sick, and how to choose the right maintenance service.
Why an Untended Website "Breaks on Its Own"
Many business owners think: "The website is paid for in full, now we just use it." Unfortunately, technology doesn't work that way. An unmaintained website deteriorates on its own through several mechanisms:
Outdated security. Content management systems (CMS), plugins, and third-party libraries have security holes discovered continuously. Hackers scan the internet looking for websites running old versions—and Indonesia is one of the countries with high rates of cyberattacks. BSSN (Indonesia's National Cyber and Crypto Agency) records thousands of cyber incidents every year; un-updated SME websites are the easiest targets.
Declining compatibility. New browsers, operating systems, and devices keep appearing. Code written three years ago can stop working correctly in the latest Chrome version, or display broken on this year's Android phones. Without maintenance, your website slowly becomes "outdated" in visitors' eyes.
Falling performance. Growing databases, accumulating caches, unoptimized images—all of this slows a website down gradually. Impatient visitors leave; Google demotes slow websites.
Stale content. A website that's never updated looks abandoned. Prospective clients see "Last news: 2023" and wonder whether your business is still operating.
The conclusion: a website is a subscription, not a one-time purchase.
Maintenance Components You Need to Understand
Website maintenance isn't one activity but a set of parallel tasks. Here are the main components:
1. Security
This is the most critical component and the most often neglected. It includes:
- Routine updates of CMS, plugins, themes, and libraries—as soon as security patches are released.
- Malware monitoring and cleanup if infected.
- Web application firewall (WAF) to block common attacks.
- Periodic security scans to detect vulnerabilities.
- Access management: remove unused accounts, strengthen passwords, enable two-factor authentication.
A hacked website can be a reputational disaster: your pages could be injected with gambling or phishing content, penalized by Google (blocked from search results), and lose customer trust. Read our complete website security guide for businesses.
2. Backups
A backup is a safety net you hope to never need—until you really do. Requirements for healthy backups:
- Automated and scheduled — daily for websites with dynamic data (online stores, booking systems).
- Stored in a separate location — not on the same server as your website.
- Tested regularly — a backup that was never tested isn't a backup; it's hope. Test restoration at least every 3 months.
Databases, uploaded files, and configuration must all be covered. When a website is lost to a bad update or ransomware attack, a restorable backup is the difference between "an overnight disruption" and "a week of halted business."
3. Software Updates
CMS, plugins, themes, and frameworks must follow supported versions. Updates aren't just about "being latest"—old versions stop receiving security patches, and compatibility problems pile up.
One thing to note: updates aren't risk-free. Major updates sometimes break existing functionality. The correct process: back up first, update in a test environment, then apply to production. Professional maintenance services always follow this flow.
4. Monitoring
You can't fix what you don't know is broken. Good monitoring covers:
- Uptime — is your website online or not? Fast notification when it goes down.
- Performance — load speed, Core Web Vitals, and trends over time.
- Errors — server errors (5xx), application errors, and error logs.
- SSL — is the certificate still valid? An expired one makes browsers block your website.
- Domain — domain expiration date. An expired domain can be taken by someone else.
5. Bug Fixes
No website is bug-free. Forms that don't send, buttons that don't work on certain devices, layouts that break in new browsers—all of this appears over time. Maintenance services cover small bug fixes that don't require major development.
6. Periodic Performance Optimization
Monthly or quarterly, a website needs a "service": cleaning the database, optimizing images, refreshing caches, and reviewing speed. This keeps the website fast as content and traffic grow.
7. Content Updates (Optional)
Some businesses ask maintenance teams to handle content: writing blog posts, updating product information, changing promo banners. This can be part of a maintenance package or separated as a content service.
How Often Should Maintenance Happen?
The ideal frequency depends on the website type. Here are realistic guidelines:
| Activity | Static/company profile site | Online store / system | Custom application |
|---|---|---|---|
| Backups | Weekly | Daily | Daily |
| Security updates | Monthly | Weekly | Weekly |
| Uptime monitoring | 24/7 automated | 24/7 automated | 24/7 automated |
| SSL/domain checks | Monthly | Monthly | Monthly |
| Performance optimization | Quarterly | Monthly | Monthly |
| Full security review | Quarterly | Monthly | Quarterly |
The more data and transactions a website handles, the more often and seriously it needs maintenance. An online store down for one hour during peak time loses real sales; a profile site down for one night is easier to forgive.
How Much Does Website Maintenance Cost in Indonesia?
Maintenance costs vary widely by complexity. Here are realistic estimates for the Indonesian market in 2026:
| Website type | Basic plan (monthly) | Standard plan (monthly) | Complete plan (monthly) |
|---|---|---|---|
| Landing page / simple profile | Rp 150–300 thousand | Rp 300–600 thousand | Rp 600 thousand–1.5 million |
| Multi-page company profile | Rp 300–600 thousand | Rp 600 thousand–1.5 million | Rp 1.5–3 million |
| Online store / e-commerce | Rp 600 thousand–1.5 million | Rp 1.5–3 million | Rp 3–7 million |
| Custom web application | Rp 1–2 million | Rp 2–5 million | Rp 5–15 million |
What differentiates the plans:
- Basic: backups, security updates, uptime monitoring, small incident handling.
- Standard: everything above plus periodic performance optimization, small bug fixes, and monthly reports.
- Complete: everything above plus fast response times, small content/feature changes, handling priority, and SLA guarantees.
Alternatively, if you have an internal IT team, you can manage it yourself—but also count their time cost. Maintenance done "whenever there's time" by someone whose main job is something else almost always gets forgotten. The reality on the ground: many SME websites' last backup is more than a year old, and nobody knows until disaster strikes.
Signs Your Website Needs Attention
Some symptoms indicate your website is under-maintained:
- "Not Secure" warnings in the browser — SSL is broken or expired.
- Warnings in Google Search Console — malware, indexing issues, or penalties.
- Occasional error pages — 500, 502, or unintended 404s.
- The website gets progressively slower over time.
- Suspicious content appears — suspicious redirects, strange pop-ups, extra pages you didn't create.
- Features silently stop working — forms don't send, notifications fail, payments error out.
- A CMS dashboard full of update notifications ignored for months.
If you experience several of these symptoms, your website needs care—now, not later.
Managing Maintenance In-House vs Outsourcing
In-House
Suitable if you have an internal technical team with capacity. Advantages: full control, no subscription fees. Disadvantages: hidden costs (salaries, training), priority risks, and a single point of failure—if that person leaves, the knowledge leaves too.
Outsourcing to Professionals
Suitable for most SMEs and mid-sized companies. Advantages:
- Proven expertise — teams handling many websites know problem patterns and solutions.
- Continuity — not dependent on one person.
- SLAs (service level agreements) — binding response times, not "tomorrow if I get around to it."
- Documented knowledge — clean change logs and procedures.
Disadvantages: ongoing monthly costs, and you need to choose a truly competent vendor. Some "cheap" providers only sell weekly backups and promises—not real maintenance.
Things to avoid when choosing a maintenance provider:
- Prices that are too cheap (below Rp 150 thousand/month) — usually just a weekly backup, no monitoring, no accountability.
- No written SLA — no guaranteed response time when problems occur.
- Non-transparent access — you must retain full access to domain, hosting, and code.
- No periodic reporting — you never know what's actually being done.
Questions to Ask a Maintenance Provider
Before signing a maintenance package, ask:
- "What exactly is included in this package?" Ask for a detailed list, not "everything is covered."
- "What's your response time for critical vs non-critical issues?" The SLA must be written.
- "How does your update process work—straight to production or tested first?" Careless updates can break a website.
- "Where are backups stored, and how often is restoration tested?" Vague answers are a red flag.
- "Can I see a sample report?" Serious providers have clear report formats.
- "What happens if the website gets malware?" Is cleanup included, or an extra cost?
- "Is there a warranty on fixes?" Some providers guarantee specific bug fixes within a certain period.
Competent vendors welcome sharp questions; incompetent ones will dodge.
Building a Website That's Easy to Maintain
The best decisions start early: a website designed with maintenance in mind will be far cheaper and safer to care for. Key principles:
- Choose mainstream technology — popular technologies have more developers, documentation, and fast security patches.
- Avoid excessive customization — every customization is code that must be maintained. Use standard features when they're enough.
- Document everything — credentials, architecture, deployment procedures, vendor contacts. An undocumented website is a puzzle for whoever comes later.
- Ensure clear ownership — domain, hosting, and source code in your name. Without this, you can't switch providers when maintenance disappoints.
- Plan an annual budget — set aside roughly 15–25% of the build cost per year for maintenance.
Read our guides on choosing a software house and website development costs—both topics tie directly into long-term maintenance costs.
The Annual Maintenance Calendar
Good maintenance is routine and scheduled, not reactive. Here's an example calendar you can adapt—whether managed by an internal team or a service provider:
Every Day (Automated)
- Automated backups run (for websites with dynamic data)
- Uptime and error monitoring runs 24/7
- Immediate notifications for any anomaly
Every Week
- Review the short monitoring report
- Small security updates if patches are released
- Check order/form status for transactional businesses
Every Month
- Update CMS, plugins, and libraries (with backup and testing first)
- Review error logs and fix small bugs
- Check SSL certificate and domain expiration
- Monthly report: uptime, performance, work performed
- Quick backup test (restore to a test environment)
Every Quarter
- Full performance optimization: database, images, cache
- Security review: access audit, malware scan, password review
- Full backup restoration test
- Evaluate development needs: what features should be added?
Every Year
- Full security audit by an independent party (for businesses handling sensitive data)
- Domain and certificate renewal (if not automated)
- Review the maintenance contract and compare market prices
- Technology evaluation: is the website still on a supported version?
This calendar isn't a rigid rule—small businesses can tighten the schedule, large businesses can add layers. The key: a written schedule that gets executed, not good intentions that evaporate.
Disaster Recovery: When the Worst Happens
Every serious business must have an answer to one question: "What do we do if the website is lost or completely broken?" A disaster recovery plan doesn't have to be complex, but it must exist and be tested.
Scenarios to Prepare For
- Server destroyed or hosting provider goes bankrupt — website and data lost. Off-site backups are the only savior.
- Ransomware attack — data encrypted and ransom demanded. Without backups, the options are paying (not recommended) or losing data.
- Human error — a bad update, an accidentally deleted database, broken configuration. This is the most common cause, and it often happens during the busiest hours.
- Security incident — website compromised and must be cleaned from scratch.
The One-Page Document You Must Have
Create a simple recovery plan document containing:
- Emergency contacts — who to call first (internal and vendor).
- Backup location — where backups are stored and how to retrieve them.
- Recovery procedure — step by step to restore the website from backup.
- Who is responsible — one name, not "the team."
- Recovery time objective (RTO) — maximum hours until the website must be back online.
- List of parties to notify — customers, banks, payment gateway, ad providers.
This document should be stored somewhere that won't disappear along with the website—printed out or saved in separate cloud storage.
Recovery Drills
Theory isn't enough. At least once a year, run a recovery drill: restore the website from backup into a test environment and confirm it works. A team that has practiced can recover in hours; a team that has never practiced can take days—and every hour of downtime costs money and reputation.
FAQ: Common Maintenance Questions
"My website was built 3 years ago and never maintained. Can it still be saved?"
Mostly yes, as long as backups or at least the source code still exist. The process: a full audit (security, performance, compatibility), staged updates to supported versions, and cleanup. Costs can approach rebuild costs if the technology is very outdated—that's why, before deciding, ask for two options: repair cost and rebuild cost. Compare both honestly.
"Is maintenance mandatory? Small businesses don't have the budget."
Maintenance doesn't have to be expensive. For a simple profile website, a basic plan of Rp 150–300 thousand per month already covers backups, security updates, and monitoring. Compare that with the risk: a hacked or down website can lose customers worth far more. Think of maintenance as insurance—you hope you never need it, but you sleep better because it exists.
"I can update content myself. Why do I still need maintenance?"
Content updates are just one small part of care. Security, backups, monitoring, and performance optimization are invisible to visitors, but they determine whether your website stays alive and healthy. A website with regularly updated content but neglected security is an easy target for hackers.
"What's the difference between maintenance and feature development?"
Maintenance keeps the system running: updates, backups, bug fixes, optimization. Feature development adds new capabilities: new pages, new integrations, new modules. They have different scopes and are usually billed differently. Make sure your contract defines the boundary between them, so there are no surprises when you request changes.
"How do I check whether my maintenance provider actually works?"
Ask for verifiable periodic reports: backup evidence (date and size), update logs, uptime monitoring results, and work records. A good provider doesn't mind showing evidence—it's part of their selling point. You can also check yourself: when was the website last updated, does the SSL still apply, and does the page load fast?
Conclusion: A Healthy Website Is the Result of Routine Care
A website isn't a project that's "done" and then forgotten. It's a living asset whose value is determined by care: maintained security, tested backups, monitored performance, and fresh content. A well-maintained website is a marketing machine working 24 hours a day; a neglected one is a reputational time bomb.
Start with a simple audit: when was your website last backed up, updated, and speed-tested? If the answer is "I don't remember," that's your starting point. Whether managed in-house or outsourced, what matters is that maintenance becomes a scheduled routine with a clear owner—not "whenever we get around to it."
The Kartech. team in Bandar Lampung provides maintenance and evolution services for websites and applications—from uptime monitoring, tested backups, and security updates to advanced feature development after launch. See our services page or discuss your needs via our contact page and WhatsApp 0899-6293-888. We believe a healthy website is an investment that keeps working for your business.