Google Search Console Click Spikes Are Bot Traffic, Not Demand

What happened

Some site owners opened Google Search Console and saw a sharp vertical spike in clicks. Impressions and rankings hadn't moved. Joy Hawkins shared a screenshot, Barry Schwartz asked how people were filtering it, and Marie Haynes then analysed the pattern across the sites she monitors, in a write-up for Search Engine Journal.

Most properties looked normal. A subset saw clicks jump 2x to 6.5x between Oct. 31 and Nov. 2, 2026. The data she pulled was fresh and not yet finalized, so details could still change.

One example: a site with a six-month median of 21 desktop clicks a day logged 297 on Nov. 2. Its desktop CTR went from 0.20% to 2.89%, while mobile stayed flat. More than 40 city and service pages that had no clicks all week suddenly got three to 16 clicks each, even though they ranked on pages 2 to 6.

Why it doesn't look human

The giveaway is where the clicks landed. Real clicks cluster in the top few results on page 1. Here, URLs at positions 12 to 54 showed CTRs of 45% to 100%, mostly on desktop. Many queries logged exactly one click on one impression.

A second site showed a different pattern. One troubleshooting page that normally gets zero to one click a day jumped to 40 clicks on Nov. 2, all from Canada. The clicks came from 23 slightly reworded versions of the same question, including systematic number swaps like 3 times, 4 times and 5 times.

Impressions looked flat because of scale. Adding around 275 impressions to a site with 18,000 a day barely moves the line. Adding 275 clicks to a 50-click baseline makes a huge spike.

What could be behind it

Nobody has confirmed a cause. The article lists four possibilities:

• Scrapers or headless browsers that click through results.
• CTR manipulation networks clicking decoy results to warm up browser profiles.
• AI agents running query fan-out and opening candidate pages.
• A gap or glitch in Google's normal bot-click filtering.

The analysis says it is not human traffic either way.

Why it matters for your business

The risk is mostly misreading the data. If you report a click spike to a client or your board, someone will ask what you did to cause it. If you chase it, you might build content around queries nobody real searched for.

It also shows how automated visits to search results and pages are becoming harder to separate from real demand. AI agents browsing on behalf of users are part of that mix, and your reports will increasingly need filtering.

What to do now

GSC has no single button to strip out only bot clicks if many pages were hit. These approaches help:

1. Exclude a spiked URL. Use Add filter > Page > URLs not containing, and enter the slug or subfolder.
2. Check the Countries tab. One affected page's spike came entirely from Canada, so a country filter can isolate it.
3. Switch to Device: Mobile. On the affected sites, mobile stayed flat and gives a cleaner trendline.
4. Filter the Pages tab by Position > 10. This shows which deep-ranking URLs were hit.

Beyond filtering, annotate the dates in your reporting so the spike is explained. Compare GSC with your own analytics and sales data. If clicks rose and nothing else did, treat the clicks with suspicion.

Don't make strategy changes based on Oct. 31 to Nov. 2 data. Wait to see whether Google cleans it up or acknowledges it.

The bottom line

If your numbers jumped without any matching rise in leads, orders or engaged sessions, assume the spike is noise until proven otherwise. Check mobile and country splits first, and report the filtered trend.