Website maintenance so small changes do not become emergencies

Who this is for

You already have a site. Someone needs to update the platform, change a phone number, swap a seasonal banner, or check that the form still arrives. That person might be you, and you would rather not learn it during an outage. Maintenance is for owners who want that work named and scheduled, not for a project that has not launched yet. A new build includes a handoff. Care after the handoff is this service.

It fits WordPress and WooCommerce sites that need plugin and core updates. It also fits marketing sites on a modern host where the work is content edits, form checks, and dependency updates in the repo you own. Tell us the stack on the first call. We will not sell a WordPress care list for a site that has no WordPress admin.

What a care month includes

We agree a list, then we stick to it. A normal month can include:

• Platform or dependency updates applied on a copy first when the host allows it.
• A backup check. We do not call a plugin "installed" a backup. We want a file you could restore, and we test that once at the start.
• Small text and image swaps within a stated number of minutes. A new page or a new feature is a quote, not a quiet extra.
• A form or checkout click-through after updates that touch those paths.
• A short note of what changed, written in plain language, not a dump of version numbers with no meaning.

The published website packages include support days at launch: 14 days on the one page site, 30 days on the starter site, 45 on the business site, 60 on the pro site, and 90 on pro plus. Those windows are part of the build. This page is what happens after they end. Prices for care are quoted from the work, not invented as a universal monthly figure on this page. See pricing for the build ladder and ask us for a care quote that matches your stack.

How we run a change

1. You send the edit or we open the scheduled update window.
2. We make the change on staging when the platform has one.
3. We check the page on a phone, including the form if we touched it.
4. We publish and send the note the same day.
5. If an update breaks layout, we roll back using the backup we already proved, then we tell you what failed.

Urgent breaks jump the queue. A new landing page does not. That distinction keeps the care plan from becoming an unpaid redesign.

Problems we are hired to stop

The common failure is a year of skipped updates followed by a hacked WordPress login or a checkout that white-screens. We cannot promise a site will never be attacked. We can remove unused plugins, keep the ones you use current, and keep a restore point. Deeper hardening is security and backups.

Another failure is the "quick" edit that drifts the design. Five people with admin rights and no template rules will each invent a new button. Care includes edits inside the templates you already approved. If you want a new layout system, that is website redesign or web design.

A third failure is nobody watching the inbox. We can test that a form sends. We cannot sit in your inbox and reply to customers. Say who receives the mail, and we will use that address in the test.

A small worked example

A 10 page service site on the starter ladder ($150 to build) launches, and the support window ends. The next quarter needs a holiday hours change, two staff photos, one new testimonial you actually received, and two rounds of WordPress updates. That is care. It is not a reason to rebuild the 10 pages. If the same site later needs 10 more service pages, the build conversation moves toward the 20 page tier at $250, and care continues around it. The content checklist is what we still expect those new pages to pass.

Related services

Speed complaints during care often belong to speed optimization. A move to a new host belongs to website migration. Start care at contact.