· Notes for owners
Why did my Search Console clicks spike? Check for bots first
A sudden jump in Search Console clicks can be bot traffic, not customers. Here is how to check the reports and filter the spike before you act.
On November 5, 2026, Search Engine Journal reported that sudden spikes in Google Search Console clicks were not human traffic. Several sites saw jumps of 2x to 6.5x between Oct. 31 and Nov. 2, 2026, while impressions and rankings stayed flat. The cause may be bots or a Google logging bug. Either way, the clicks did not come from people searching.
Do you know which of your clicks came from a person? If a chart jumps, answer that question before you read the jump as growth.
A spike in clicks is not a sale
The pattern is worth knowing by sight. On one multi-location service business, desktop clicks jumped 14.1x over the prior seven-day average while mobile clicks stayed flat. On Nov. 2, 2026, 91% of that site's clicks were desktop (297 of 327).
Two details explain the pattern. Pages that ranked on Pages 2 to 6 suddenly logged 45% to 100% click-through rates. Second, the clicks landed across dozens of one-off query variations, mostly on desktop.
In the news example, impressions stayed flat while one site's clicks went from about 50 a day to 327, a 6.5x spike.
What the AI reports count
Google's generative AI performance report counts impressions as the number of times links to your site were shown to a user in an AI feature, such as AI Overviews and AI Mode. Sites that appear in those features are included in overall Search Console traffic. Google's help page for the report is dated 2026-08-31.
Bing's AI Performance report counts citations, aggregated across supported AI surfaces, and its data is a sample (as of 2026-02-10). It does not indicate ranking, authority or the role of a page within an answer. On 2026-06-16, Bing added Intents, Topics, Citation Share and Compare to the report in preview, as described here.
The published pages do not state what share of the Bing data is sampled, or the reporting delay of either report.
Two traps to avoid
- Reading a Bing citation count as traffic or placement. A citation is a mention inside an answer. The report does not show that the page ranked, that it was trusted, or that anyone visited.
- Comparing AI impressions across the logging gap. Google lists a logging error that decreased impressions on the Generative AI performance report for data from August 13 to August 17, 2026. Read the data anomalies page before you compare any trend across those days.
What to do this week
Hand this list to whoever runs your website or reports.
- Find the date range of any spike in Search Console. Do not change plans on it yet.
- Compare the desktop line with the mobile line. The news item used the mobile trend as its unaffected baseline.
- On the Pages tab, filter for Position greater than 10. This shows the deep-ranking pages that gained clicks.
- If one page is the problem, exclude it with the Page filter in the top bar. The news item notes there is no single button to strip out only bot clicks when dozens of pages are affected.
- Before you compare AI impressions over time, check the anomaly dates from August 13 to August 17, 2026.
- Set any plan by the orders and bookings that followed the spike, not by the click line.
The news item does not say whether the spike will continue. Plan around that uncertainty, not around the chart.
Reading these reports well is part of organic growth work. The numbers help only when the traffic behind them is real. Our work is being your technology department: we map how your business sells, build the systems your customers find you with and everything behind them, and run those systems with you. Your next step to grow is a discovery call.