A website monitor reports that everything is working. The homepage loads, the design looks right and the monthly hosting payment has gone through.
Yet none of that establishes whether a customer can submit an enquiry and have it reach your team.
For a service business, we would put a complete enquiry test ahead of chasing a perfect performance score. Both performance and availability matter, but a fast page with a broken contact process fails at the point where the business needs it most.
Define what the website needs to do
Begin with the customer journey. For a small consultancy, that could be reading a service page, checking the company's credentials and sending a message. For another business, it includes booking an appointment or paying online.
Maintenance should cover those actions as well as the server behind them. List the important journeys and assign responsibility for testing them.
That turns a vague promise to “look after the website” into work that can be checked.
Test the enquiry from the customer's screen to your inbox
Submit a realistic test enquiry from a phone. Confirm that required fields are clear, validation works and the visitor receives a useful confirmation.
Then check delivery to the mailbox the team actually monitors. A form displaying “message sent” does not prove the recipient received it. Delivery services, mailbox rules and spam controls all sit between the visitor and the person expected to respond.
Test again after changes to forms, hosting, email services or DNS. Use clear test messages and avoid collecting unnecessary personal information during routine checks.
An uptime check and a completed enquiry test answer different questions. A maintenance agreement should make room for both.
Every website has components to maintain
A WordPress website needs attention to its core software, themes and plugins. A site built with a modern framework has dependencies, build tools and hosting configuration to maintain. A hosted website builder leaves some responsibilities with the platform and others with the business.
Our technical preference is to keep the number of components proportionate to the job. A straightforward service website should not require a large stack of plugins just to display content and accept an enquiry.
That preference is not a reason to label every WordPress site insecure or every modern framework safe. Security comes from the architecture, access controls, maintenance and testing together.
Protect the accounts that control the site
The domain registrar, DNS service, hosting account and source repository can all affect your website. Access to those systems deserves the same attention as the website's own login screen.
Use individual accounts where supported, protect powerful access with MFA and retain business control of recovery arrangements. Record renewal responsibilities and ensure alerts reach someone who will act on them.
A website can have a valid HTTPS certificate and still have weak administrative access. The padlock does not assess who can change the pages or redirect the domain. The same account-control questions apply when changing IT support provider.
Make the recovery plan complete
A copy of the source code is useful, but it is not necessarily everything required to restore the service. Include content, uploaded files, configuration and any database used by the site.
Document the external connections too: forms, transactional email, booking tools and payment services. Keep secrets in appropriate secure storage rather than copying them into a general handover document.
Test restoration in a controlled environment and confirm that the important customer journeys work. Record the access and steps needed so recovery does not depend entirely on one person's memory.
Keep content changes separate from technical maintenance
A maintained website still needs accurate service information. Remove obsolete offers, update contact details and check that examples and qualifications remain current.
Agree which content changes are included in the monthly fee, how they are requested and how quickly they will be handled. A new booking integration or substantial redesign should have its own scope and quotation.
For search visibility, keep useful service pages easy to reach and resolve broken links or accidental indexing restrictions. Routine maintenance supports a usable website; it does not establish a guaranteed search position.
What should a maintenance agreement include?
Look for an explicit list covering technical updates, customer-journey testing, backup and restoration, monitoring, content allowances and support hours. Identify exclusions and ownership of the domain, content and accounts.
The strongest agreement is one you can assess against actual work. “Fully managed” is too vague unless the responsibilities underneath it are clear.
Need reliable website maintenance?
Montalex provides website design, hosting and ongoing maintenance. We can review the supportability of your existing site and quote for the technical work and ongoing updates it needs.
Tell us about your website