Quick answer: WordPress client training at handover should cover login and users, how to edit pages with the block editor (or their page builder), media uploads, menus, basic SEO fields, what not to touch, how updates and backups work, and how to request help. Keep the session short, record it, leave a one-page cheat sheet and create a user account with the right role (usually Editor, not Administrator). Good training prevents emergency calls and protects the site you just built.
Why handover training is part of the build
You can ship a beautiful theme and still leave the client afraid to change a phone number. Fear leads to one of two failure modes: the site never updates, or someone with Administrator access installs random plugins at midnight.
Training is cheaper than either outcome. It also sets expectations about what “support” means after launch. If you use Gutenberg, pair this session with a friendly pointer to how the block editor works so vocabulary matches what they see on screen.
Before the meeting: prepare the environment
- Create named logins for real people (no shared “marketing@” admin)
- Assign Editor for content staff; reserve Administrator for technical owners
- Remove placeholder content and lorem boxes that invite confusion
- Write a one-page PDF: login URL, who to call, what they can edit
- Set up a staging site bookmark if they have one
- Confirm backups are running and say so out loud
A WordPress site audit mindset helps: show them the health basics so Site Health warnings do not panic them later (Site Health screen).
Session agenda (60 to 90 minutes)
1. Dashboard orientation (10 minutes)
Show where Pages, Posts, Media and Users live. Hide or explain noisy widgets. If you customized dashboard widgets for them, demonstrate those first (dashboard widgets).
2. Editing a page safely (20 minutes)
Walk through:
- Opening a page
- Editing a heading and paragraph
- Adding an image with alt text
- Preview vs Update
- Revisions and how to restore an earlier version (revisions)
If they use blocks, stick to the blocks you enabled in the theme. If they still use Classic Editor by choice, train on that tool honestly (Classic Editor plugin). Do not train on five page builders “just in case.”
3. Media library hygiene (10 minutes)
- Upload size limits
- Cropping and naming files
- Not uploading 5MB phone photos for icons
- Replacing images without leaving broken links
4. Menus and the homepage (10 minutes)
Show Appearance > Menus (or the live preview path you use). Explain that deleting a page does not always remove the menu item. If the Customizer matters for their theme, cover only the controls they own (Customizer).
5. Blog workflow (optional, 10 minutes)
Categories vs tags, featured images, excerpts, and scheduling. Mention their SEO plugin fields briefly without turning the meeting into an SEO course (Yoast vs Rank Math style choices can be documented separately).
6. What not to touch (10 minutes)
Be explicit:
- Do not install plugins without asking
- Do not edit PHP or theme files
- Do not change permalinks
- Do not delete unknown users
- Do not ignore SSL warnings
Write it on the cheat sheet.
7. Updates, backups and security (10 minutes)
Explain who applies core, plugin and theme updates. Show that backups exist and how restore requests work. Clients sleep better when this is concrete. Point to the wider recovery idea in website disaster recovery without dumping jargon.
8. Support path (5 minutes)
How to send a request: screenshots, URL, what they tried. Expected response times. What counts as a change request vs a bug.
Recording and materials
- Record the Zoom/Meet session with permission
- Store the recording in their drive
- Leave the PDF cheat sheet in the same folder
- Add three “recipe” GIFs or short clips: update homepage text, add a team member, create a blog post
People forget live demos. Artifacts make training stick.
Role-based training
Owners need billing, domain, hosting and Administrator responsibilities.
Editors need content only.
SEO contractors may need Search Console and plugin access without full admin.
Do not train everyone in the same hour with the same login. Separate audiences when the firm is larger.
Common handover failures
- Training on staging while production differs
- Giving everyone Administrator “for convenience”
- No mention of spam comments or form floods
- Skipping mobile editing realities
- Promising “unlimited training” without a package boundary
Put training hours in the statement of work. Extra workshops can be billed cleanly.
Aftercare in the first 30 days
Schedule a 30-minute follow-up once they have tried real edits. That second session catches confusion while launch knowledge is fresh. Review the pages they changed; fix process gaps, not only bugs.
Sample cheat sheet outline
- Login URL and password reset path
- Who is allowed to publish
- How to update the homepage phone number
- How to add a team photo
- How to create a draft blog post
- What to do if the site looks broken (do not install plugins; contact support)
- Backup confirmation sentence (“Nightly backups kept for X days; ask us to restore”)
- Support email and expected reply window
One page. Large type. No essay.
Training for multilingual sites
If the site uses translation workflows, show which plugin screens they use, who approves translations and what not to edit in the default language by accident. Point developers at translation-ready practices so string changes do not break locales.
Measuring whether training worked
Two weeks later, check:
- Have they published without breaking layouts?
- Are emergency tickets down?
- Did anyone install a plugin anyway?
Adjust the cheat sheet based on real mistakes, not hypothetical ones.
FAQ
Should clients learn to update plugins?
Usually no. Technical owners or retainers should handle updates unless the client has an in-house developer.
What if they insist on a page builder?
Train on the builder you installed and document which modules are safe. Do not leave unused builders active.
Is a written manual enough without a call?
Rarely. People learn WordPress faster by doing one edit with you watching.
How technical should training get?
Only as technical as their role. Editors do not need FTP.
Hand over confidence, not just a login
WordPress client training is how your project keeps looking good after month two. Cover edits, limits, backups and support paths, leave artifacts, and follow up once. If you want builds that include a clear handover and editor-friendly blocks, see Turn visitors into customers.
