Skip to the main content

6 min readPublished Last updated

What Is a Website Care Plan, and What's In It?

Written by UXPro Design Studio. Kitchener, ON. Prepared with AI assistance and checked against the sources listed below.

What is a website care plan and what does it include?

A website care plan is a monthly service in which someone is accountable for keeping your site online, secure, current and still delivering enquiries: hosting and DNS oversight, software and security updates, tested backups, uptime monitoring, a stated allowance of content edits, and regular checks that your forms still work. It differs from hosting, which only keeps the site online, and from basic maintenance, which keeps it technically working without anyone checking that it still does its job for the business.

Example, not a client

Redlined example

A typical website care plan description
  1. Edits

    Struck: Unlimited edits. Inserted: One hour of content edits a month; new pages quoted separately.

  2. Support

    A stated response window for each plan, in business days, written into the plan.

  3. Backups

    Daily backups, kept off-site, with a scheduled test restore.

Invented from patterns that recur across many sites. No real business is depicted; any resemblance is the pattern, not the firm.
Key facts
HostingKeeps the site online: a server, not a service relationship
MaintenanceKeeps the site working: updates, backups, certificates, uptime checks
Care planMaintenance plus a person accountable for edits, lead delivery, reporting and, on some tiers, content
UXPro care plans (as of 15 October 2026)Essentials $250, Growth $650, Authority $1,200 CAD a month, plus HST; month-to-month, cancel any time
The test to applyA stated edit allowance, a stated support arrangement and a backup that has actually been restored

Maintenance vs care plan vs hosting: what is the difference?

These three get sold in the same sentence and sometimes on the same invoice line. They are layers, and each one includes the one below it.

Table · scrolls sideways

LayerWhat it coversWhat it does not coverTypical monthly cost
HostingThe server your site's files live on; the site stays reachable at your domainUpdates, backups, monitoring, content, anyone checking that anything worksOften a few dollars a month for shared hosting, or bundled into a builder subscription
MaintenanceHosting oversight plus software and security updates, backups, certificate renewal and uptime monitoringContent changes, lead-delivery checks, reporting, a person reviewing what happenedVaries widely by provider and by what is included
Care planMaintenance plus a stated edit allowance, a monthly check that forms still deliver, reporting and, on higher tiers, SEO and content workRedesigns, new builds and ad spend, which are separate projects or budgetsUXPro: $250, $650 or $1,200 CAD a month, plus HST

The practical test: ask whoever looks after your site who is notified if it goes down, when a backup was last restored, and who checks that the contact form still reaches an inbox. If the answers are vague, you most likely have hosting described as maintenance.

Why hosting alone is the risky option. A site can be perfectly hosted, loading and looking fine, while its form has stopped sending email after a routine change at the mail provider. Hosting does not check for that. Only a person, on a schedule, does.

Why maintenance is necessary but not sufficient. Maintenance keeps the site working the way it did last month. It does not ask whether last month's version was working for the business: whether the hours, prices and staff are current, or whether a new service needs a page.

What does a real care plan cover?

Table · scrolls sideways

What a real plan coversWhy it matters
Hosting and DNS oversightSomeone watches the accounts that keep your site reachable, not just the invoice
Security and dependency updatesComponents are patched on a schedule, and the site is checked afterwards
Certificate renewalLet's Encrypt's FAQ says its default certificates last 90 days and recommends renewing every 60; someone should notice if the automatic renewal fails
Uptime monitoringYou hear about an outage from an alert, not from a client
Backups, testedA backup nobody has restored is a hope, not a plan
A stated edit allowanceSmall text and photo changes happen without a separate invoice
Lead delivery checkedA real test submission confirms the form still reaches an inbox
ReportingA short note on what changed, what was updated and what was tested

On updates, WordPress's own updating guide says most sites apply minor and security core updates automatically, but major releases need someone to run them, with a backup taken first. Plugins, themes and the dependencies of a custom-built site need the same attention.

What are UXPro's care plans?

As a concrete example, here is what our three tiers include as of 15 October 2026. All are month-to-month, and you can cancel any time.

Table · scrolls sideways

PlanPriceIncludes
Essentials$250 CAD a month, plus HSTHosting and DNS oversight, security and dependency updates, uptime monitoring, backups, lead delivery kept working, 1 hour of content edits a month
Growth$650 CAD a month, plus HSTEverything in Essentials, 2 hours of edits, 1 SEO article a month, AI-search tuning (FAQs, structured data, llms.txt), Google Business Profile upkeep, quarterly reporting
Authority$1,200 CAD a month, plus HSTEverything in Growth, 4 hours of edits, 2 SEO articles a month, landing pages included, monthly reporting and a strategy call

Essentials and Growth come with email support, and Growth is answered ahead of Essentials. Authority is answered first, ahead of every other plan. Work outside a plan is quoted before we start it. HST applies at the rate for your province; the Canada Revenue Agency's rate page lists 13% for Ontario. None of the plans promises rankings, traffic or AI citations: the content tiers do the work and report on it, and the results are not ours to promise.

Whoever you choose, the question is whether their tiers map onto the coverage table above, not whether the number sounds fair.

What do care plans usually exclude?

Read the fine print, because this is where surprises happen. Most plans exclude:

  • A redesign, or new pages beyond the stated allowance.
  • Large catalogue or e-commerce data entry.
  • Third-party subscriptions such as booking systems, email and paid plugins.
  • Ad spend and ad management.
  • Recovery from a change made outside the plan, such as an unreviewed plugin.

Ask how a provider treats requests on the boundary. Swapping a hero photo is an edit; redesigning the hero section is a project. A provider who writes that line down in the plan is easier to work with than one who decides case by case.

Why do support arrangements matter?

Under the marketing language, a care plan is a promise about who answers when the site is down or the form stops sending. "We'll get to it" is not a support arrangement. Ask each provider what the arrangement is on each tier, what happens outside business hours for something genuinely urgent, and get the answer in writing before you need it.

How much this matters depends on the business. A law firm whose consultation bookings all run through the website loses more for every hour the form is broken than a daycare with a prominent phone number and a full waitlist.

Backups vs disaster recovery: what is the difference?

A backup is a copy of your site from a point in time. Disaster recovery is the tested process of getting that copy back into production after a hack, a bad update or an accidental deletion. The Canadian Centre for Cyber Security's backup guidance recommends testing recovery from backups on a routine basis, keeping an offline copy, and storing a copy off-site.

So ask three questions: where are the backups stored, how many weeks of history are kept, and when was one last restored? A backup on the same server as the live site protects against very little, and a history of only one night will not help when a bad change goes unnoticed for a week.

What people ask next

The questions this guide gets asked after it has been read. Each answer is on the page, so the FAQ markup and the visible text are the same words.

Hosting keeps the site online. Maintenance keeps it technically working: updates, backups, certificates and uptime checks. A care plan adds a person accountable for the site doing its job, with a stated edit allowance, a monthly check that forms still deliver, reporting and, on some tiers, ongoing content.

You need less of one, not none. A static site still sits on a host that can go down, a domain and certificate that can lapse, and a contact form that can stop delivering without anyone noticing. A light plan with monitoring, DNS oversight and a tested backup covers the failures a static site actually has.

A properly run plan hands you a clean exit: the domain in your name, hosting in your account or an easy transfer, and your content and code. Ask how you would leave before you sign. Our plans are month-to-month, and your code stays in your repository.

You should. Register the domain in your name or your business's name, on an account whose login you control, and make sure the code and content are yours to take elsewhere. A care plan is a service you can cancel; it should never be a lock on ownership.

Next step

What to do with this.

See the full inclusion table on care plans. For the ownership question in depth, read do you own your website? Planning a new site with a plan from day one? See website design and build.

Reviewed 15 October 2026 against the sources listed below.

What you get

We read your site by hand and reply with written findings.

No turnaround time is published yet. We would rather say nothing than publish a window we have not tested.

Written by

UXPro Design Studio

UXPro Design Studio · Kitchener, ON

Prepared with AI assistance and checked against the sources listed below.

Sources

Terms in this guide

Structured data, Care plan, HST — defined, with sources, in the glossary.

For AI agents

Read as Markdown — the same guide as plain text, served as text/markdown. The feed for every published guide is at /blog/rss.xml.