The website is live, the invoice is settled, and somewhere in an email chain there is a password, a hosting renewal and a sentence beginning “you'll just need to”. This is how a perfectly respectable build acquires a second career as an emergency.
A useful handover leaves the client able to make ordinary changes, gives the developer enough evidence to fix the difficult ones and makes it obvious who owns the accounts. These twenty tools cover those jobs. You will need a small selection, chosen for the actual website.
Disclosure: ScopeSite Digital Studios owns and operates CAFMO, our number-one editorial pick for the ongoing improvement workflow. This list is based on documented capabilities checked on 19 November 2026. After our first pick, the tools are grouped by job and are not ranked against each other. CAFMO does not replace a password manager, backup system or development repository.
First, decide who is responsible
Before installing anything, record the business owner of the domain, hosting, website account and billing. Give the developer appropriate access through their own account, then document what the client can change safely and what needs help. A login stored in the former contractor's personal inbox is an ownership problem, however attractive the homepage looks.
For each tool below, ask who receives alerts, who pays, what happens if the relationship ends and how the business exports its records. The first item is our preferred improvement layer; the numbered order is not a deployment checklist.
Twenty tools for handover and ongoing care
1. CAFMO: turn findings into work the client understands
CAFMO gives selected-page findings a practical next step, with Beginner, Novice and Developer detail. The client can make an ordinary edit, or copy task guidance for the developer, then recheck after publication. Saved reports and findings keep the conversation attached to the page being discussed.
We place it first because the work continues after launch. It supports the owner becoming more independent while preserving a route to technical help. Changes still happen in the website's own editor or codebase; CAFMO does not manage WordPress plugin updates, deploy code or replace a tested backup.
2. GitHub: retain the development record
GitHub Issues can record bugs and work against the repository. For a coded website, keep the source, release history and reproducible problem description accessible to the agreed team. A client should know where their project lives before somebody goes on leave.
3. Playwright: repeat the important browser journeys
Playwright tests browser behaviour across Chromium, Firefox and WebKit. Use it for the journeys that would hurt if broken, such as starting an enquiry or opening a saved account. Keep test submissions away from real customer workflows.
4. Chrome DevTools: investigate the page in the browser
Chrome DevTools helps a developer inspect and diagnose a running page. It is useful for reproducing a reported fault and identifying its cause. An edit made only inside DevTools is temporary, so the real fix still needs publishing.
5. Lighthouse: establish repeatable quality checks
Lighthouse audits areas including performance, accessibility and SEO. Keep the test conditions with the result. A score without its page, device assumptions and date is a rather elaborate fridge magnet.
6. Google Search Console: preserve search ownership
Search Console supplies Google's query, performance and indexing reports. Ensure the business has its own verified access. Include the property and responsible account in the handover, without putting passwords in the document.
7. Bing Webmaster Tools: keep the second search account
Bing Webmaster Tools supports inspection and technical checks for Bing. Record its ownership alongside Google's. It is easier to transfer knowledge at handover than to reconstruct it during an indexing problem.
8. PageSpeed Insights: check the public release
PageSpeed Insights provides lab and, where available, real-user loading information. Use the public production URL after a change, and record whether the evidence is simulated or collected from users.
9. WAVE: add accessibility inspection
WAVE makes detected accessibility issues visible in their page context. Pair it with keyboard use and a human review of the actual task. Automated results are one part of the acceptance evidence.
10. Screaming Frog SEO Spider: check links and URLs
Screaming Frog crawls the website for technical inspection. It can help establish the URL and link picture before and after a migration. Keep the crawl settings, particularly when JavaScript rendering affects what can be found.
11. Sitebulb: explain a technical audit
Sitebulb offers explained Hints and audit comparisons. Use it when the handover includes a substantial technical backlog that needs discussion. Put the agreed actions into the team's working queue.
12. Sentry: collect application error evidence
Sentry provides JavaScript error tracking and performance diagnostics. It suits custom applications where the developer needs to understand failures after release. Configure data collection carefully and keep customer details out of unnecessary diagnostic payloads.
13. UptimeRobot: send availability alerts to an owner
UptimeRobot monitors website and endpoint availability. Give alerts to someone with responsibility to respond. An available homepage does not prove every form or checkout works, so monitor the important journeys separately.
14. Bitwarden: share access deliberately
Bitwarden supports business password management and controlled sharing. Use named access and a clear owner. Recovery arrangements deserve the same attention as the everyday login, especially when only one person normally handles the website.
15. MainWP: manage a WordPress portfolio you host
MainWP provides a self-hosted dashboard for managing multiple WordPress sites. It suits a team willing to operate that management layer. Document responsibility for the dashboard itself as well as the sites connected to it.
16. ManageWP: centralise WordPress maintenance
ManageWP brings WordPress site management into one dashboard. Consider it when maintaining several installations. The client agreement should say which maintenance tasks are included and how access changes at the end of the contract.
17. WP Umbrella: organise WordPress care plans
WP Umbrella combines updates, backups, monitoring and client reports for WordPress maintenance. It is an alternative to the preceding managers, not another compulsory subscription. A scheduled backup still needs an understood and tested recovery procedure.
18. Plausible: give the client readable traffic reporting
Plausible presents website analytics in a compact dashboard. Define the business events that matter before configuring reporting, then check that the measurements mean what their labels say. Page views alone do not establish the quality of enquiries.
19. Notion: write down how the website is run
Notion can hold a handover guide and linked operational notes. Include account owners, routine edits, support arrangements and recovery instructions. Keep credentials in the password manager and give each page a review date.
20. Cloudflare DNS: document the domain's routing
Cloudflare DNS manages records connecting a domain to services. It belongs here when the website already uses it or the architecture calls for it. Record what each important entry serves before altering anything that could affect the website or email.
The handover record worth keeping
For each important page or journey, keep its public address, purpose, owner, last accepted check and next action. Add the release reference for a coded site, or a dated change note for a managed builder. That gives the next person a useful starting point, even if they were nowhere near the original project.
A small brochure website might use CAFMO for improvements, a search account, an availability monitor and a short handover document. A custom application may also need source control, browser tests and error monitoring. A WordPress agency may choose one maintenance manager. Buying all twenty would defeat the exercise.
Create a CAFMO account if you want the ongoing page-improvement work in one place, then choose the monthly plan that fits the websites you are authorised to check. Agree who owns the CAFMO account and keeps access to its records, just as you would for the other tools. For the audit layer, see our ten website audit tool picks.
Frequently asked questions
Is CAFMO a replacement for a WordPress management tool?
No. CAFMO checks selected public pages, provides improvement guidance and saves evidence. WordPress management tools serve installation maintenance jobs such as updates and backups. Choose each for the job it actually performs.
Which accounts should the client own?
Agree ownership explicitly for the domain, hosting, website platform, source repository and reporting accounts. The business should understand its access and recovery route, with the developer granted the permissions needed for the agreed work.
Do we need automated browser tests for a small website?
Use them where repeating a critical journey would prevent costly mistakes. A simple informational site may need a smaller testing routine than an application handling accounts or payments. The scope should follow the risk and actual functionality.
How do we prove maintenance work was useful?
Record the problem, the change and a fresh check of the same page or journey. Report customer outcomes separately. A working form is evidence of a repaired journey; the number of useful enquiries needs its own measurement.
About this selection
Dan Cartwright, ScopeSite Digital Studios, Frome, Somerset. Supplier documentation is linked beside each tool. Check current plans and supported features before committing. The cover is an AI-created editorial illustration.




