
Who Maintains Your WordPress Website When Nobody Is Paid To?
Most small business WordPress sites have nobody responsible for them. What goes wrong in the first year, what maintenance involves, and how to make it a job.
Writing
20 write-ups from production, newest first. Each one is a problem hit on a real project and how it was diagnosed and fixed.

Most small business WordPress sites have nobody responsible for them. What goes wrong in the first year, what maintenance involves, and how to make it a job.

What a good website care plan does every month, what it should never include, how to spot a lock-in, and what a fair monthly price looks like.

The fifteen-minute monthly Search Console review we run for care plan clients: which reports, what counts as a problem, and what gets fixed at once.

A single calendar for every renewal your website depends on: what goes on it, how to build it in an hour, the fields that matter, and how it runs.

The line between edits a business owner should make on their own website and edits that go to the developer, why it is drawn there.

Which WordPress plugin updates most often break a site and why, how we stage and test each monthly round, and what is checked before updates go live.

A site that was fast at launch is slow a year later and nobody changed the design. The five ways performance drifts and what continuous monitoring looks like.

What a website security scan actually does, the problems it finds and the ones it misses, why a clean scan is not a secure site, and what else a care plan does.

What support response times mean from a small studio: what is answered in an hour, what waits until Monday, and what monitoring handles while nobody is awake.

Three anonymised small business websites left alone for years: what failed, what recovery cost, and what a care plan would have cost over the same period.

Why taking on maintenance of a website built by someone else starts with a paid review, what it checks, what it can rule out, and what happens to the fee.

The questions that reveal whether a maintenance plan is a service or a trap: who owns the accounts, what happens to backups and licences, notice, handover.

Uptime says the site is fine and the booking button has been broken for a fortnight. Why booking flows fail silently and how to monitor them properly.

What a good monthly website maintenance report should tell you: updates made, backups tested, uptime, speed, security and the decisions it asks of you.

How uptime monitoring works for a small business website, what to monitor beyond whether it is up, and how to know it is down before a customer does.

Why website updates should run on a staging copy before going live, what staging is, and how it prevents the broken-site emergencies we see most.

What counts as a small change under a care plan's included hours and what is a separate project, with examples and how we tell you which it is.

How daily website backups should work: where they are stored, how often they are tested, how long they are kept, and how a restore actually happens.

How to choose between Basic, Growth and Scale care plans by working out what an hour of your time costs and how often the site changes.

Care plan or hourly support for your website: a year of costs side by side, what each covers, and the point where a plan becomes cheaper.