How to hand a client a website they can edit themselves

A bakery's new website goes live on a Tuesday. On Friday the owner wants to change the weekend bread special herself, so she logs in with the admin details you sent, drags a block to make room for a photo, and the whole top of the home page slides sideways on phones. She texts you a screenshot on Saturday morning with one word: help.

She did nothing wrong. She was handed the keys to the whole building when she only needed the key to the noticeboard.

A client can edit their own website safely when you decide three things before handover: which parts they change, a login that can only change those parts, and a short lesson with a one-page guide they keep. Get those right and the owner updates the special on Friday, and you hear about it only when she's pleased.

What should a client be able to edit themselves?

Start from what changes in the business, not from what the software allows. A bakery's prices, specials and opening hours change every few weeks. Its layout and menu structure shouldn't change at all without a conversation.

If you researched the business before you pitched, your notes already tell you what moves. The same research on local businesses to pitch that found their out-of-date menu is a list of what they'll want to update.

Let the client edit	Keep with you
Prices, specials and menus	Page layout and design
Opening hours and holiday notices	The main menu and page structure
Staff names and photos on the team page	Theme, add-ons and site settings
News posts or a simple blog	Contact forms and booking links
Photos in existing spots	Domain, hosting and email settings

Write the left column down and agree it with the client. It becomes the heart of the guide you leave them, and it tells them what to send you instead.

Which website setup makes client editing easy?

There's no single right tool. What matters is that the client can reach the words and photos on the left of that table without touching anything on the right.

• WordPress. It comes with built-in user roles, so you can give the owner a login that edits content but can't install add-ons or change the theme.
• A site builder. Most let you invite a client with limited editing rights. Check what a limited user can still move before you rely on it.
• A hand-built site or one your AI agent built. Add a small content editor for the few things that change, or keep editable text in a simple file the client can update. Keep the design itself out of reach.
• No editing at all. For some clients the honest answer is "send the change to me". A dentist who changes the website twice a year may prefer a care plan with small changes included over learning a login.

Ask the client which they want. Plenty of owners are relieved to hear they don't have to learn anything.

How do you set up a client login that can't break the site?

Give each person their own login, with the smallest set of powers that covers their edits.

WordPress is a good example because its rules are written down. Its documentation lists six built-in roles. An Administrator has access to every admin feature on the site. An Editor can publish and manage posts and pages, including other people's, but the extra admin powers, such as installing and updating plugins and themes, stay with Administrators on a single site. For most owners, Editor is the right everyday login.

Ownership is a separate question from everyday access. The business should own the main admin account, the domain and the hosting, and the website handover checklist sets that out account by account. The owner can hold the admin login in a safe place and use the editor login day to day, the way you'd keep the spare shop key in a drawer.

Then lock what you can. Many builders and themes let you fix sections in place so they can't be dragged, deleted or restyled. Set content areas to accept text and images only. If a page has a special layout, such as a price table, give the client a field to fill in rather than a blank canvas.

How do you show a client how to edit their site?

On a short call with the client's hands on the keyboard, not yours. Twenty minutes is usually enough.

1. Have them log in with their own editor login, on the device they'll really use.
2. Make three real edits together: change a price, add a holiday notice, swap a photo.
3. Let them preview each change before it goes live, and show them how to undo it.
4. Show them where the guide is and who to contact when something looks wrong.

Record the call if they agree, so they can watch it again in six months. Owners forget steps they only do twice a year, and a recording saves you both a call.

What goes in a one-page editing guide?

One page the owner can keep open on their phone:

• How to log in, with the address of the login page. Never the password itself.
• What you can change, the left column of the table, with the steps for each.
• What to send us instead, the right column, with how to ask.
• Photos. The size to use, and a reminder to write a short description for each image. The W3C, the group that sets web standards, explains in its images tutorial that this text is read aloud or shown as Braille for people who can't see the picture, and that it should carry the essential information the image shows. "Sourdough loaf, $9" helps; "IMG_4032" doesn't.
• Before you publish: preview on a phone.
• If something breaks: stop, don't try to fix it, send a screenshot.

Keep it in plain words. If a step needs a technical term, explain it once in brackets and move on.

What happens when the client breaks something?

Something will go wrong eventually, and it's rarely the client's fault. Agree the plan before it happens.

Keep backups and know how to restore the last good version. Say in writing who fixes a problem, how quickly, and whether it's covered by a care plan or charged. A client who knows a mistake can be undone edits more calmly and texts you less.

When you restore, you need to know which version was the good one. That's why it helps to run a website QA checklist before handover and write down the version you checked. If an AI agent built or changed the site, the same habit applies: review AI built website changes before a client sees them, so you know exactly what was handed over.

Where does client editing fit in the handover?

Near the end, after the site has passed its final check and before you close the project. Run through your website QA checklist, fix what needs fixing, then set up the editor login, run the short lesson and send the guide. Add the guide to the handover notes so it lives with the domain, hosting and account details.

The order matters. Hand over editing on a site that isn't finished and the first round of client edits lands on top of your last round of fixes, and nobody can tell which change broke what.

If you want to see how building, review and delivery fit together as one routine, how to build, review and deliver client websites walks through it. Whatever your AI agency uses, the rule stays simple: decide what the client edits, give them a login that edits only that, and show them once with their own hands on the keys.