Website maintenance should keep the agreed website usable, recoverable, and understandable to the people who operate it. The scope might include dependency updates, content changes, form checks, performance investigation, or incident support. A monthly label does not tell you which of those responsibilities an agency has accepted.
Start with the website's important tasks: a visitor finds a service, submits an inquiry, buys a product, or downloads a document. Ask who notices when each task stops working and who can fix it. This guide explains how to commission that ongoing work without treating support, new development, and search marketing as the same service.
Related service: Website development and agreed support- 01Report the affected task
- 02Assess impact and ownership
- 03Approve the proposed change
- 04Test in a suitable environment
- 05Release and confirm the task works
SECTION 01
Separate maintenance, small changes, and new projects
Inventory the platform, hosting, domain, forms, commerce provider, analytics, integrations, and paid extensions. Identify which accounts your business controls and which suppliers operate essential parts. An agency cannot promise to repair a third-party outage, but it can help detect the failure and manage the agreed fallback.
Then define the work classes. Updating a contact detail is different from adding a booking system. A dependency patch may need testing even when no visible feature changes. Ask how time is allocated, what requires separate approval, and what happens when a request exceeds the support scope.
| Workstream | Example deliverable | Boundary to agree |
|---|---|---|
| Technical upkeep | Reviewed updates and a tested deployment | Supported components and upgrade limits |
| Content edits | Approved text or image changes | Who supplies content and how reviews work |
| Functional checks | Evidence that a form reaches its destination | Test frequency and connected systems |
| Incident support | Triage, recovery steps, and a status update | Coverage hours and escalation route |
| New functionality | A separately scoped feature or integration | Estimate, acceptance, and release approval |
SECTION 02
Example: a working page with a broken inquiry handoff
Imagine a service website still returns a successful page while its lead destination rejects submissions after a credential change. This is an illustrative incident. An uptime monitor may report no problem, and a visitor may believe the inquiry was delivered unless the form checks the actual result.
A useful support scope includes a safe test submission, confirmation at the receiving system, and an owned failure alert. The support person identifies the broken connection, agrees a temporary contact route, restores access, and verifies delivery. Test entries should be labeled and removed through the agreed process so they do not become genuine sales leads.
The completion record should explain the affected period, what was recoverable, the change made, and how it was tested. Do not claim lost inquiries were recovered if no submission record exists. Add the failure to future checks so the same issue is easier to detect.
SECTION 03
Scope performance and analytics as measurable work
Website speed optimization starts with representative pages and actual symptoms. A large image, delayed server response, heavy script, or unstable layout needs a different fix. Google's Web Vitals guidance distinguishes loading, responsiveness, and visual stability, and explains why laboratory results are not a substitute for real-user data.
Ask the agency to record the baseline, investigate the cause, implement an agreed change, and retest comparable conditions. A performance score is not a promise that every visitor will get the same result. Third-party tools and the user's device can affect the experience.
For website analytics setup, define the business events before installing tags: a completed inquiry, an accepted checkout, or another agreed action. Test consent behavior, duplicate events, and whether the event represents completion rather than a button click. Keep private form contents out of analytics, and have the responsible business owner approve collection requirements.
SECTION 04
Protect search foundations when making routine changes
A content update can accidentally change a URL, remove an internal link, or hide useful text. A deployment can carry a preview-only indexing restriction into production. Include representative title, canonical, status-code, and sitemap checks in the release procedure when those areas change.
Google describes Search Console as a way to monitor how a website performs in Search and identify issues. Use it to inspect actual signals, not to promise that maintenance will recover a particular ranking. Ongoing keyword research, editorial work, and promotion need their own scope if you want them included.
SECTION 05
Agree access, recovery, and support evidence
Keep an account inventory and recovery contacts under business control. Ask which backups exist, what they include, and whether restoration has been tested. A code rollback may not reverse a database or content change, so the recovery plan should match the kind of release being made.
Catapult's post-launch work is agreed in the proposal. For U.S. or international teams, define time-zone coverage, the incident contact, and the difference between acknowledging a report and resolving it. Contact us for pricing based on the website and responsibilities involved; there is no universal maintenance scope.
SECTION 06
Frequently asked questions
Does website maintenance include SEO?
Only to the extent agreed. Maintaining crawlable pages, working URLs, and indexing settings differs from ongoing keyword research, new content, and promotion. List both scopes explicitly if you need them.
Does a support contract mean 24-hour coverage?
No. Confirm coverage hours, contact channels, response expectations, and escalation arrangements. Acknowledgment time and resolution time are separate commitments.
Can website support include analytics and speed improvements?
Yes, if the proposal defines the events, pages, investigation, implementation, and verification included. Agree a baseline and test method instead of relying on an unexplained score or a count of installed tags.
PRIMARY REFERENCES
Sources and further reading
These references cover the standards, platforms, or published prices discussed in the guide. Worked examples and checklists are our editorial guidance.
- Web VitalsGoogle web.dev
- How to use Search ConsoleGoogle Search Central
EDITORIAL METHOD
About this guide
We use AI to assist with drafting and editing. Catapult AI Work is responsible for the published content. Examples illustrate possible approaches; they are not client case studies unless identified as such.
Budget examples are not Catapult package prices. Check linked provider pages for current fees and plan limits before making a purchase.
Read the editorial policy