If your Search Console showed a sudden jump in clicks in early November, do not celebrate yet. Between October 31 and November 2, several sites saw clicks jump 2x to 6.5x while impressions and rankings stayed flat, mostly on desktop and on pages ranking around positions 11 to 55. Analyst Marie Haynes says it is bot traffic, or a Google logging issue, and no site changes are needed. Check any early-November jump before reporting it as growth.
The pattern was striking because of what did not move. Clicks rose sharply, between 2x and 6.5x on the affected sites, over just a few days at the turn of the month. Impressions, the number of times pages appeared in search results, stayed flat, and rankings did not change either. That combination is the fingerprint of a reporting anomaly rather than real growth, because real growth in clicks normally comes with more impressions, better positions, or both.
The spike was concentrated in specific places: mostly desktop traffic, and mostly pages ranking around positions 11 to 55, the stretch of the results where pages appear on later pages or low on the first one. A genuine surge of human interest would spread more evenly across devices and positions, and it would usually show up in analytics and server logs as real visits. A spike that lives only in one report, in one device category, and in one band of positions is behaving like a measurement artefact.
Analyst Marie Haynes says the early-November jump is bot traffic, or a Google logging issue, and her advice is clear: no site changes are needed. The reasoning is practical. Bots can generate clicks that Search Console records, especially automated traffic that mimics search visits, and a logging issue on Google's side can inflate the numbers in the same way. Either explanation fits the evidence far better than a sudden, invisible wave of human searchers who left no trace in rankings or impressions.
The advice not to change anything is the part worth underlining. A site owner who sees clicks multiply will naturally want to do something: publish more of whatever spiked, shift budget, or report a win to a client. Acting on a phantom spike means optimising for traffic that never existed, and it can mean explaining a correction later when the numbers fall back to normal. The disciplined move is to verify first and celebrate later.
Start by narrowing the spike down. In Search Console, filter the affected dates and break the clicks down by page, query, device, and country. If the extra clicks sit on a small set of pages, in one device category, or from an odd mix of locations, that points toward bots rather than people. Then compare against your analytics: real clicks become sessions, and sessions leave footprints such as time on site and further page views, while bot clicks usually do not.
Check your server logs too, if you can. A real surge in visits shows up as real requests from varied sources, while bot traffic often arrives in bursts from a narrow set of addresses or with unusual user agents. You do not need to become a log analyst to do this: even a rough look at whether analytics sessions rose in step with the Search Console clicks will tell you most of what you need to know. If the clicks rose and the sessions did not, the clicks were not people.
Once you have confirmed a spike is not real, the next job is to keep it out of your reports. Annotate the dates in whatever tool you use, so that a future reader knows the early-November numbers carry an asterisk. When you compare periods, either exclude October 31 to November 2 from the comparison or show the comparison both ways, with and without the spike, so nobody draws a conclusion from the inflated numbers alone.
For ongoing monitoring, set up a simple cross-check: a weekly comparison of Search Console clicks against analytics sessions, so that a future divergence shows up quickly. The practical takeaway is to build reporting that trusts no single source, because any single source can be distorted by bots or by a logging problem, and the distortion always looks like good news, which is exactly when people stop checking.
For SEOs, this spike is a reminder that the numbers are not the work, they are the evidence for the work, and bad evidence leads to bad decisions. Reporting bot clicks as growth misleads clients, distorts forecasts, and can push a team to double down on pages that did nothing special. The SEOs who caught the spike early, checked it against a second source, and reported it honestly are the ones whose clients will trust the next report.
For link builders, the lesson is about choosing targets by real performance. A page whose clicks spiked on bots is not suddenly a better link target, and a campaign built on phantom traffic will disappoint when the real numbers arrive. Judge pages by the traffic that actually turns into engagement, and keep the bot spikes out of the story you tell about your own results.
Sources: Search Engine Journal, November 5, 2026.
Related reading on this site: 88% Disconnect Between Google Top 10 and ChatGPT Recommendations, Study Finds, Ahrefs: Half of AI Citations Vanish Within a Day, Google Search Queries Hit a Five-Year High — and Revenue Didn't Follow, November 2026 Google Webmaster Report: Spam Update Done, AI Everywhere, Google's November 2026 Core Update Is Rolling Out, and Google Tests AI Overview Query Refinements That Lead to AI Mode.
Linkbaits helps you create content that earns citations and backlinks. Start with the toolkit and build your first linkable asset this week.
Start free trial