SEO consultant monthly meeting: agenda and decision log
The structure that makes the monthly SEO consultant meeting work: a 45-minute agenda template, a decision log format and the topics that never enter the room.
By Roozbeh Nazari · CEO
In most companies the monthly SEO meeting falls into one of two shapes: a one-way session in which the consultant reads out a fifty-slide deck, or a free-form chat in which nobody remembers the decisions taken last month. Both burn budget. This article describes the meeting structure we use with our own clients: a forty-five-minute agenda, a one-page decision log, and a list of topics that should never enter the meeting. The structure adapts to any company that buys SEO consulting; the clinic examples come from the sector we work in.
Before the meeting: the report has been read
The first rule of the meeting is that the report is not read in the meeting. The one-page monthly report is sent at least two working days before; participants arrive having read it and noted their questions. We described which five blocks the report should consist of in a separate article; what matters here is that the report is the input to the meeting, not its output. If the report is opened for the first time in the meeting, the meeting turns into a reading session and no time is left for decisions.
The second precondition is that the previous meeting's decision log is in front of everyone. Without a decision log, the meeting starts from zero every month.
The forty-five-minute agenda
Five minutes: status of previous decisions. Every line in the decision log is read out one by one: done, not done, postponed. For items not done, nobody asks why; only a new date and owner are written. If this section runs past five minutes, the problem is not the meeting but the planning of the monthly workload.
Ten minutes: outcome metrics. The number of qualified organic enquiries, against the previous month and the same month of the previous year. A single question is discussed: is the change the result of our work, the season, or the market? The honest answer is often "we are not sure", and giving that answer is better than inventing a cause. In health tourism we know that demand follows the source market's calendar; Ramadan, summer holidays and school terms affect enquiries from the Gulf countries. When such an effect is discussed, the evidence is Search Console's month-by-month impression data and your own enquiry records.
Ten minutes: early-warning metrics. Clicks and impressions on the target query set, the share of target pages indexed, the share of URLs passing the good threshold in Core Web Vitals, critical errors. Only what has changed is discussed here; a metric that has not moved does not make the agenda.
Fifteen minutes: decisions. The real part of the meeting. The consultant brings at most three proposals; for each, the expected impact, the work required and the owner are written down. The client side accepts, rejects or postpones each proposal. Every accepted proposal goes into the decision log. No more than three proposals are brought, because we rarely see more than three meaningful pieces of work implemented in a month.
Five minutes: scope and blockers. How many recommendations are waiting for implementation? Which work is sitting not in the consultant's queue but in the developer team's or the content team's? This section reminds everyone every month that SEO is an organisational task, not a consultant's task. We drew the line between where consulting ends and implementation begins in our service model; that line should be visible in the meeting too.
Decision log format
The decision log can be a text file rather than a table; what matters is that every line carries the same five fields. Date: the meeting at which the decision was taken. Decision: one sentence, starting with a verb ("Physician information will be added to the Arabic treatment pages"). Owner: one person, not a team. Due date: a day, not a month. Status: open, done, cancelled. A sixth field, "why", can be added; someone reading the log a year later should see which data the decision rested on.
The log is kept in a shared document and updated within twenty-four hours of every meeting. Decisions cover not only SEO work but also the decision not to act: the line "Persian blog translation postponed this quarter, reason: budget" prevents the same discussion from reopening three months later. A closed decision is not deleted from the log but marked done; the length of the log is the history of the relationship. The consultant does this work; producing the meeting's output is part of the consulting service. The decisions of the first ninety days differ in character from those of later months; we described what the first period should focus on in our roadmap article.
What should not enter the meeting
Some topics hijack the meeting and eat the time reserved for decisions. Ranking lists: the question "where do we rank for this keyword" is not answered by what one person sees in their browser; personalisation, location and device change the result. If rankings are to be discussed, they are discussed through the average position in Search Console and that query's click count. Algorithm update speculation: when an update happens, the question is not "what changed" but "what changed on our pages", and that is a ten-second answer in the early-warning section. Competitor discussion: what a competitor is doing is interesting but does not produce decisions; competitor analysis is a separate piece of work, not a meeting. Tool comparison: which SEO tool is better has nothing to do with the client's budget.
Participants
Two people on the client side are enough: someone who can make decisions, and a representative of the team that will implement them. In a clinic this is usually the marketing lead and the person responsible for the website; having the patient coordinator join once a quarter keeps the enquiry-quality discussion grounded in reality. One person on the consultant side; if a technical topic is on the agenda, the developer is invited for that month but does not become a permanent participant. If more than six people are in the meeting, it turns into a presentation and the decisions get made somewhere else.
Quarterly and annual meetings
Alongside the monthly structure there are two different meetings. The quarterly meeting, unlike the monthly one, questions the KPI set itself: are we measuring the right thing, is the target query set still right, has a new locale or treatment area entered scope? The annual meeting looks at the contract itself: scope, budget, working surface and whether the relationship continues. Not mixing these three meeting types is the precondition for the monthly meeting finishing in forty-five minutes.
Our own practice
We regard the monthly meeting as the most valuable forty-five minutes of the engagement, and we count a month without a meeting as an incomplete delivery. We keep the decision log in the client's document, not in our own system; when the relationship ends, the log stays with the client. We pull all report data from the client's Search Console and GA4 accounts; you can see public examples on our reports page. The meeting structure itself is not complicated; the hard part is applying it with the same discipline every month.