SEO status meeting: a concrete checklist for client and agency

A useful SEO status meeting should create shared understanding and decisions. It should not require the client to interpret a wall of charts, and it should not require the agency to defend every fluctuation in search data. A clear agenda keeps evidence, interpretation, and next actions separate.

Use this checklist before, during, and after the meeting. Adjust the depth to the engagement, but keep the underlying questions visible.

Before the meeting: prepare the evidence

Confirm the reporting period

Write down the exact dates or scan numbers. Ensure that every chart and finding uses the stated period or clearly labels a different comparison.

Confirm the scope

List the project, domain, selected pages, markets, and sources. If the report covers only part of the website, say so. Check whether WordPress evidence, crawler data, or Search Console data was unavailable or delayed.

Review concrete changes

Identify the most relevant page-level findings. Preserve links and before-and-after values so the team can open the evidence during the meeting.

Separate unfinished recommendations

Mark recommendations, work in progress, completed actions, and publicly observed results distinctly. Do not place them all under a generic “done” heading.

Opening the meeting

Begin with the purpose: review what was documented, clarify exceptions, and agree on priorities. Confirm whether anyone expects the meeting to cover performance, implementation, strategy, or all three.

State the important coverage limitations early. This prevents a missing data source from becoming a surprise after conclusions have already been discussed.

Part 1: documented activity

Ask the agency or internal specialist to walk through material activity by page and category.

• Which pages changed?
• What was added, removed, or modified?
• Which source recorded or observed the event?
• Is actor attribution confirmed, uncertain, or unavailable?
• Was active time recorded, and what was the tracking coverage?

Open a small number of representative findings rather than reading every row aloud. The complete evidence can remain available for later inspection.

Part 2: unexpected findings

Focus on changes that were not planned, corrections that did not remain active, or technical conditions requiring confirmation.

For each one, decide whether to verify, repair, monitor, or accept it. Assign an owner and a target date when action is required. Avoid labeling every difference as an emergency.

Part 3: results and context

If performance data is included, name the source, date range, filters, and comparison. Discuss impressions, clicks, traffic, leads, or revenue as outcomes rather than proof of completed work.

Ask which documented changes could plausibly relate to the movement and what other explanations exist. Seasonality, demand, competitors, campaigns, tracking changes, and search interface changes may all matter.

Use careful language. “The movement followed the documented update” is evidence about timing. “The update caused the movement” requires a much stronger basis.

Part 4: decisions and next steps

Turn findings into a short, prioritized list. Every item should have:

1. a clear action or question
2. an owner
3. a target time
4. the evidence that will confirm completion
5. the report or source where the result should appear

This last point makes the next meeting easier. If a redirect will be repaired, agree that the next scan should show the intended destination and successful response.

Questions the client can ask

• What was directly observed versus professionally interpreted?
• Which important work is outside the report’s visibility?
• Can we open the affected page or source evidence?
• Did any earlier fix disappear or change again?
• Are we comparing equivalent periods and scope?
• What remains unknown after this report?
• What should be visible next time if the plan is completed?

These questions are normal governance, not distrust.

Questions the agency can ask

• Did the client make or approve changes outside the agency workflow?
• Are upcoming releases likely to affect monitored pages?
• Has the business priority or target market changed?
• Which findings need business context before they are judged?
• Who can confirm intent for unexpected changes?

The answers help prevent technically correct observations from receiving the wrong interpretation.

Common meeting mistakes

Do not spend the entire meeting explaining a single composite score. Do not present rankings without query, market, device, and time context. Do not call missing data “no activity.” Do not mix recommendations with completed work. Do not leave without named decisions.

A beautiful slide deck cannot compensate for missing source evidence. A plain report can be highly useful when every claim is traceable.

After the meeting

Record the decisions, owners, and expected evidence. Keep the report immutable so the historical record does not change after discussion. Corrections or notes can be attached without rewriting what was originally observed.

At the next meeting, begin by reviewing the agreed items. This creates continuity and makes recurring reporting a working process rather than a monthly performance ritual.

Conclusion

An SEO status meeting works best when it starts with scope and evidence, reviews unexpected findings, discusses outcomes with appropriate caution, and ends with verifiable next steps. Both client and agency should leave knowing what changed, what is interpreted, what remains unknown, and what will be checked next.

Use the main guide to SEO reporting and the checklist for what an agency should document to prepare the underlying material.