When SEO traffic suddenly drops, first identify “which pages lost how much traffic,” then determine the cause. Directly changing titles, updating content in bulk, or adjusting the site structure can disrupt the current state and make subsequent troubleshooting harder to assess. For this kind of sharp traffic decline (baisse trafic seo), an effective starting point is to create a before-and-after comparison table for pages and determine whether the decline is concentrated on a few pages, a particular page type, or spread across the entire site.
Also confirm which data set shows the decline: a drop in search clicks in Google Search Console and a decrease in organic search sessions recorded in GA4 do not point to exactly the same troubleshooting steps. The former reflects changes in clicks from search results; the latter is also affected by tracking code, user consent settings, and channel attribution.
In the “Performance” report in Search Console, first review the daily click trend and identify when the decline began. Then select two periods of the same length with the same distribution of weekdays. You can start by comparing two full weeks; if the site normally receives few clicks per day, extend the periods as appropriate to avoid large percentage changes caused by a handful of clicks lost on an individual inquiry page.
Keep filters such as search type, country, and device consistent, and exclude dates for which data has not yet been fully reported. If the business has pronounced holidays or seasonality, also refer to the same period last year, while accounting for changes this year in newly added pages, promotional plans, and market coverage.
Next, cross-check organic search sessions in GA4. If GA4 shows a marked decline while Search Console clicks remain largely stable, first check the tracking implementation, redirects, and consent management settings. If both decline, move on to locating the affected pages. The two tools use different measurement criteria, so their figures do not need to match exactly; focus on whether the timing and scope of the decline are consistent.
In Search Console, enable date comparison, switch to the “Pages” dimension, and export data for both periods. For each URL, retain at least clicks, impressions, click-through rate, and average position, and add page type, language, or target market to make subsequent grouping easier.
Consider adding the following fields:
Sort in descending order by clicks lost first, then review the percentage decline. For example, if one page drops from 500 clicks to 250 and another from 10 to zero, the latter has a larger percentage decline, but the former has a much greater impact on the total. This is only a calculation example; actual priorities should also take inquiry quality into account.
The comparison table should include all URLs that appeared in either period to avoid missing pages that received no clicks in the later period. If there are many pages, also be aware of row limits in the interface and exports. If necessary, split the data by directory or use the API to retrieve more complete data; do not treat the visible list as a complete inventory of the site.

Also check whether other URLs have taken over the lost traffic: clicks to an old product page may decline while a new product page gains clicks, possibly due to a migration or a change in which page appears in search results. Search Console page data is generally attributed to the canonical URL selected by Google. When analyzing the data, consider redirects and canonicalization together to avoid double-counting losses.
Once you have a list of declining pages, group them by directory, template, language, country, and device before reviewing them individually. This step is especially important for multilingual international trade websites: a stable English directory alongside a decline in the French directory calls for a different scope of investigation than a simultaneous decline across product detail pages in all languages.
If losses are concentrated in a few high-traffic articles, first check the queries associated with those articles and changes in search results. If pages using the same template are declining in large numbers, review template deployments, internal link changes, indexing directives, and canonical URL settings. If the decline is limited to mobile devices or a particular country, continue the analysis with the relevant filters to avoid sitewide averages masking a localized issue.
For each group, review both total clicks and the number of affected pages. A decline on one high-traffic page may pull down the group’s overall figures; this alone does not mean the entire directory has a problem. Comparing the start of the decline with records of site releases, domain migrations, and URL changes can narrow the scope, but timing overlap is only a clue and must be verified by checking the pages.
For pages with substantial click losses and high business value, click the URL to open its report, then switch to the “Queries” dimension. Page-level average position and click-through rate can be affected by changes in the mix of queries, so compare the same set of key queries where possible and keep country and device settings consistent.
The Queries report does not show every query, so do not treat the sum of clicks for visible queries as the page’s total. When checking a URL, also consider the index record and live inspection: a page being accessible now does not mean it was free of issues when the decline occurred; likewise, a problem that has been fixed may not yet be reflected in search performance.
The final troubleshooting checklist should answer four questions: Which URL declined? How much traffic was lost? What type of shared issue does it indicate? Who should investigate next? For international B2B websites, losses on a small number of high-intent product pages may affect lead generation more than losses across many informational pages, so prioritize pages based on historical inquiry performance. After implementing fixes, continue monitoring with the same date ranges and filters, and record when the fixes were made so you can determine whether the affected pages have actually recovered.
Related Articles
Related Products


