Keep an education website secure, current and reliable

Your guide to making the right decision

What to consider before starting your project

School website maintenance protects the everyday tasks that families and staff depend on. A working homepage is not enough if the enquiry form fails, a notice is out of date or a software update breaks a page. Support should cover agreed technical checks and a clear process for reporting problems.

We define maintenance responsibilities around the site's platform, hosting, integrations and publishing needs. The scope can include backups, update checks, form tests and content support, with response times agreed in writing. Backup availability and recovery testing are different checks; a useful service explains both rather than assuming a stored copy is sufficient.

Design around your audience

This work serves school web coordinators, communications staff, IT owners and families using the site. Their questions vary by decision stage, location and the information they already have. We organize the content and next steps around those differences, so people can find the right route without being pushed into an unsuitable enquiry or application.

Understand your starting point

Our initial review aims to prevent broken forms, outdated notices and security regressions. We examine an existing visitor journey with your team, including the information available, the point where a visitor takes action and the staff response. Recent questions and incomplete enquiries can help identify where a practical change is needed.

The review draws on backups, update logs, incident procedures and access ownership. Your team confirms the academic and operational facts, while we identify the website, content or marketing changes within the proposed scope. Depending on the agreed scope, planning can include an SLA checklist for uptime alerts, backups and scheduled updates. Access requirements, dependencies and any further approvals are agreed before implementation.

Agree on scope, ownership and handover

The proposal should describe the agreed deliverables, review stages and handover. The agreed planning documents give both teams a shared basis for reviewing the work. We clarify the information and access needed from your team, who approves the work, and which ongoing updates are included or separately scoped.

One risk to address is treating a maintenance contract as just plugin upgrades. The scope should explain how this will be checked and who is responsible for corrections. Your team should also know which activities depend on its systems or approvals, and which outcomes a service provider can measure without promising results it cannot control.

How to measure progress

Useful measures include resolution time and task availability. We agree the definitions and available data before reporting progress. Activity measures such as impressions, visits and form submissions help explain the journey, but they need context from the institution before they can be treated as successful admissions or commercial outcomes.

Reporting should connect observed changes with a practical next decision. Compare equivalent periods and account for intake dates, course availability and changes in follow-up. Where the systems cannot reliably measure resolution time and task availability, the report should identify the gap and the next measurement step rather than present an unsupported conclusion.

What to ask a potential digital partner

1. Can you show relevant work or explain how you would evaluate this project before recommending an approach?
2. How will subject-matter and admissions staff review claims before publication?
3. What are the acceptance criteria, maintenance responsibilities and escalation routes?

Official resources and references

• Google Search Central: creating helpful, reliable, people-first content
• Google Search Central: organization structured data
• US Federal Trade Commission: COPPA guidance, including school contexts

Prepare for a useful project discussion

Bring your current website or campaign example, the main question you want to resolve and any relevant information about backups, update logs, incident procedures and access ownership. A short, specific brief is enough to begin. Do not send student records, passwords or other sensitive information through a public enquiry form.

Before implementation, agree who reviews the planning documents and how changes will be approved. The handover should identify the owner, the approved version and the checks used to accept it. This keeps future corrections and routine updates manageable after the project is complete.