18/11/2026
An SEO traffic drop tells you nothing until you know where it is happening and why. Fixing before diagnosing means rewriting healthy pages and leaving the cause untouched. This page is for the marketing or SEO lead who has to explain a fall in organic traffic to senior management, then decide what to do.
The method has five steps: check that the drop is real, locate it, identify the cause, decide, then prevent. Answers generated by search engines are now part of the picture; what they change in each area of work is described in our page on the impact of AI on SEO.
Check that the SEO traffic drop is real
Before looking for a cause, rule out false drops. A share of alerts comes from measurement, not from search performance.
Rule out a measurement problem
Compare two independent sources: clicks in Search Console and organic sessions in your analytics tool. If sessions fall while clicks are stable, the problem lies in data collection, not in the search results. Four causes recur:
- Broken tagging after a release: a tag missing from a template, a container left unpublished.
- A modified consent banner: a new configuration lowers the share of visits measured.
- A change in attribution: organic visits reclassified as direct or referral.
- A modified filter or view in the analytics tool.
Conversely, if Search Console clicks are falling too, the drop is real and the diagnosis can begin. Keep in mind that the two tools never match exactly: they do not count the same thing, and a constant gap between them is normal. What matters is a gap that opens suddenly, on a date you can tie to a change in tagging or consent.
Neutralise seasonality and the calendar
A month-on-month comparison is misleading as soon as the business is seasonal. Compare the period with the same period of the previous year, with an equivalent number of working days, and look at demand itself: if impressions fall across a whole topic while your positions have not moved, it is search volume that is declining, not your visibility. Note internal events too: a campaign that stopped, a publishing freeze or a price change sometimes explains what gets blamed on the search engine.
Locate the loss before looking for its cause
An overall drop is almost always the sum of a few local drops. Until it has been located, every hypothesis remains open.
Segment by page, query, device and country
In the Performance report of Google Search Console, compare two periods and break the loss down along four axes:
- By page and by template: does the drop affect the whole site, a directory, a type of page?
- By query: brand or non-brand, informational or decision queries?
- By device: mobile only, desktop only, both?
- By country and language: one market, or all of them?
A drop concentrated on one template points to a technical or editorial cause specific to that template. A drop limited to mobile points to rendering or performance. A drop limited to brand queries is rarely an SEO matter: it reflects falling demand. Breaking the site down by template and comparing on a constant scope are described in our method for website analysis.
Date the start of the drop precisely
The shape of the curve tells you as much as its size. Switch to a daily view and find the first day of the fall, on the pages that carry the loss. A step change, from one day to the next, signals an event: a deployment, a migration, a sanction, a search engine update. A steady erosion over several weeks signals an underlying movement: competitors gaining ground, content ageing, generated answers extending to new queries. The two shapes do not call for the same investigation: the first is solved by finding what happened that day, the second by comparing your pages with those that have overtaken them.
Read impressions, position and click-through rate together
Traffic is the product of three quantities, and each tells a different story. Read them together, on the pages and queries that carry the loss:
This reading does not give the cause, but it eliminates half of the hypotheses. Above all, it avoids the most common mistake: treating a fall in click-through rate at a stable position as a ranking problem.
Identify the cause: the six families
Once the loss has been located and characterised, six families of cause cover almost every case. They are checked in this order, from the quickest to verify to the longest.
A technical or indexing cause
This is the first lead when the fall is sudden and affects a set of pages. In Search Console, check the change in the number of indexed pages and the reasons for exclusion, then check on the affected pages:
- Directives: a noindex tag or a robots.txt rule deployed by mistake.
- Canonical tags: pointing to a URL other than the one intended.
- Response codes: server errors, pages that can no longer be found.
- Rendering: main content that no longer appears in the HTML seen by the crawler.
- Performance: a clear deterioration in loading times on mobile.
Set the date of the fall against the release log: a drop that begins on the day of a deployment rarely has another cause.
A migration or redesign
A change of URL, domain, site structure or template is the most costly cause, because it affects the whole site at once. The signs are characteristic: long-standing pages disappearing from the report, 404 errors rising, redirects in chains or pointing to the home page. Check that every old URL that carried traffic or links redirects to its equivalent, in a single step. Check as well that internal links, the sitemap and canonical tags now point to the new addresses rather than to the old ones: a migration is only complete when the site no longer relies on its own redirects. The method is described in our guide to the SEO redirect plan.
An algorithm update
Google changes its algorithm continuously: 500 to 600 updates a year (SEO.com, 2026). Most go unnoticed; a few, which are announced, redistribute positions across entire sectors. Three clues point to this cause: the fall coincides with an announced update, it affects many pages with no change on your side, and competitors with the same profile rise or fall at the same time.
In that case, there is no setting to undo. The response is editorial: compare the pages that lost with those that replaced them, on usefulness, depth, freshness and evidence of expertise.
A manual action
Rarer, it is checked in a minute: the Manual actions report in Search Console shows whether a Google reviewer has sanctioned the site, and on what grounds. Without a notification in that report, it is not a manual sanction, however large the fall. The word "penalty" is often wrongly used to describe a simple loss of ranking: the distinction matters, because a manual action is lifted through a reconsideration request, whereas an algorithmic decline cannot be negotiated. The grounds and the reconsideration procedure are detailed in our article on the Google penalty.
Competition or cannibalisation
If the loss affects a few specific queries, look at who now holds the place. A competitor may have published a more complete page, or Google may have changed the type of result expected (a comparison where it used to show a guide). Check your own pages too: when two URLs on the site alternate on the same query, neither settles, and positions fluctuate. This case is spotted by filtering a query in Search Console and listing the pages shown for it; it is dealt with by consolidation, as our article on SEO cannibalisation explains.
AI-generated answers
This is the cause to consider when the position is stable and the click-through rate is declining. A summary displayed above the links satisfies part of the searches without a visit. The phenomenon is broad: 60% of searches end without a click (Semrush, 2025), and the fall in organic traffic linked to the arrival of generative AI is estimated at between 15 and 35% (SEO.com, 2026; Squid Impact, 2025), a range that varies by sector and by type of query.
Three checks confirm the hypothesis: the loss is concentrated on simple informational queries, positions have not changed, and a reading of the results page shows an AI Overview on the queries concerned. Comparison and decision pages are generally less affected. The mechanism of searches without a visit, and how to measure it, is the subject of our article on zero-click.
Decide: fix, consolidate, redirect your effort
The diagnosis is only worth the decision it prepares. Each cause has a corresponding action of a different kind, and a recovery time that differs too:
The last row needs clarifying. A drop caused by generated answers is not "repaired" like a technical error: the click lost on a definition will not return. The decision concerns two points. First, make your pages citable, so that the summary names your brand. Second, shift effort towards the queries where a visit keeps its value: comparison, choice, implementation.
Prioritise by what is at stake, not by apparent size: a 40% loss on informational pages with no conversions weighs less than a 10% loss on pages that feed your sales enquiries. Link each affected page to the conversions it used to carry before setting the order of corrections. When two causes overlap, which is common after a redesign, deal first with the one that prevents the others from being measured: as long as pages are missing from the index, their content cannot be judged.
Present the diagnosis to senior management
Senior management is not asking for a course in search optimisation: it wants to know what happened, what it costs and what has been decided. Structure your report in four parts, on one page:
- The finding: the loss in figures, on what scope, since what date, compared with the same period of the previous year.
- The cause: the family identified, the checks carried out, and those that made it possible to rule out the other hypotheses.
- The stakes: the conversions carried by the affected pages, to distinguish a loss of visits from a loss of business.
- The plan: the actions, their owner, the expected recovery time and the date of the next review.
Two precautions make this report credible. Do not present as certain a cause that is only probable: say what has been verified and what remains a hypothesis. And do not announce a return to the previous level when the cause lies in generated answers: announce what you are aiming for instead, a presence in those answers and effort shifted towards decision pages.
Finally, set a dated checkpoint. A technical fix can be verified within a few weeks; if the curve does not react in that time, the cause retained was not the right one, or not the only one, and the diagnosis is reopened.
Prevent the next traffic drop
A drop detected within two days costs far less than one discovered at the monthly review. Three arrangements are enough to shorten that delay.
Monitoring at three rhythms
Organise monitoring according to what each rhythm lets you see:
- Every week: indexed pages, crawl errors, clicks on the pages that carry conversions, gaps in click-through rate at a stable position.
- Every month: positions by group of pages, queries won and lost, comparison with the same period of the previous year.
- At every release: a check of directives, canonical tags, redirects and rendering on a sample of each template.
Set alert thresholds per template rather than one overall threshold: a fall by half on one type of page can remain invisible in the site total.
A change log
The question "what changed that day?" must have a written answer. Keep a dated log of releases, publications, page removals, tagging changes and updates announced by search engines. When a drop occurs, this log cuts the diagnosis from several days to a few hours. It does not need a dedicated tool: a table shared between marketing, product and the technical team is enough, provided everyone records their changes on the day itself. Discipline matters more than format. Add one column for the pages or templates concerned by each change: it lets you match a line of the log to a segment of the loss in a single filter.
A less exposed portfolio of pages
A site whose traffic rests on definitions and simple questions is the most exposed to generated answers. Rebalance gradually towards pages that a summary does not replace: detailed comparisons, methods, proprietary data, decision pages. In parallel, track your presence in the answers of AI engines, so that visibility lost in clicks is partly regained in citations. This rebalancing is decided page by page: keep the informational pages that serve as a gateway to the topic, but give them a continuation towards a decision page, so that the remaining visit has somewhere to go.
FAQ on SEO traffic drops
Why is my SEO traffic dropping?
Six causes cover most cases: a technical or indexing problem, a badly redirected migration, an algorithm update, a manual action, stronger competition or internal cannibalisation, and AI-generated answers that reduce clicks. The diagnosis starts by locating the loss: which pages, which queries, which device.
How do you know whether the drop comes from a Google update?
Set the date of the fall against the updates announced by Google, check that no change took place on your site on that date, and see whether competitors with the same profile moved at the same time. If all three conditions are met, the cause is probable. The response is then editorial, not technical.
Do AI Overviews reduce SEO traffic?
Yes, on simple informational queries: the summary answers before the links and part of the searches end without a visit. The characteristic sign is a falling click-through rate at a stable position. Comparison and decision pages hold up better, because users look for evidence there.
How long does it take to recover traffic?
It depends on the cause. A corrected technical error is recovered in a few days to a few weeks. A badly redirected migration takes several weeks to several months. After an algorithm update, recovery often waits for the next update. Some of the clicks lost to generated answers do not come back.
Which tools should you use to diagnose a traffic drop?
Search Console is enough to locate the loss: pages, queries, devices, countries, indexing and manual actions. An analytics tool links the drop to conversions. A crawler checks directives, redirects and rendering. Your release log remains the most useful source of all.
Does a traffic drop mean a penalty?
Rarely. A manual sanction is always notified in the Manual actions report in Search Console; without a notification, it is not one. Most drops are explained by a technical cause, an algorithm update or a change in the results page.
Continue reading
Depending on what the diagnosis has shown:
- The anomalies affect several templates: if crawling, indexing or rendering is at fault on a large number of pages, the fix becomes a project in its own right → technical SEO audit.
- The results page answers in your place: if the position is stable and AI Overviews appear on your queries, the objective becomes citation → Google AI Overviews and SEO.
- You need figures to put the situation to senior management: if you need market benchmarks on clicks, positions and searches without a visit → SEO statistics.
- You want to spot the affected pages without assembling exports: if the drop concerns a site of several thousand URLs, the Incremys 360° GEO & SEO Audit module maps pages by template, flags technical and semantic anomalies, and shows for each keyword whether the brand is present in AI answers.
.png)
.jpeg)

.jpeg)
%2520-%2520blue.jpeg)
.avif)