A website can look perfectly healthy while enquiries are failing to reach the inbox. The homepage loads, the menu works, and nobody has mentioned a problem. Meanwhile, a form notification is being rejected by the mail server. For a service business, these quiet faults may matter far more than an obvious broken image.
That is why I think of WordPress care as a continuing responsibility, rather than a monthly visit to the Updates screen. Software needs attention, certainly. So do backups, forms, hosting, content and the small changes that keep a site useful as the business develops.
A monthly care plan gives someone responsibility for those checks and a way to respond when they find something. The details should fit the website. A five-page information site, a booking system and an online shop have very different consequences when something stops working.
Backups are no use if you can’t restore the site
A backup is the starting point for recovery. It should contain the pieces needed to put the website back together, be recent enough to be useful, and be accessible when the normal site or hosting account is having trouble.
WordPress stores content and many settings in a database. Themes, plugins and uploaded media live in files. WordPress explains why both files and the database matter; saving one without the other may leave you with only part of the site.
The right backup frequency depends on what changes. If a brochure site is edited once or twice a month, a modest schedule may be enough. A shop taking orders daily needs more recent recovery points, because restoring yesterday’s copy could lose orders and customer information added since then. A care agreement should say what is backed up, how often, where copies are kept and how long they remain available.
There is a question worth asking your provider: Has anyone tested a restoration? Seeing a green “backup complete” notice tells you that a process ran. It does not prove the resulting copy contains everything or that someone knows how to use it. The UK’s National Cyber Security Centre advises checking that backups contain the necessary data and knowing how to restore it.
A full restoration does not need to happen on the live site every month. The recovery route does need to be understood and tested periodically. It helps to keep a copy separate from the account hosting the website, so that one account problem does not remove both the site and its means of recovery.
Updates need a check afterwards
WordPress, its theme and its plugins all receive updates. Some fix security issues; others address bugs or compatibility. The WordPress hardening guidance recommends keeping software current. Leaving an old version in place indefinitely is rarely a sensible maintenance strategy.
Installing an update is only part of the job. Before a significant change, I want a current backup and a sense of what that plugin or theme does on the site. Afterwards, I check the pages and functions most likely to have been affected. A successful update message cannot tell me whether the mobile menu still opens, a Divi layout has shifted, or a booking confirmation reaches the customer.
Some updates can run automatically. That can work well when the components are chosen carefully and someone watches for failures. Other changes deserve a manual review or a test away from the live site first, particularly where payments, bookings or a complex integration are involved. WordPress’s guidance on plugin and theme auto-updates also points to the importance of backups and a route back if something goes wrong.
In a care plan, I would want to know who decides which updates can run on their own, who checks the result, and who sorts out a problem. Those are more useful details than a monthly count of updated plugins.
Security needs someone to act on warnings
No provider can promise that a website will never be attacked. The software is one part of a wider picture that includes hosting, account access, passwords and the devices used to log in. Routine care can still reduce avoidable risks and help a business respond sooner.
That may involve reviewing security alerts, checking for unexpected administrator accounts, removing unused software, keeping login access sensible and noticing changes nobody intended to make. An alert is useful only when someone can judge whether it matters and do something about it. A dashboard full of warnings that nobody reads is a poor substitute for a person who knows the site.
The level of monitoring should match the business. An information site and a busy shop need different response arrangements. What matters in either case is knowing who receives alerts, what they will investigate and what happens if the issue needs work beyond the regular agreement.
Follow the enquiry all the way through
For many small businesses, the contact form is the most commercially important part of the website. A visitor may complete it successfully and see a reassuring confirmation, while the notification email never arrives. The owner sees a quiet week and assumes nobody got in touch.
Would you know if enquiries stopped arriving? A useful form test follows a real message from the website through to the destination inbox. It checks the confirmation shown to the visitor as well as the notification received by the business. My article on why contact forms lose good enquiries looks at the points where that journey can fail.
The same principle applies to other journeys. A dance school might need to know that a class booking appears in its calendar and that the customer receives the right message. A shop needs to know that an order can be placed and the transactional emails are sent. A simple service site may need only its form, telephone links and main enquiry buttons checked. There is little value in testing features the site does not use while overlooking the one it relies on.
Watch how the site behaves for visitors
Uptime monitoring can tell someone when a site is unavailable. It cannot tell the whole story. A server may answer normally while an important page displays an error, a photograph disappears, a mobile menu becomes awkward, or a form sits broken halfway down the page.
A monthly visual check should include the pages that matter most to the business, on desktop and on a phone. I look for unexpected layout changes, missing content, certificate warnings, slow pages and obvious friction in the route towards an enquiry or booking. Automated tools help draw attention to changes; looking at the site as a visitor catches different problems.
Performance checks are most useful when they reveal a meaningful change. If a page suddenly feels slow after several large photographs were added, it is worth investigating. A small movement in a test score, with no noticeable change for visitors, may not deserve the same response. The care provider should be able to explain what changed and what is worth doing about it.
Monitoring can be proportionate too. A site taking bookings throughout the day may justify frequent availability checks and a quick response. A small brochure site may need less intensive monitoring. The aim is to catch problems that affect people and the business, then act on them.
Keep the information and design current
A site can be technically sound and still give a poor account of the business. Staff move on. Services change. Opening hours, prices and booking arrangements become outdated. An old call to action may lead visitors to a service that is no longer offered.
Someone familiar with the website can spot these things during routine care and raise them with the owner. The provider should not have to guess what the business now offers. The owner should not have to remember every page that needs an edit when something changes.
Some care plans cover only the technical work. Others include a certain amount of content editing, design refinement or support. Both can be reasonable arrangements if the scope is clear. Ask how small requests are handled, how quickly they are normally addressed and when a change becomes a separate project.
At BWSD, the managed website offer combines hosting and technical care with ongoing content updates and incremental design work. That matters to a business whose website needs to move with it. The precise work and time available should still be agreed for each project.
Know what the monthly fee covers
The phrase “care plan” does not have a standard list of inclusions. Before choosing one, ask the provider to spell out:
- Which parts of the site are backed up, where copies are stored, and how restoration is tested.
- How updates are handled and what is checked afterwards.
- Which forms, booking steps or purchase journeys are tested.
- Who receives alerts and deals with a problem.
- Whether hosting, licences and minor content changes are included.
- What response to expect when something urgent happens.
- Who controls the domain, hosting account and WordPress administrator access.
It should also be clear what requires a separate quote. A new section with substantial planning, a full redesign, extensive product entry, custom development or recovery from an existing compromise may be beyond routine care. Likewise, a monthly website agreement should not be mistaken for legal advice, formal accessibility certification or a guarantee against security incidents.
These boundaries protect the relationship. The owner knows what help is available, and the provider can give an honest answer when a request needs more time or a specialist. “Emergency support” deserves particular clarity: a promise to respond during working hours is different from round-the-clock cover.
A useful report explains what was found
A report that says “seven plugins updated” records activity. A short note saying the updates were applied, the enquiry form was tested and a layout problem was fixed tells the owner what happened to the website.
I would also expect a provider to flag something that needs the owner’s input: a service description that appears out of date, a booking journey whose wording is unclear, or a recurring warning that calls for separate work. Care is more useful when it leads to decisions, even small ones.
The value of an ongoing relationship is that the person doing this work knows the site’s design, hosting, plugins and purpose. They can spot when a change is harmless and when it affects the route a customer takes. The monthly checks provide a regular opportunity to apply that judgement.
If you have a WordPress site and are unsure what happens beyond occasional updates, I can help you look at the current arrangement and the gaps that matter for your business. If you would prefer one person to handle the design, upkeep and steady improvements, book a conversation with me and tell me what the site needs to do better.
Sources and further reading
- WordPress Developer Resources: Backups
- WordPress Developer Resources: Backing Up WordPress Files
- WordPress Developer Resources: Hardening WordPress
- WordPress documentation: Plugin and theme auto-updates
- National Cyber Security Centre: Backing up your data
Important note
This article provides general information and professional commentary. It is not advice tailored to your particular business, website or circumstances, and it should not be treated as legal, financial, privacy, accessibility, cybersecurity or other specialist advice. Any opinions are my own professional judgement based on the information available when the article was researched.
Products, prices, services, software and official guidance can change. External links are provided for reference; I do not control third-party websites and cannot guarantee their continuing availability, accuracy or content. A link does not imply endorsement of everything published by that source.
Check current official information before making an important decision. Test technical changes safely, keep a verified backup, and obtain appropriately qualified advice where the consequences warrant it. Any sponsorship, free product, affiliate link or other commercial relationship relevant to the article will be clearly disclosed.
That is why I think of WordPress care as a continuing responsibility, rather than a monthly visit to the Updates screen. Software needs attention, certainly. So do backups, forms, hosting, content and the small changes that keep a site useful as the business develops.
A monthly care plan gives someone responsibility for those checks and a way to respond when they find something. The details should fit the website. A five-page information site, a booking system and an online shop have very different consequences when something stops working.
Important note
This article provides general information and professional commentary. It is not advice tailored to your particular business, website or circumstances, and it should not be treated as legal, financial, privacy, accessibility, cybersecurity or other specialist advice. Any opinions are my own professional judgement based on the information available when the article was researched.
Products, prices, services, software and official guidance can change. External links are provided for reference; I do not control third-party websites and cannot guarantee their continuing availability, accuracy or content. A link does not imply endorsement of everything published by that source.
Check current official information before making an important decision. Test technical changes safely, keep a verified backup, and obtain appropriately qualified advice where the consequences warrant it. Any sponsorship, free product, affiliate link or other commercial relationship relevant to the article will be clearly disclosed.
