WordPress maintenance for businesses: the checks to plan

These services may concern the same website while covering different interventions. The contract should name the person responsible for each scope and specify who coordinates providers when an incident affects several components.

These two situations are fictional: they illustrate a diagnostic method and do not describe work carried out for Oryon clients. A symptom observed after a change is not sufficient to establish its cause.

First example: after an update, the form displays a confirmation, but the enquiry no longer arrives in the business tool. Record the versions before and after the update, the test time, the page, the action performed and the expected destination. With authorised access, have a test enquiry followed from the form to the receiving tool and the available logs examined. The diagnosis should distinguish a fault in the plugin, custom connector or receiving service before assigning the work. If the connector is involved, clarify whether the code correction is covered by the contract or needs a separate quote. Acceptance then consists of observing receipt of the enquiry and the expected fields in the business tool.

Second example: an internally developed plugin no longer produces the expected document after a PHP version change. Note the versions involved, the steps and the error message, then have the failure reproduced in a suitable staging environment with test data. Identify the failing component and check whether adapting it to that PHP version falls within the contract. A WordPress core update alone does not validate a correction to custom code. After the intervention, repeat document creation and check its content with the person who uses it.

For each case, the report should connect the symptom to the component examined, describe the chosen intervention and identify the delivered version. Record the result of the complete journey, the person who approves it and any reservations. A page displaying correctly does not prove that the expected business result has been achieved.

Request an inventory of WordPress core, the theme, plugins and custom adaptations. Associate each component with its use: form, booking, display or connection to another tool. This list helps explain dependencies and identify licences needed for updates.

Distinguish WordPress access from hosting and domain access. A previous provider may hold an essential account without appearing in the site administration. Clarify which access must be transferred and the rights each person needs, while retaining control of your company’s accounts.

WordPress documentation distinguishes files from the database: both are needed to restore a complete site. Ask what the backup covers, where it is stored and who can retrieve it if hosting becomes inaccessible. Adapt its frequency to the information you can accept having to reconstruct.

Plan a restoration in a separate environment. Check the resulting site: recent content, media, administration login and essential functions. Have the date, backup used, observed duration and difficulties recorded. This measurement describes a test; it does not promise the same duration for every future incident.

WordPress recommends keeping an installation up to date and having a backup before an upgrade. For your site, clarify the policy for core, plugins and theme: automatic updates, supervised operations, necessary tests and the person responsible for monitoring results.

Significant changes can be tried in staging before being applied publicly. Also plan a procedure for urgent security fixes so they do not wait until the next regular appointment. When a component is no longer maintained, request documented options and a separate scope for any replacement.

Define a short acceptance checklist suited to your activity and repeat it after a significant intervention. A home page that displays is not enough to validate a form or an external connection. For the relevant functions, also check receipt of the result in the mailbox or receiving tool.

Have updates, monitoring, backups, corrections and improvements distinguished. Adding a client area or rebuilding a custom plugin may require a new work package. Also check how licences, hosting and external providers’ interventions are included in the quote.

Ask how to report an outage, during which hours requests are handled and what an announced response time means: acknowledgement, diagnosis or restoration. These are different stages. The report should explain what was done, what remains open and which decisions are yours.

Gather the site address, observed symptoms, recent interventions and available documents. For a malfunction, identify the page, the steps to reproduce it and its effect on your activity. A precise example helps diagnosis more than a general assessment of speed or security.

Oryon’s WordPress service can start with an audit of the existing site, followed by an intervention plan and maintenance within a defined scope. During scoping, ask which documents, access and procedures will be handed over so someone else can take over the site later.