Show clients what happens after launch

In the last lesson, Sam prepared a launch checklist for ClearFlow Plumbing. The site structure and content drafts are organized, but the owner still needs to approve the work and the team needs to finish its checks.

Sam thinks ahead to a question most designers will hear sooner or later:

“Once the website is live, how will we know whether it's helping?”

A client doesn't need a wall of charts. They need to understand whether people are finding the website, what visitors are doing and whether inquiries are reaching the business.

Sam starts with the information ClearFlow already has. That way, there will be something sensible to compare with after a future launch.

ClearFlow has records from September 1–30, 2026. Sam puts the most useful numbers next to their sources.

Sam doesn't draw arrows between these numbers. They come from different reports and describe different things.

For example, 142 clicks doesn't mean 142 homeowners visited, and it certainly doesn't mean 142 people inquired.

Likewise, the 127 organic sessions were counted by a different system. Sam doesn't subtract 127 from 142 and call the difference “lost visitors”.

The useful question is not “Why don't all the numbers match?” It's “What is each report measuring, and what can we learn from it?”

Sam opens Google Search Console. It's useful for understanding how a website appears in Google Search.

Two numbers matter at the start:

• Impressions: how often a link from the site appeared in search results under Google's counting rules.
• Clicks: how often someone clicked from those results to the website.

Search Console can also help Sam look at which pages appeared and which searches led to clicks. That's more useful than staring at a total alone.

ClearFlow's goal isn't simply to get as many visits as possible. The owner wants more relevant water heater repair inquiries from Austin homeowners, while continuing to serve drain cleaning customers.

So Sam would pay particular attention to the existing /water-heater-repair page and its relevant searches.

The September page report shows no impressions or clicks for that page. The October 20 website review later found a noindex setting. Sam already recorded the issue for investigation. Before reporting anything about that page's current search performance, he needs the authorized team to check its current setting.

The report gives Sam a place to start asking better questions. It doesn't replace the technical checks from Lesson 9.

Next, Sam opens the website's analytics report.

It shows 127 organic search sessions for September.

A session is a period of activity on the website. It's a different measurement from a click on a Google result. Analytics can also group organic search visits from search engines other than Google, depending on how the report is set up.

That means 127 sessions and 142 clicks can both be accurate without matching exactly.

If the figures change unexpectedly after launch, Sam should check that the date range, analytics setup and reporting definitions are comparable before drawing conclusions.

For a web designer, there's also a very practical check: is the tracking actually working on the redesigned website? If the analytics code or permissions change during a redesign, the client may lose useful measurement even when the website itself looks fine.

ClearFlow's contact records show four confirmed inquiries across all sources in September.

That isn't the same as four inquiries from SEO. The existing report doesn't tell Sam how many of the four came from organic search.

There were also nine phone-link clicks and five form submissions recorded across traffic sources. Those actions are useful, but they don't all mean the same thing:

• Someone can tap the phone link without completing a call.
• Someone can submit a form without becoming a qualified customer.
• A confirmed inquiry is different from a booked plumbing job.

If ClearFlow wants to understand where its inquiries come from, Sam should help the owner decide how to record the inquiry source and check that the tracking is working. The owner or the person managing reporting may need to help with that.

For a website project, Sam can start with two useful checks: does a test form message reach the business, and, if analytics event tracking is part of the agreed work, does it record a successful submission rather than just a button click? The business still needs to confirm which contacts were genuine inquiries.

A good client update says exactly what the records show. It doesn't turn every button click into a new customer.

Sam now has enough to explain the starting point without overwhelming ClearFlow's owner.

ClearFlow Plumbing · Website measurement note
Starting period: September 1–30, 2026

Before changing the website, we've recorded a September starting point. In September, ClearFlow's pages had 5,240 Google Search impressions and 142 clicks in the Search Console page report. Website analytics recorded 127 organic search sessions. Your contact records show four confirmed inquiries across all sources.

These figures measure different things, so we can't say that the four inquiries all came from Google. Our next steps are to confirm that the website and inquiry tracking work properly, check the earlier indexing issue on the water heater repair page and keep comparable reports for later reviews.

Notice what makes this update helpful: it explains the figures, connects them to the business goal and names the next checks. It doesn't promise that a redesign will increase traffic or inquiries.

Sam also keeps a separate work completed / work pending note. A drafted redesign is not a completed launch, and a successful form test is not a new sales lead. Those details will matter in the final handover.

When a client eventually approves a redesign and it goes live, Sam can use a simple follow-up routine.

When comparing periods, Sam should use similar date ranges and check whether the tracking and reporting definitions remained consistent. He should also consider other things that may have changed, such as demand for the services or other marketing activity.

Most importantly, a change in numbers isn't automatically proof that the website redesign caused it.

A useful report can explain both what has been observed and what still needs investigation.

Some clients will also ask, “Is our website appearing in Google's AI answers?”

Google Search Console now has a separate Generative AI performance report. When a website has enough data for the report to appear, it can show impressions for links in Google's AI Overviews and AI Mode.

That's useful, but it isn't a report of every time a business is mentioned by AI. It doesn't measure visibility across tools such as ChatGPT or other AI services. And an unavailable report doesn't tell Sam that the business is never mentioned by AI.

Sam also won't add the AI report's link impressions to the ordinary Google Search totals and treat them as a second, separate group of visitors. The report covers part of Google's broader Web Search data.

We'll explore how to explain AI visibility more carefully in Lesson 14.

Sam should apply the same care to the studio's own website.

He has drafts to improve Cedarline's /services and /work pages. Before publishing them, Sam needs to check what measurement access already exists, whether the project inquiry form actually delivers messages and what dates he can use as a starting point.

He doesn't have reliable studio traffic or inquiry numbers to quote yet. That's fine. The useful first step is to set up a trustworthy starting point, rather than guessing.

Try it with your own studio: If a new client asked how you'd show whether their website is helping, which two things would you check first? Would you know where the figures came from?

Sam now has a useful starting-point note for ClearFlow. It explains what Google Search shows, what website analytics measures and what the contact records actually confirm.

More importantly, Sam knows what he can tell the owner without guessing. He can track a future approved launch, review the right pages and ask for better inquiry-source information when the business needs it.

The goal isn't to impress the client with numbers. It's to help the client understand what happened, what still needs checking and what to do next.