WordPress Support Plan: 12 Questions to Ask Before You Sign

A WordPress support plan should make responsibilities clear before the website needs urgent help. Similar monthly prices can hide major differences in monitoring, testing, response and recovery.

1. What is checked automatically and manually?

Uptime tools are useful, but forms, checkout and integrations often need real functional tests.

2. How are updates tested?

Ask whether changes use staging, backups and rollback. Critical security fixes also need a process for prompt release.

3. Where are backups stored?

Copies should be separate from the live server, retained for an agreed period and tested through restoration.

4. What security work is included?

Clarify monitoring, account review, malware response and cleanup. No supplier can promise a website will never be attacked.

5. What counts as an emergency?

Define downtime, broken transactions and security incidents, plus the channel and hours for reporting them.

6. What are response and resolution targets?

A response acknowledges the issue; resolution fixes it. Understand both and whether targets differ by severity.

7. Are content changes included?

Ask what qualifies, how requests are submitted and whether unused time carries forward.

8. Who owns hosting and licences?

The business should understand renewals, access and what transfers if support ends.

9. Are performance checks included?

A WordPress support plan may monitor speed or only availability. Define important pages and thresholds.

10. How are changes documented?

Reports should record updates, tests, incidents and recommendations in language the business can use.

11. What is excluded?

New features, third-party failures, hacked-site recovery or out-of-hours work may be separate. Clear exclusions prevent surprises.

12. How can the agreement end?

Confirm notice, handover, access and data arrangements. Avoid support that traps the website in accounts the business cannot control.

Match support to risk

A brochure site and busy ecommerce store should not use identical arrangements. Assess downtime cost, data sensitivity, internal skill and required recovery time.

Compare our guides to maintenance costs and maintenance risks. The WordPress documentation also provides official security-hardening guidance.

Choose clarity over reassurance

A good WordPress support plan explains what happens on an ordinary month and a difficult one. Olli Hopkins Digital can review the current website and recommend an appropriate level of care.

Is an unlimited support plan really unlimited?

Usually there are fair-use rules, task-size limits or exclusions. Ask for examples of requests that qualify and those treated as projects. “Unlimited” should not replace a clear service description.

Should the plan include development time?

Routine content edits and small fixes may be included, while new templates and integrations are quoted separately. A small monthly improvement allowance can help the site evolve, provided priorities and unused capacity are transparent.

What access should the business retain?

Keep control of the domain, hosting account, WordPress administrator access, analytics and paid licences where practical. Use individual accounts rather than shared passwords. Document how access will be handed to a replacement provider.

How do you review the provider?

Check incidents, response, completed preventative work and improvements every six months. A quiet period may mean the plan is working, but reporting should still show what was monitored and tested. A WordPress support plan earns its value through preparedness and continuity, not only visible tickets.

A practical way to apply this guide

Set aside 45 minutes with one colleague and review the current situation against the advice above. Write down what is working, what is uncertain and the single issue most likely to affect a customer. Gather one piece of evidence for each conclusion rather than relying only on preference.

Turn the discussion into three actions: one quick correction, one improvement that needs planning and one question requiring further research. Give every action an owner and date. This small exercise makes WordPress support plan a business decision rather than another article saved for later. Review the result after four weeks and record what changed for customers, staff or performance. If nothing moved, check whether the action addressed the real problem or only the easiest visible symptom.