How to talk to the board about drops after a Google update

A drop after a Google update only becomes a business problem once it is clear what exactly has dropped, since when, and with what effect for the company. Specifics matter. In a conversation with the board, it is not the person who knows the most theories about algorithms who wins, but the one who separates facts from hypotheses and can turn them into decisions. That requires joining SEO data, analytics, technical implementations and sales results into one coherent narrative. The most important thing is this: the board does not need a lecture about Google, only a short, credible answer as to what happened, what the impact is and what needs to be done. A well-prepared conversation reduces chaos, speeds up decisions and lowers the risk of wrong reactions. A badly prepared one usually ends in a hunt for a culprit instead of looking for a solution.

What a conversation with the board after a Google update looks like in practice

This is not an academic debate. In practice, a conversation with the board after a Google update is the process of translating SEO data into management decisions, not a presentation of “pretty” charts. It is not mainly about rankings or the visibility graph itself, but about establishing what has dropped, since when, in which areas and what impact this has on leads, sales or acquisition cost. This is not an SEO report, but a decision-making document.

The board usually expects five things. Confirmation of the problem, the level of confidence in the diagnosis, a risk map, an action plan and a list of decisions requiring approval. The problem is that when these elements are blurred, the conversation drifts within minutes into general questions about the algorithm instead of staying focused on the real priorities. A good presentation should immediately show whether the problem is local, broad, temporary or structural. The question is: what does that change for the business right now.

The most useful format for such a conversation is a short decision pack. No embellishments. It should include a concise summary for the board, data confirming the scale of the drop, the most affected segments, the most likely causes and a recovery plan with owners and deadlines. The less educating about the algorithm and the more decision logic, the better the quality of the conversation. This is exactly the format that reduces “guesswork” and keeps the meeting on track.

The topic becomes critical when the drop affects pages and queries of high business value. Then there is no room for half-measures. This is especially important if organic traffic feeds the sales pipeline, supports e-commerce performance or, after a sudden drop, increases dependence on paid channels. In such situations, you need to say clearly whether changes are needed only in SEO, or also in content, UX, development, analytics or publishing rules. Not “we’ll improve something”, but exactly what and where.

In practice, it is also worth setting expectations around the certainty of the conclusions straight away. The data speaks clearly: some things can be confirmed with hard evidence, some will only be a strong time correlation, and some will remain a hypothesis for further verification. The biggest mistake at this stage is speaking with complete certainty about a cause that cannot yet be proved. It is better to honestly name the level of certainty than to promise a diagnosis that falls apart at the first follow-up question.

The current operational context and its impact on SEO

The current operational context is a set of factors that may explain a drop in SEO and do not necessarily mean that the Google update is to blame. In practice, the key is to distinguish the effect of algorithmic changes from seasonality, demand fluctuations, on-site implementations, measurement errors, indexing issues or shifts in search results layouts. The publication date of the update alone is not enough to make a diagnosis.

First, verify whether organic traffic has really dropped. And whether the drop is also visible in other metrics, not just in one chart. Compare clicks, impressions, CTR, position, brand and non-brand share and conversions or a sensible equivalent. One metric almost always says too little to speak to the board responsibly.

For this kind of analysis, you need data from several sources, not one tool. Most often this means Google Search Console, GA4 or another analytics system, server logs, a technical crawler, implementation history from the CMS or repository, ranking monitoring and the CRM or sales data. Only once all of this is combined into one whole can you assess whether the problem concerns visibility, traffic, measurement, indexing or the real business result. And that is where the difference begins between “something has dropped” and “we know what has dropped”.

From the board’s perspective, it is not the fact of the drop itself that matters, but its breakdown. You need to show whether specific product lines, services, countries, devices, page types or brand and non-brand queries were affected. This breakdown often turns the interpretation on its head, because a drop on an informational blog has a different meaning from a drop on category pages, offer pages or landing pages generating leads. The question is: where exactly does it hurt.

Clear communication also requires a hard separation of facts from assumptions. You can say that the drop in non-brand clicks on a given template type is confirmed, and that the correlation with the update window is strong, but the cause still needs validation. Not “we know”, but “we are checking”. That way of speaking builds credibility, because it clearly shows what is already known, what is not yet known and what the next stage of analysis will be based on.

How the process of preparing a conversation with the board works

The process of preparing a conversation with the board consists of turning scattered data into a short decision-making document: what has dropped, why, with what effect and what needs to be approved. It sounds simple, but it is easy to fall into a thinking shortcut here. You start by confirming that the problem is real and not the result of a measurement error, tagging changes or attribution differences. You check not only organic traffic, but also clicks, impressions, CTR, average position and conversions or a sensible proxy metric. If you do not confirm the data quality at the outset, the whole conversation will be based on bad conclusions.

The next step is to compare the moment of the drop against two calendars: Google’s public updates and what you yourselves have been changing on the site. And this is often where things get interesting, because the drop coincides not only with the update, but also with a redesign, a restructuring of internal linking, template changes, noindex, canonicals or a straightforward indexing issue. Timing correlation is still not a verdict. But beware, it can narrow the leads and cut off the most convenient excuse of “it’s definitely Google”.

Then you need to break the drop down into segments. Without this, the board sees one number and gets the impression the whole house is on fire. The analysis should clearly show whether brand or non-brand took the hit, which countries, devices, page types, URL directories and query groups are dropping the most. The most valuable segmentation is by business impact, not by reporting convenience. A drop on the informational blog and a drop on product pages may look similar in SEO, but they mean something completely different to the business. The question is: where does it really hurt.

Only after this segmentation does it make sense to talk about the causes. Not before. You need to check content quality, search intent alignment, duplication, thin content, keyword cannibalisation, changes in CTR in search results, crawl and indexing issues, performance, accessibility and UX elements. In practice, there is rarely one switch that is responsible; more often it is several small faults at once that add up to a major drop. So instead of one impressive theory, it is better to point to the most likely set of causes, backed by data. A diagnosis that reduces everything to one reason without comparing the data is usually too weak for board level.

After the diagnosis, you need to quantify the business impact and build the narrative. Without a narrative, you are left with slides, and slides do not make decisions. The board needs answers on which product lines were affected, how leads, sales or pressure on other channels changed, and whether the problem is local or broad. A good message structure is simple: what happened, how we know, what we still do not know, what the impact is, what we are doing now and what decisions we need. This order keeps the conversation on track and limits digressions about the algorithm itself.

At the end, an action plan is created. Concrete, with owners, dependencies and a reporting cycle, not a “wish list” for the future. It should separate quick safeguards, medium-term fixes and systemic changes that require time or collaboration between several teams. The board does not need the full audit, but a package that allows it to make a decision:

• a short summary of the problem and its scale,
• the most affected segments and areas,
• cause hypotheses with a level of confidence,
• action priorities and dependencies between teams,
• a list of decisions, approvals and resources needed immediately.

What to say to the board to be effective

When speaking to the board, you use the language of business impact and decisions. Not the language of positions and tools. Instead of saying “the average position has dropped”, it is better to show that the dip affects pages with high purchase intent, so the lead flow is shrinking and pressure on paid channels is increasing. And this is not cosmetic. Framing it this way immediately sets the right level of discussion and shortens the path from report to decision.

The most effective message has a simple structure. What happened, how we know, what we still do not know, what the impact is and what we propose next. This helps the board see the difference between fact, correlation and hypothesis, instead of receiving one smooth story. Clearly separating what is confirmed from what is still being checked builds credibility more than categorical claims. The question is whether the drop is one thread or several layered on top of each other. This is particularly important when the drop coincided with several changes at once.

A single metric in isolation can be like a thermometer without a patient. A drop in traffic on its own may say nothing about revenue, and visibility on its own will not show whether the pages that actually close sales have been affected. The minimum set to present is clicks, impressions, CTR, position, conversions or their proxy, and a split into brand and non-brand. Only then can you see whether it is an operational, strategic or simply reporting problem. And you immediately know where to look for leverage and where there is only noise.

Do not promise a quick rebound. Even less should you promise a certain return date. After changes to content, architecture or technical setup, some effects take time because Google has to reprocess and reassess the site, and that does not happen “by tomorrow”. The board will accept a realistic risk-reduction plan more readily than a promise of improvement without substance. A good answer is: we know what we are improving, we know how we will assess progress, and we know what cannot yet be concluded today. It sounds less impressive, but it works.

Also state plainly what decisions you need. Without this, the meeting ends with general goodwill and zero action. Usually this means priority for development, approval for changes in content governance, additional editorial resources, access to logs, deployment history or a regular review of critical sections. A general request for “SEO support” is simply not specific enough. The board works more efficiently when it gets a list of decisions, owners and the consequences of inaction, instead of a request to “do something”.

Finally, watch what not to say. Do not equate every drop with one update, do not mix brand with non-brand and do not serve a full audit where a decision is needed, not a lecture. An effective conversation with the board is not about showing everything, only about showing what changes a decision. What should resonate after the meeting. If it is clear what has been checked, what is most likely and who is responsible for the next steps, the communication has done its job.

The most important decisions and actions that need to be taken

The most important decisions are straightforward. They should quickly stop the losses, assign owners to the actions and set the priorities for work that genuinely increases traffic and business performance. The board does not need to approve the entire SEO audit. It needs to approve the scope of changes, resources, order of work and how the results will be monitored. The worst situation is agreement to “fix SEO” without a decision on who needs to deliver it, by when and with what priority.

In practice, the first group of decisions concerns operational priority. If the drop hits pages or queries of high value, there is no room for half measures. The right priority has to be given to technical fixes, content changes and data analysis, rather than hoping it will “somehow squeeze in” between other topics. Without this, SEO loses out to tasks in the backlog, and the problem drags on for weeks despite an accurate diagnosis.

The second group of decisions concerns the scope of the fix. Some actions are quick: unblocking indexing, correcting internal linking, fixing incorrect tags or restoring key content elements. Others need to take longer, because they involve rebuilding templates, updating the content policy, improving usability or changing the publishing process, in other words things that are not done “along the way”. The board should know which actions reduce risk immediately and which build improvement only over the following weeks or months.

• approval of development priority for technical fixes affecting crawl, indexing, templates and performance,
• approval of changes to content governance if the problem concerns quality, duplication, mismatch with intent or poor topic coverage,
• allocation of editorial, UX, analytical and SEO resources to the sections with the highest business value,
• ensuring access to data: GSC, analytics, CRM, server logs, deployment history and the template map,
• setting the owners of actions, deadlines, dependencies and the reporting cycle to the board.

The third decision concerns how progress is measured. “We’re working on SEO” sounds reassuring, but it is empty in informational terms. The question is what exactly we monitor separately: brand and non-brand, page types, countries, devices, transactional and informational queries, and the impact on leads or sales. If reporting is not segmented, it is easy to hide a real problem behind improvement in a less important area.

It is also necessary to agree a realistic expectation model straight away. Some fixes can work quickly, but others require Google’s systems to reassess them and do not have a “guaranteed rebound date”. That is why the plan for the board should show not only the expected direction of change, but also the limitations, risks and checkpoints after implementation, so decisions are based not on hope but on a verifiable timetable.

Common mistakes to avoid when talking to the board

The common mistakes are painfully repetitive. They involve mixing facts with assumptions, staring at technical metrics without business context, and asking for “general support” instead of specific decisions. Such a conversation usually ends in frustration on both sides. The board gets a flood of detail, but still does not hear clearly what it is supposed to approve and why.

The first common mistake is automatically attributing the entire drop to one Google update. The timing matters, but it is not proof in itself. The problem is that just as often the drop is partly caused by on-site deployments, content changes, indexing errors, SERP changes or faulty measurement. If you do not separate temporal correlation from confirmed cause, the board will be given a diagnosis that is too certain and may make the wrong decision.

The second mistake is showing one metric only, usually rankings or traffic. One chart is not enough. Visibility alone does not yet say whether the drop concerns an area important to the business, or merely “makes noise” at the margins. You need to separate brand from non-brand, informational pages from sales pages, low- and high-intent queries, and traffic from conversion impact. Otherwise you may trigger an alarm where the problem is limited, or, conversely, understate a truly costly problem.

The third mistake is promising a quick rebound. It sounds good on a slide. The board will usually accept uncertainty if it is clearly named and properly justified, rather than reality being spun. A declaration that “we’ll be back to the previous results in two weeks” works much worse when there is no basis for it. In a conversation about declines, it is better to promise process control and quality of decisions than a fast result that nobody can guarantee.

The fourth mistake is the lack of prioritisation. A list without hierarchy is, in practice, a lack of a plan. If the board is given a long list of problems without indicating what has the greatest impact on performance and what is blocking the rest of the work, the material becomes of little use. The question is not “what is wrong on the site”, but “what do we do first, why exactly that and what do we need for it”.

The fifth mistake is failing to close the conversation with decisions and the next step. Without that, the meeting drifts into the air. After the meeting it should be clear who is responsible for delivery, when the next checkpoint is and what data you will show in the next report. If the meeting ends without owners, deadlines and the scope of responsibility, even an accurate diagnosis will not translate into improvement.