When a small business website is finished, the handover matters more than many people realise.
A lot of business owners focus on the design, the pages and the launch, but the real test comes afterward. Once the website is live, do you actually have what you need to own it, manage it and use it properly?
That is where website handover becomes important.
A proper handover should not leave the client guessing who controls the site, where the login details are, who owns the domain, or what happens if the developer disappears.
For a small business, the website should feel like an asset you control, not something you are locked out of.
Why website handover matters
A website handover is not just admin.
It affects things like:
- ownership
- access
- future updates
- hosting control
- backups
- support
- whether the website can be managed properly later
If a handover is unclear, the business can end up in a weak position. That might mean not having the right logins, not understanding where the website is hosted, not knowing how to update anything, or not even being sure who actually controls the domain.
Those problems are more common than they should be.
A finished website should not leave the client dependent by accident
Some businesses are happy to keep ongoing support with the person who built the site. That is fine.
But even if support continues, the handover should still be clear.
A small business should not be left in a position where:
- they do not know where the site is hosted
- they do not have access to the website
- they do not control the domain
- they are forced into hosting they did not understand
- they have no record of what plugins or systems are in use
- they cannot move the site later if needed
That is not good handover. That is confusion.
What a small business should receive at website handover
A proper website handover does not need to be overcomplicated, but it should cover the basics properly.
1. Website admin access
The client should receive access to the website itself.
For a WordPress website, that usually means an admin login to the WordPress dashboard.
For a Shopify website, that means the relevant store access and permissions.
The important thing is simple: the client should not be locked out of their own website.
2. Domain details or domain access
This is a big one.
The business should know:
- where the domain is registered
- who controls it
- how it can be accessed
- whether auto-renew is set up
- whether the domain is in the business owner’s name or account
A lot of confusion happens because the website is live, but the owner has no idea where the domain is actually held.
That is not a good position to be in.
3. Hosting details
If the website is hosted somewhere specific, the client should know:
- who the hosting provider is
- whether the hosting is in their name or the developer’s name
- what is included
- whether the hosting is optional or tied to a support plan
- how to access the hosting account if needed
Even if the client chooses not to manage hosting personally, they should still understand the arrangement clearly.
4. Confirmation of ownership
This should be clear.
The business owner should understand:
- whether they own the website
- whether they own the content
- whether they control the domain
- whether the site can be moved later if needed
- whether there are any third-party theme or plugin licences involved
This does not need to be written in legal language on the page, but it should be explained properly as part of the project handover.
5. Core login details
The client should receive the important login details or know exactly where they are stored.
That might include:
- website admin login
- hosting login
- domain registrar login
- email/SMTP login if relevant
- Shopify login
- key plugin or service logins if relevant
This should be organised sensibly, not passed over in a rushed email with bits missing.
6. A list of what has been built
A small business owner does not need a developer-level technical breakdown, but they should understand the basics of what they are receiving.
That can include:
- platform used
- key plugins or apps
- theme used
- what pages have been created
- forms or integrations that are in place
- anything custom or unusual that affects the site
This helps the site feel understandable rather than mysterious.
7. Backup arrangement
The client should know:
- whether backups are in place
- how often they happen
- where they are stored
- whether backup management is part of an ongoing support plan
A lot of business owners assume backups exist when they have never actually been explained.
That is something worth clearing up at handover.
8. Basic training or guidance
Not every client wants to manage the site personally, but most should be given at least a simple explanation of how to handle basic tasks.
That might include:
- how to log in
- how to edit basic text
- how to update images
- how to view form submissions
- who to contact if they need help
This can be very light, but some form of practical guidance is usually helpful.
9. Clarity on what is and is not included after launch
This is where misunderstandings often happen.
The client should know clearly:
- whether support is included after launch
- whether there is a warranty period for issues
- whether hosting includes updates or just hosting
- whether future edits are chargeable
- whether there is an optional care plan
This protects both sides.
A website handover should not leave the client assuming unlimited help is included forever if that was never agreed.
10. Contact details for future support
Even if the project is complete, it helps to know where support sits afterward.
The client should know:
- who to contact for help
- whether ongoing support is available
- whether hosting or maintenance is separate
- what kind of future work can be requested
That makes the transition after launch much smoother.
Common handover problems small businesses run into
A few problems come up regularly.
These include:
- not having the domain login
- not knowing where the website is hosted
- no admin access
- no backup clarity
- plugin or theme licences tied to someone else
- not understanding what is included after launch
- relying on one person with no documented access
- not having any training or guidance at all
These issues are avoidable, but only if the handover is handled properly.
Why this matters even if the business wants ongoing support
Some people are happy for the person who built the site to keep hosting it, updating it and helping with future work.
That is completely fine.
But ongoing support should come from clarity, not dependency.
A good handover can still happen even when the client stays with the same provider for hosting, maintenance and updates.
In fact, that usually builds more trust.
WordPress website handover: extra things worth checking
For WordPress websites in particular, handover should often include clarity on:
- the active theme
- key plugins
- whether plugin licences are client-owned or provider-owned
- how updates are handled
- whether a staging site exists
- how forms and email sending are configured
This matters because WordPress sites can become awkward later if the client has no idea what the site depends on.
Shopify website handover: extra things worth checking
For Shopify websites, handover should often include clarity on:
- store ownership
- staff access and permissions
- theme access
- apps in use
- app costs
- shipping and payment setup
- email capture tools
- any linked services such as Klaviyo or ShipStation
Again, the goal is not to overwhelm the client. It is to make sure they understand what they have.
A simple website handover checklist
If you want the short version, a small business should usually receive:
- website admin access
- domain access or domain details
- hosting details
- ownership clarity
- core login details
- summary of what has been built
- backup arrangement
- basic training or guidance
- clear post-launch support terms
- contact route for future help
If those things are covered, the handover is usually in a much better place.
What not to accept
A small business should be cautious if, after launch:
- they do not have access to their site
- they do not know where the domain is
- they do not know where the hosting is
- they are not clear on ownership
- they have no idea what happens next
- they have no records of logins or setup
That is usually a sign the handover has not been handled properly.
Final thoughts
A website handover should leave a small business feeling clear, informed and in control.
It does not need to be overly technical, but it should cover the basics properly so the website can be managed, supported and moved if needed in future.
The site itself matters, but the handover matters too.
If that part is messy, the business can end up with a website it uses but does not really control.
Need help with a website build, fix or handover?
I build and improve websites for small businesses with a practical, straightforward approach.
That includes:
- website design
- website fixes
- WordPress support
- Shopify support
- clear project handover
- ongoing website support where needed
If you need help with a website project and want a clearer, more sensible process, take a look at my website pricing or get in touch.
Need this done properly?
I work directly with small businesses on web design, WordPress fixes, Shopify support and local SEO. No agency overhead.
See web design in Blackburn →