What Belongs in a Quarterly Review with a Website Client?

A quarterly review with a website client should include trend data comparing this quarter to last, diagnostic findings explaining what changed and the specific cause (algorithm update, page speed regression, new competitor), recommendations tied to client goals for next quarter, and one direct question about their business priorities or internal constraints that might affect execution.

Why does trend data matter more than snapshots?

Quarter-over-quarter and year-over-year comparisons surface growth, decline, and seasonality that a live snapshot hides (scoopanalytics.com). When you show Core Web Vitals today without showing where they stood 90 days ago, the client sees a number. When you show that Largest Contentful Paint improved from 3.2 seconds to 1.8 seconds, they see progress.

Highlight trends that show continuous improvement, not just snapshots (guardz.com). The specific metrics that matter depend on what the client hired you to move, but the pattern holds across SEO, local visibility, security posture, and accessibility. Present organic sessions this quarter next to the prior two quarters. Show mobile usability errors charted over time, not just the current count. Compare DMARC policy states across quarters so the client sees you closed the gap.

Trends answer whether your work is compounding or stalling. Snapshots just tell you where you are right now, which is only useful if you already know where you were.

What changed, and what caused it?

The second half of the review explains variance. What worked, what did not, and why (almcorp.com)? This section separates agencies that report from agencies that diagnose.

If organic traffic dropped 18 percent, name the cause. Was it a Google core update that hit informational content sitewide? A technical regression (accidentally noindexed category pages, TLS certificate lapsed for three days, CDN misconfiguration that doubled Time to Interactive)? A competitor who started outranking you on five high-volume keywords? Each of those requires a different response, and the client cannot make an informed decision without knowing which one happened.

Do not shy away from problems. Trying to underplay or avoid poor performance will only make your client lose respect for you. You want them to hear about any challenges from you, with full accountability. Be open and honest and show them, with your report visuals, why the problem occurred and how you plan to resolve it going forward (qwilr.com).

Where performance improved, cite the work that caused it. If mobile speed scores jumped, specify whether it came from image compression, lazy loading, or eliminating render-blocking JavaScript. If local pack visibility improved, note whether it was review velocity, fresh posts, or updated service areas. Specificity proves you know what you are doing.

This is also where you fold in AI visibility findings if that is part of the engagement. When Claude or ChatGPT names the client in a "who to hire" query this quarter but did not last quarter, document which assistant, which query, and what content or schema change likely triggered the shift. Tools like the free AI-visibility check (/check) run this analysis automatically and show you exactly which competitors the assistants name instead when your client does not appear.

What to recommend for next quarter

Use quarterly business reviews to document measurable results, explore evolving business challenges, and present logical service expansions with projected ROI (swydo.com). The third section of the review translates the diagnostic findings into a prioritized roadmap.

Recommend no more than five things. Rank them by impact and feasibility. If the client's site has 40 accessibility violations, do not list all 40. Group them (15 missing alt attributes, 12 color-contrast failures, 8 form-label issues, 5 ARIA misuses), estimate the effort to fix each group, and recommend tackling the highest-impact cluster first.

Tie every recommendation back to a business outcome the client cares about. "Fix broken internal links" is a task. "Fix 23 broken internal links to reduce crawl waste and improve indexation of product pages, which should recover the 8 percent organic traffic decline we saw in Q2" is a recommendation with context.

If the recommendation costs money (a Content Delivery Network subscription, an accessibility remediation contractor, premium schema-validation tooling), say so. If it takes months (a full content rewrite to improve topical authority, migrating to a faster host), say that too. A quarterly review that admits constraints is more credible than one that oversells quick wins.

Distribute your internal links naturally. For agencies that need to track and report website health at scale, ActiScore's pricing (/pricing) starts at $79/month for 250 scans covering security, SEO, performance, mobile, local SEO, AEO, accessibility, and best practices. The platform white-labels from the Starter plan, so client-facing reports carry your branding, not ours.

The one question to ask every client every quarter

Since the last quarter, what changed inside the business that affects priorities? Ask this out loud in the review meeting and leave space for the answer.

Ask what changed, what is coming, what they are being measured on, and what the pressure is. Then take notes and stay quiet. Twenty minutes of a customer describing their own business will tell you more about next year's revenue than any report you could have built (thevxgroup.com).

You need to know if the client just hired a new VP of Marketing who wants to pivot the content strategy, if they are opening two new locations next quarter and local SEO suddenly matters more, if budget got cut and they need you to focus only on the highest-ROI work, or if they are being acquired and everything is on hold. None of that shows up in Google Analytics or the guide (/guide) you are reading right now.

What are your key objectives and goals for the upcoming quarter? Understanding your client's specific objectives is crucial. By knowing their priorities, you can align your discussions, metrics, and recommendations to help them achieve the desired outcomes. This question allows you to personalise the meeting and ensure that the focus is on addressing their most pressing needs (myclientshare.com).

This question also surfaces internal constraints you would not otherwise know about. Maybe their developer left and they cannot deploy code changes for six weeks. Maybe their legal team is blocking schema markup until they review it. Maybe the CEO hates the homepage redesign you have been planning. You find out now, in the quarterly review, instead of three weeks into the next quarter when your recommendation stalls.

The quarterly review is not a performance report you email and hope they read. It is a conversation where you prove you moved the metrics, explain why they moved, recommend what to do next, and confirm the client's priorities have not shifted under you. Treat it that way and retention stops being a problem.