Website maintenance services that keep everyday work moving.
A website can look finished while the work behind it keeps changing. Software releases arrive, documents expire, and contact details need an edit. WebXd helps organize that ongoing care around the site you have, with an agreed schedule, useful checks, and a record of what changed. Your team gets a clearer way to keep the website usable.
Give every recurring responsibility a name.
Start with the accounts and components that keep the website working. We review the platform, hosting, domain, extensions, and connected services within the agreed scope. The register records who controls each account, which renewals matter, and where a technical dependency needs attention. Access is shared through an agreed secure method rather than pasted into a support ticket.
An inherited site may have missing source files or an extension that its vendor has stopped supporting. Those findings belong in the opening review. We separate initial repairs from recurring care so the maintenance plan starts with a realistic view of what can be maintained and what needs a different decision.
- Account owner and renewal contact
- Supported software and known customizations
- Important forms, pages, and connected services
- Approval owner and route for urgent issues
Put the work on a calendar that fits the site.
A brochure site and a busy publishing site need different routines. The calendar pairs each task with an owner, a review interval, and the evidence expected when it is done. Backup frequency and retention reflect how much information changes and the recovery needs you agree to. A monthly report can summarize work even when individual tasks run more often.
Scheduled care also needs a route for exceptions. A relevant vendor advisory or a broken customer journey may require assessment before the next routine review. We define how that assessment reaches the right person and who can authorize a change. Security investigation and incident response require their own agreed scope.
| When | Care task | Keep this evidence |
|---|---|---|
| At intake | Inventory accounts and dependencies | Owner, access route, known limits |
| At the agreed interval | Review updates and routine checks | Assessment, findings, next action |
| Before and after a change | Confirm recovery options; test affected journeys | Backup reference and check results |
| At the review meeting | Reconcile requests and upcoming renewals | Completed work, open items, owners |
An update is complete when the affected task still works.
Consider a routine update to the component behind an inquiry form. The change record names the installed and proposed versions, the reason for updating, and the pages that use it. We assess release notes and compatibility before choosing the deployment approach. A separate test environment is useful where available, especially when the change affects custom behavior.
The checks follow the visitor’s task. Capture how the form behaves before the update, then repeat the agreed test after the change. Confirm required fields, the confirmation screen, and receipt at the expected destination. Use test details that can be identified and removed. Record anything left unresolved rather than treating a successful installation message as the whole result.
- Request
- Update the inquiry form component
- Before
- Capture field behavior and a test receipt
- Decision
- Test the candidate release before live approval
- After
- Repeat the journey on desktop and phone
- Record
- Version, approval, check evidence, open issues
Keep the restore evidence beside the backup record.
A backup record should explain what was saved and where it can be retrieved. For a typical WordPress site, the database and site files are separate parts of a complete backup. We review the agreed coverage against the site’s actual setup. Content stored in another system needs its own recovery arrangements.
A restore exercise provides evidence beyond a completed backup job. Where included in scope, restore an agreed backup into a separate environment and check the selected pages and functions. Record the backup date, the environment, and any missing content or dependencies. This shows what was verified in that exercise; it does not guarantee every future recovery.
Before a live restore, consider what has changed since the backup. New inquiries, orders, or published content may need to be preserved or reconciled separately. Recovery decisions should involve the person responsible for that information, with the limits and expected disruption understood before work begins.
- Coverage: files, data, and external dependencies
- Retrieval: storage location, retention, and access
- Exercise: selected backup, restore destination, checks
- Decision: recent changes and recovery authority
Give a small edit enough context to finish it.
Changing opening hours sounds simple until the old hours remain in a footer or downloadable guide. A useful content request identifies the source of truth, affected locations, approved wording, and desired publishing date. We check the agreed pages after publishing and return a record of the edit. Your team remains responsible for approving the business information.
The maintenance agreement defines which edits belong in routine care. Replacing a document or correcting a link is different from introducing a new page layout or rebuilding an integration. Requests that exceed the agreed allowance or complexity get a separate scope before implementation. That keeps the queue understandable as the site’s needs change.
Choose CMS support for a publishing or platform problem. Add security and monitoring for observation and response coordination. Use website training when your team needs to learn the task it will own.
Questions that define a useful maintenance plan.
A maintenance proposal should make the recurring work easy to understand. Ask which systems are covered, how requests enter the queue, what evidence you receive, and when an item needs a separate estimate. These details matter more than a long list of tools.
What do website maintenance services include?
The scope can include a site inventory, software update assessment, backups, agreed functional checks, small content edits, and a change record. Coverage depends on the platform and access available. We specify the tasks and responsibilities in the proposal, including work performed by your host or another provider.
How much does website maintenance cost?
Cost depends on the site's dependencies, custom code, important journeys, and volume of content requests. Initial repairs, licenses, hosting, and larger changes may need separate budgeting. Share the site URL and the work that tends to accumulate so we can define a scope and estimate around those needs.
Can you maintain a website someone else built?
We can review an existing site to assess fit before agreeing to ongoing care. The review looks at access, available source files, software support, and known issues. If a dependency cannot be updated safely or essential access is missing, we explain the preparatory work or limits before setting the recurring scope.
Does maintenance include hosting or constant monitoring?
Hosting responsibilities and monitoring coverage are defined separately in the agreement. Routine maintenance does not establish continuous observation or an uptime guarantee. If alerts and incident handling are needed, discuss the security and monitoring scope alongside the care calendar, including who receives and acts on a signal.
What happens when an update causes a problem?
The change record should include recovery options and the person authorized to use them. We investigate the affected behavior and decide whether to correct, pause, or reverse the change within the agreed scope. Restoring older data can affect newer information, so the recovery decision considers both the technical issue and business activity.