Google Search Console Reports Suspicious Click Spikes for Some Sites

Google Search Console's performance report has shown a sharp, unexplained spike in clicks for a subset of sites since roughly November 1, 2026, and Google has not yet confirmed a cause. Impressions, notably, remain flat. That asymmetry is the strongest clue analysts have.

The anomaly first surfaced through Search Engine Land's reporting, which found three sites with a huge click spike via the Search Console API. The Google web interface showed the spike on only one of those three properties. This API-versus-interface discrepancy suggests the issue may sit inside Google's reporting pipeline rather than in actual search behavior. No Google statement exists as of publication; I reached to Google for comment and nothing confirmed has returned.

Who is seeing the spike?

The pattern is uneven, and that unevenness matters.

• Joy Hawkins posted a chart on X showing the click spike and later wrote: "3 sites so far look like this. Based on the CTR patterns I'm seeing I'm fairly confident it's bot traffic."
• Glenn Gabe confirmed the anomaly on X on November 3, 2026: "Only seeing that on a few properties. Most DO NOT show that. And very well could be a bug."
• Lily Ray and Alex Wolk were tagged into the same thread, extending the discussion.
• One site owner reported: "I have 5x clicks in GSC for the weekend... could this be rank trackers resolving the ?goto parameters? They don't seem to have translated to actual traffic on site."
• Another commenter, @_WeirdGinger, claimed the pattern appeared across roughly 60% of brands they checked, and advised checking Google Analytics data for October 31.

The 60% figure is an anecdotal estimate from a single practitioner, not a measured sample. Treat it as signal, not data.

What does the evidence actually show?

Three facts separate confirmed observation from speculation.

First, the confirmed part: multiple independent SEOs report inflated click counts in Search Console over the past several days, concentrated around the weekend of October 31 to November 1, 2026. One reporter saw five times normal click volume.

Second, the tool-signal part: Hawkins reports flat impressions alongside the click spike, and abnormal CTR patterns. Gabe sees it on only a few properties. The API and the web interface disagree on two of three tested sites.

Third, what is not said: Google has issued no statement confirming or denying a bug, a bot surge, or a data-processing error. Every explanation on the table, bot traffic, rank-tracker parameter pollution, or an internal reporting defect, remains practitioner speculation.

The comment about "?goto parameters" deserves scrutiny. If rank-tracking tools were resolving redirect parameters through Google results, the clicks would register in Search Console without producing sessions on the site. The reporter's observation that the spike "doesn't seem to have translated to actual traffic" fits that theory. It also fits plain bot traffic. The evidence cannot yet distinguish between them.

Should site owners act?

Not yet. The spike affects reporting, not rankings, and no one has documented an actual traffic increase on affected sites. Site owners who benchmark CTR or click volumes for month-over-month reporting should annotate the affected dates now, before any Google correction rewrites or removes the data. Comparing Search Console clicks against Google Analytics sessions for October 31 through November 2 will quickly show whether the spike reflects real visits.

Takeaway: this is a reporting anomaly, not a ranking event, and nobody should adjust strategy around it.

Watch for a Google statement on the Search Console data, and check whether the company retroactively corrects the affected dates in future reports.