Give clients a useful SEO handover
Bring the website plan, open issues and next steps together so a client knows what has been prepared, what needs approval and what happens after launch.
The last conversation matters, too
Sam has spent the previous lessons thinking through ClearFlow Plumbing's possible redesign.
He began with the owner's goals. Then he worked through the existing pages, service information, navigation, mobile experience, technical settings and what to check before a new version goes live. He also learned how to explain search and AI visibility without confusing them with actual customer inquiries.
Now he needs to make that work understandable to the person who asked for help.
Imagine ClearFlow's owner saying:
“This all sounds useful. What exactly have we got, and what happens next?”
Sam could send a long collection of notes. Or he could prepare one short handover that answers the important questions.
A good handover doesn't try to impress a client with SEO terminology. It helps them make the next decision.
Start with the client's goal, not your task list
ClearFlow's owner wants more relevant water heater repair inquiries from homeowners in Austin, while continuing to receive suitable drain cleaning inquiries.
Sam puts that goal at the top of the handover. It gives the rest of the plan a purpose.
For example, he can explain why the website should keep its dedicated water heater repair page, rather than replacing it with a generic services page. And he can explain why the inquiry form and phone link deserve careful testing.
The client doesn't need to remember which lesson introduced page structure or indexing. They need to understand how the decisions connect to the business.
Say what's ready, and what's still waiting
Sam has prepared a lot of useful work. But a prepared design is not the same as a published website.
He uses three simple labels:
- Prepared: The idea, page plan or draft is ready to review.
- Needs a decision: The owner or an authorized specialist must approve something, supply missing information or inspect an issue.
- To verify: The finished website will need a real test before an item can be called complete.
Those labels protect both the client and the designer. Nobody has to guess whether something was suggested, approved or actually tested.
For ClearFlow, the six existing page addresses are still the recommended structure. Sam has proposed clearer service copy and easier inquiry routes, but no redesign has been approved or published.
The water heater page also needs attention. An earlier review found a setting called noindex, which can prevent a page from appearing in Google Search. Sam needs a fresh check before anyone decides on a correction. He won't claim a new design has solved it.
Worked example: Sam's one-page handover
Sam creates a short document called ClearFlow Plumbing · Website redesign handover plan.
Purpose: Help Austin homeowners understand ClearFlow's two services and make an appropriate inquiry.
Project stage: Review of proposed work; publication has not been approved.
| Area | What Sam can show | What happens next |
|---|---|---|
| Website pages | A clear role for the homepage, the two service pages, the existing article, About and Contact. The six addresses can stay. | Review the plan with the owner; confirm that no URL change is needed. |
| Service content | Drafted headings and useful page content for water heater repair and drain cleaning. | Owner confirms service details and approves public wording. |
| Navigation and inquiry | A proposed link from the no-hot-water article to water heater repair, plus a clearer mobile contact layout. | Build and test the approved changes; check real form delivery and phone-link behavior. |
| Technical SEO | The earlier noindex finding on the water heater page is documented. | An authorized person rechecks it; obtain approval for any fix and verify afterward. |
| Measurement | September's starting-point figures and a plan for later checks. | Confirm tracking and report on comparable periods after a future launch. |
| AI visibility | A short explanation of what the website can improve and which Google AI report may be useful. | Check any available Google AI link-impression data separately from observations in other AI tools. |
Notice what Sam doesn't write: “Redesign finished,” “all problems fixed,” or “SEO traffic will increase.” Those statements would not describe the work's current stage.
The handover is useful precisely because the owner can see what needs attention before making a decision.
Give the next action a person and a check
A handover that says “SEO needs fixing” isn't very useful. The client still has to guess who will act and how they'll know it worked.
Sam makes the important next steps more specific:
| Next action | Who should take it | What will show it's done |
|---|---|---|
| Review service-page wording and business claims | ClearFlow owner | Approved copy is recorded for the final build. |
| Recheck the water heater page's indexing instruction | Authorized developer or site administrator | A dated inspection records the current setting; any correction has separate approval and a later verification. |
| Test mobile inquiry links and form delivery | Sam and the person responsible for the final build | The final website works on a phone, and a labeled test form reaches the intended recipient. |
| Approve publication and the release plan | ClearFlow owner and authorized website team | Scope, remaining issues, responsibilities and the publication decision are agreed. |
These are proposed responsibilities for the handover discussion. Sam still needs to agree the people and dates with ClearFlow before treating them as assigned work.
A simple way to remember this is: Action + person + evidence + review date.
A checklist becomes much more useful when the owner can see who is handling each item.
What happens after the website launches?
Sam also includes a short follow-up plan. It starts only if the owner approves the work and the redesigned website is actually published.
| When | What to check | What to record |
|---|---|---|
| Launch day | Visit all six live URLs; follow important links; test phone and form contact; check the agreed search settings and tracking. | Test date, result, unresolved issue and responsible person. |
| First week | Review indexing information and any newly discovered errors; follow up on important unresolved items. | What changed, what still needs attention and the next review date. |
| Weeks 2–4 | Look at relevant service-page search activity, organic sessions and confirmed inquiries as new information becomes available. | Comparable dates, data sources, observations and questions to investigate. |
This isn't a promise that Google will update everything in a week or that inquiries will increase in 30 days. It's a sensible way to make sure the website is monitored and problems don't get forgotten.
The follow-up also needs an agreed owner. For some projects Sam may perform the launch checks. For others the client, developer or an SEO specialist may handle them. The scope should be clear before publication.
Use the starting numbers correctly
Sam keeps the original September measurement note with the handover:
| Source and measurement | Value |
|---|---|
| Google Search Console page-report impressions | 5,240 |
| Google Search Console page-report clicks | 142 |
| Analytics organic search sessions | 127 |
| Confirmed inquiries from all sources | 4 |
These numbers don't describe one step-by-step sales funnel. In particular, the four confirmed inquiries cannot all be credited to Google Search.
When comparable information becomes available after a future launch, the client can review whether the right pages are being found, whether people can inquire and whether the business is receiving useful inquiries. A change in numbers doesn't, by itself, prove the redesign caused it.
Sam doesn't fill the handover with every metric he has ever seen. He chooses the ones that answer the owner's questions.
What about the client's AI question?
Sam also brings forward the note from Lesson 14.
He explains that the same foundations still matter: clear service information, useful pages, working links and appropriate indexing. Google's Generative AI performance report, when available, can show link impressions in AI Overviews and AI Mode. It doesn't measure all AI assistants.
That's enough for the handover. The client now knows what the website team can work on and what later evidence might tell them.
Be clear about where your job ends
Sam designs websites. He doesn't sell ongoing SEO management as part of Cedarline's normal offering.
So his handover makes a helpful distinction:
Website project work covers the agreed design, content preparation, build and release checks.
Ongoing SEO work may include reviewing search data, discovering new opportunities, maintaining important content, investigating technical issues and deciding what the site needs next.
A client might manage that work themselves, ask a specialist to do it, or use a strategy-led SEO platform such as Blue Kite SEO. Sam can explain those options without promising a particular result or selling a service he doesn't provide.
The important thing isn't which option the client chooses. It's that the client understands what will continue after launch and who will own it.
The conversation Sam is ready to have
Sam prepares a message to discuss the plan with ClearFlow's owner:
We've mapped out how the existing website pages can better explain water heater repair and drain cleaning, while making it easier for homeowners to get in touch. The proposed page structure keeps your current addresses, and the service content is ready for your review.
Before any launch, we need your approval of the wording and scope, a fresh check of the water heater page's indexing setting, and tests of the final contact routes. I've listed the next actions and who we'll need to involve. Once publication is approved, we can check the live website and use the September figures as a starting point for future reviews.
That's a professional handover. The client can understand it, ask questions and make an informed decision.
Now finish the plan for your own studio
Sam turns back to Cedarline Web Studio. The course began with his own website, so that's where the final activity returns.
He already has coordinated drafts for three pages:
- Homepage
/: Introduce Cedarline and the service businesses it helps. - Services
/services: Explain new websites, redesigns and optional website care. - Work
/work: Show selected design work with accurate explanations of Sam's contribution.
All three should help a visitor find the existing Contact /contact page when they're ready to discuss a project.
Sam chooses a realistic first set of actions:
- Review the three drafts together, keeping each page's purpose distinct.
- Test the
/contactinquiry form on the actual site and check that inquiries arrive. - Record a dated starting point for search activity and suitable inquiries, using the information available.
- Publish when the wording and technical checks are ready, then review comparable information later.
He doesn't need to launch a dozen new pages or promise himself a ranking target. He needs a website that makes sense to the right clients, a way for them to contact him, and a habit of checking what happens next.
One practical habit to keep
Whenever you finish a website project, ask yourself:
Could the client tell someone else what is ready, what needs doing, who owns it and what happens next?
If the answer is yes, your handover is doing its job.
Help Sam hand over the next steps
Choose a useful handover decision for each situation. You can change your answer to explore the reasoning.
What should the handover say?
Sam has prepared page and content drafts for ClearFlow. The owner hasn't approved publication, and the water heater indexing question still needs a current inspection.
Put your handover together
Use the ClearFlow story to write a short handover you could adapt for a real client. Keep it simple. Every field is optional, and you can come back to your answers later.
See Sam's completed example
- What stage is the project at?
- ClearFlow's redesign proposal and handover plan are prepared for discussion. Owner approval, a fresh technical inspection, implementation planning and final build tests still stand between the drafts and any authorized launch.
- What have you prepared?
- Keep /, /water-heater-repair, /drain-cleaning, /blog/no-hot-water-what-to-check, /about and /contact. Draft clearer service pages and titles, propose relevant navigation/internal links and a more usable mobile inquiry route, and preserve distinct page purposes.
- What needs attention next?
- Obtain owner-approved service wording and release scope. Recheck the October 20 noindex finding on /water-heater-repair; request separate approval if a correction is still needed. Check the final contact form, phone link, mobile layout and intended indexing/tracking settings before publication.
- Who will do it, and what proves it's done?
- Propose the owner reviews business claims and authorizes publication; an authorized developer or admin handles technical inspection and any separately approved fix; Sam coordinates design and inquiry-path tests within the agreed scope. Each item needs a named assignee, evidence of completion and a mutually agreed review date.
- What happens after launch?
- If a future launch is approved: on launch day open all six current URLs and test links, form delivery, phone link and intended search/tracking settings. In the first week check technical reports and open issues. In weeks 2–4 review comparable page search activity, organic sessions and the owner's confirmed inquiry records; record what changed and what remains unknown.
- What should the client know about measurement and AI?
- September baseline: 5,240 GSC page impressions, 142 GSC page clicks, 127 organic sessions and 4 confirmed inquiries from all sources. The four inquiries aren't attributed to Google. If available, review Google's AI Overviews/AI Mode link impressions within their proper scope. Keep other AI observations separate and record their source and date.
- Finish your own studio plan
- Review Cedarline's draft homepage, /services and /work copy together, keeping each page's purpose clear and linking sensibly to /contact. Test the actual contact form and mobile inquiry path. Record genuine studio search/inquiry readings when available, publish only after checks, and agree a later review point.
You're ready to make clearer website decisions
Think back to where Sam started.
He wanted the right clients to understand Cedarline's work. Then he learned how to ask useful questions about ClearFlow, plan pages around real services, build better inquiry routes, check technical settings and prepare for launch.
Now he can explain the work to the client without leaving them with a confusing list of SEO tasks.
That's the real skill this course has been building: making informed decisions, explaining why they matter and knowing what should happen next.
You've reached the end of SEO & AI Visibility for Web Designers.
You can return to your saved studio plan and use it as a starting point for improving your own website. When you're planning a client project, use the optional Website Launch & SEO Handover Checklist to keep the handover clear and repeatable. Find it in the course resource panel; providing an email is required only for that optional resource, not for learning the lessons.
Keep one question with you: What's the next useful thing this website needs, and who will take care of it?