Website management is the recurring work that keeps a live site secure, current, fast, and editable after launch day. It is not a redesign sold by the month. Atlantic.Net’s managed-services explainer lists the usual bag: hosting, maintenance, performance, backups, security monitoring, updates, support, and troubleshooting. If you have no one on staff who will log into WordPress on a Tuesday, you need that bag owned. If you already have a developer who ships updates, you need a checklist, not a retainer speech.
What the phrase covers (and what vendors sneak in)
Atlantic.Net describes managed website services as outsourcing the technical tasks so owners can write content and run the business. Their include-list is hosting, plugin and software updates, security monitoring and response, backup and recovery, performance, SEO hygiene, analytics, content changes, ecommerce catalog work, and support. That list is useful because it is long. A vendor who says “fully managed” and means “we rent you a server” is using the same words for a smaller job.
I would split the list in two. Care: core and plugin updates, backups you can restore, uptime checks, SSL, malware, form tests, and content edits. Projects: redesigns, migrations, new integrations, and SEO retainers. OuterBox-style agencies (retainers vs a la carte vs hybrid) make the same split because stuffing a homepage rebuild into “unlimited updates” blows up the month for both sides. Website care is the care column. A rebuild is a redesign.
Content management belongs in care when you need a page published without waiting on a freelancer who has gone quiet. It does not belong in care when the request is a new information architecture. One is an edit. The other is a project. Vendors blur them because projects bill better.
Why a live site rots without an owner
Atlantic.Net cites a Forbes Advisor figure of 1.13 billion websites online, which is a cute way of saying most of them are unmaintained. Plugins update. PHP versions move. Browsers change. Payment rules shift. A site that was fine at launch picks up silent breakage: a form that never arrives, a checkout script that failed after a plugin bump, a backup nobody has ever restored.
Their backup note is the one I would steal. Daily backups are the minimum for production. Ecommerce may need hourly snapshots. The 3-2-1 rule they recommend is three copies, two kinds of media, one off-site. A backup that has never been restored is a file you hope is a backup. Ask for a restore test in the first month of a plan. If the vendor cannot do it, you bought a checkbox.
Security is the other rot. Unpatched WordPress plugins are the usual hole. Staging updates before production is the usual fix. We have walked into sites where a developer skipped accessibility and cookie work, then the business got a legal letter. Management that includes those checks is cheaper than the letter. Management that is “we update when you email” is a ticket mill with a nicer name.
What it costs, and who should buy it
GoDaddy’s 2026 cost guide (the same one we used for build pricing) tells businesses to budget up to $500 or more a year for maintenance, with ecommerce higher because of payment and inventory. That is the cheap published floor, and it assumes a simple site. Alliance Interactive’s management page, in our earlier fingerprint of that SERP, floated $500 to $2,000 a year for some packages and used downtime scare math I will not repeat because I did not verify their downtime dollars. Price a plan against a written include-list, not against fear.
I would buy a monthly plan if content, security, and uptime have no owner. Established small businesses with no tech staff should treat care as default after a build, which is the point of web development for small business. I would not buy a plan for two copy changes a year. A la carte is cheaper. I would not buy a plan that bundles ads, “unlimited pages,” or a redesign. That is a marketing retainer wearing a maintenance hat.
The concession: a good plan feels like paying for months where nothing broke. That is the point. You are paying for the month something would have broken and nobody was watching.
How to tell a real plan from a ticket mill
Ask what is in the monthly number. Ask what is a change order. Ask who you talk to (a named person beats a rotating queue). Ask whether updates go through staging. Ask who owns the hosting account. If the vendor holds the domain and the codebase hostage, keep walking. You should own both.
Atlantic.Net’s buying checklist is expertise, range of services, flexibility, security, support, and value over sticker price. Fine. Add one: they will tell you when you do not need them. We will say a stock host and a plugin set already cover you. Most operators do not have time for a pitch that sells them a platform they will use 10 to 20 percent of. Website management should be the slice that matches the site you have, not a suite with forty unused reports.
If the site itself is the problem (traffic with no inquiries, a DIY builder that never indexed), management will not save it. Fix the site, then put care on it. Management is what you do after the thing works, so it keeps working.
One more ownership test: who gets the hosting bill. If the plan includes hosting, confirm you can leave with a copy of the site, the database, and the domain auth code. A low monthly number that hides a lock-in fee at cancellation is not cheap. We do not hold sites hostage. You should not sign with anyone who needs to. Non-technical staff can still run a serious site if the agency hides the complexity behind a CMS a person can edit. That is the job. A plan that requires you to learn staging, SSH, and plugin changelogs is a plan you will ignore, which is how the next outage happens.