Website handover checklist: help clients look after their own site
Hand over a website with clear ownership, safe editing guidance, SEO records and responsibilities. Help clients manage routine improvements confidently.

A good website handover gives the client appropriate ownership, clear editing guidance, a record of the current website and an agreed support boundary. The client should know what they can safely change, how to check the result and when to ask for help.
A folder called “Final final v7” and a password sent in a chat window is a rather modest interpretation of independence.
Confirm ownership and access
List the domain, hosting or website-builder account, content system and relevant analytics services. Record who owns each account, who pays for it and who can administer it. Use the services’ normal invitation and access controls, granting appropriate permissions.
Transfer credentials through an agreed secure method when necessary. Keep secrets out of the public handover document. Record recovery responsibilities and make sure the client can access the accounts they are expected to own.
Explain the website’s moving parts
Give the client a short map: where pages are edited, where forms deliver messages, where images live, and which integrations affect enquiries or orders. Include important renewal dates and dependencies in the agreed operational records.
For WordPress, identify the theme and important plugins. For a hosted builder, identify the account and relevant connected services. For a custom website, explain the normal content workflow and which changes require development work.
Teach a small number of repeatable edits
Demonstrate an ordinary task using the client’s actual website: amend service information, replace an image, add a useful FAQ or correct a contact detail. Let the client perform the task with guidance, then check the published page together.
- Explain the difference between draft, preview and published content.
- Show how headings organise a page.
- Explain meaningful image descriptions and sensible file preparation.
- Show how to add a relevant internal link.
- Demonstrate the available recovery or revision process.
Provide short instructions the client can find later. A two-minute recording of their actual editor can be more useful than an enormous manual covering features they will never touch.
Hand over the search and business records
Record important URLs, page purposes and the source of titles, descriptions and structured data. Confirm the approved business name, public address or service information, phone number and relevant profile links. Identify who updates these if the business changes.
Include a dated baseline of relevant search or website evidence, with clear limits. An absence of data at launch should be recorded honestly. A search submission is not proof of indexing, and a technically working page is not a guarantee of customers.
Agree the support boundary
State which routine changes the client owns, what ongoing maintenance covers and how new work is requested. Describe who investigates a failed form, an account-access problem or a plugin conflict. Keep response expectations consistent with the actual agreement.
This protects both parties. The client can make ordinary improvements without feeling that every comma is rented, and the developer has a clear basis for distinguishing maintenance from a new feature.
Finish with a real acceptance check
Ask the client to complete one agreed edit, publish it and verify the result. Confirm that the appropriate people receive a clearly labelled test enquiry. Check access to the operational records and record outstanding items with an owner.
Use the SEO action-plan format for remaining improvements. If ongoing reporting is part of the service, the client-reporting guide helps separate completed work from measured results.
Support the client’s improvement routine
CAFMO helps website owners inspect public pages and work through findings. It can support the client’s ongoing learning while their website stays in its existing platform. It does not replace account ownership, backups or your maintenance agreement.
Create a CAFMO account to explore the workflow for your own website, then decide how it fits your client handover process.
Frequently asked questions
Should a client receive full administrator access?
Agree ownership and responsibilities, then grant the appropriate access through each service’s normal controls. Different roles need different permissions; document who retains administrative responsibility.
What SEO information belongs in a handover?
Include important URLs, page purposes, metadata ownership, relevant search accounts, business details and a dated record of completed work. Explain how the client checks future changes.
Does client independence mean the developer stops supporting them?
No. Independence means the client understands routine tasks and the limits of their responsibility. An agreed support arrangement can cover maintenance, specialist changes and problems they cannot resolve.
Sources and further reading
- Google: getting started with Search Console
- Google: third-party SEO tools
- support.squarespace.com: SEO checklist
Reviewed 15 November 2026. Platform features can change; check the linked documentation for current controls.