Earlier this week, I saw Barry Schwartz’s article on X (and his write-up on Search Engine Roundtable) sharing a screenshot from Joy Hawkins. Joy noticed that multiple sites were seeing sudden, enormous vertical spikes in Google Search Console clicks during impressions stayed flat, and Barry asked a awesome follow-up question: “Anyone alternatively seeing this? If so, how are you filtering the report…”
When I saw Barry’s tweet, I immediately idea this would be the supreme real-world test for Marie’s Brain – my soon-to-be-launched agentic SEO and AI hunt inspection system.
Over the former multiple months, I have been construction Marie’s Brain to merge my 15+ years of investigation on Google’s ranking systems alongside live, programmatic admission to the Search Console and analytics data of the sites I monitor. Instead of manually clicking through Search Console asset by asset to see if any of my clients were affected, I asked my scheme to scan throughout all of the sites I monitor, inspect the unfinalized caller data through Nov. 2, 2026, and emblem any asset showing a abrupt anomaly in clicks.
Within seconds, Marie’s Brain surfaced the exact identical vertical spike throughout multiple sites in entirely distinct industries – and pulled the raw page, query, device, and nation dimensions so I could see what was really happening under the hood.
Key Takeaways
- Not genuine individual searchers: Between Oct. 31 and Nov. 2, 2026, multiple sites saw abrupt 2x to 6.5x spikes in Search Console clicks during impressions and rankings stayed flat. Whether this is external bot/agent retrieval or a Google logging bug counting automated fetches as clicks, it is not individual traffic.
- Why it looks so strange: Pages ranking on Pages 2 to 6 (Positions 12 to 54) abruptly logged 45% to 100% CTR throughout dozens of one-off query variations (mostly on Desktop).
- How to display it: There is no sole clasp in GSC to band out lone the bot clicks if dozens of pages were affected. However, you can exclude a sole spiked URL alongside a top-bar Page filter, or inspect Device: Mobile to see your unaffected mobile trendline. You can display the Pages tab by Position > 10 to see which deep-ranking URLs were affected.
What I Found Across The Sites I Monitor
Just akin Glenn Gabe and Joy Hawkins mentioned in Barry’s Search Engine Roundtable post, the bulk of properties I detect showed entirely normal traffic. However, during several SEOs saw the motion commencement complete the weekend (Oct. 31 to Nov. 1), a distinct subset of sites I detect informed a theatrical vertical spike on Monday, Nov. 2, 2026 that mirrors Joy’s screenshot:
Here is how those three anonymized properties behaved on Nov. 2, 2026 compared to their previous seven-day baseline (Oct. 26 – Nov. 1, 2026):
| Anonymized Property | Prior 7-Day Avg Clicks | Nov. 2, 2026 Clicks | Spike Multiplier | Where the Anomaly Concentrated |
|---|---|---|---|---|
| Site A (Multi-Location Service Business) | ~50 / day | 327 | 6.5x (14.1x Desktop) | United States; 91% Desktop (297 of 327 clicks throughout 120 pages) |
| Site B (Regional Service Business) | ~16 / day | 66 | 4.1x (7.9x Desktop) | United States; 83% Desktop (55 of 66 clicks throughout 36 pages) |
| Site C (Technical Q&A Site) | ~68 / day | 144 | 2.1x | Canada (jumped from ~11/day to 75 clicks during US stayed flat at 67); 40 clicks hit a sole leaf throughout 23 reworded query variations |
The 2 Big Clues In The Data
When I had my scheme drill into the raw API rows for Nov. 2, two unmistakable patterns emerged throughout the affected sites:
1. 45% To 100% CTR On Page 2 To Page 6 Results (And Why Impressions Looked Flat)
Normally, integrated clicks in Search Console are heavily concentrated in the top 3 to 5 results on Page 1. On Nov. 2, click-through charge (CTR) exploded on pages ranking between Position 11 and Position 55 (Pages 2 through 6 of Google):
- On Site A, desktop clicks jumped 14.1x complete the six-month regular median (21/day median to 297 on Nov. 2), pushing sitewide Desktop CTR from 0.20% to 2.89%, during mobile clicks stayed entirely flat (30 clicks on Nov. 2 vs. 25-40 on previous days).
- More than 40 inner city and assistance pages on Site A that had zero clicks all week abruptly logged three to 16 clicks all during ranking on Page 2 to Page 6 (for example, one city leaf logged nine clicks on 13 impressions = 69.2% CTR at Position 15.5; another logged five clicks on 11 impressions = 45.5% CTR at Position 53.8).
- Nearly all apparent non-brand query on Sites A and B logged one click on one impression (100% CTR) on Desktop at profound ranking positions (Position 14, 21, 24, 28, 30, 34, 38).
Why did total impressions remain flat if all click additionally had an impression? It comes downward to uncomplicated scale. When a location normally gets 18,000 impressions and 50 clicks per day (like Site A), adding 275 automated impressions is lone a 1.5% bump on the belief row – entirely invisible on a chart! Adding 275 clicks to a 50-click baseline, on the another hand, creates a enormous 6.5x vertical spike.
2. Synthetic Query Fan-Out Clusters
On Site C (a specialized troubleshooting Q&A site), a sole long-tail troubleshooting leaf that normally gets zero to one click per day (and never received additional than seven clicks in a sole day throughout the complete former six months) abruptly jumped to 13 clicks on Nov. 1 and 40 clicks on Nov. 2.
While the spikes on Sites A and B came from U.S. searches, all 40 clicks on this Site C leaf came from Canada. From Oct. 28 to Oct.r 31, that leaf lone had four to seven impressions per day in Canada (and 0 clicks) during ranking on Page 2. Then on Nov. 2, Canadian impressions on that leaf jumped by ~45 (to 50 impressions), and Canadian clicks jumped from 0 to 40 clicks – definition nearly all sole one of those new impressions was clicked (an 80.0% CTR at average stance 14.6 on Page 2, during U.S. clicks on that leaf stayed at 0)!
When I inspected the exact queries that clicked into that sole URL on Nov. 2, there were 23 slightly reworded variations of the exact identical troubleshooting inquiry (including systematic figure permutations akin 3 times, 4 times, 5 times, 7 times, 10 times), nearly all sole one logging 100% CTR (1 click / 1 impression, 2/2, or 3/3) between Position 10.0 and Position 33.0. Other troubleshooting pages on the identical location logged 1 click / 1 belief (100% CTR) at Position 45.5 to 54.0.
What Could Be Causing This?
Normally, whenever a essential position tracker or scraper loads a Google hunt results page, it lone generates impressions – not clicks. For Search Console to document a click, a browser or bot has to really prosecute (or trigger) Google’s click-tracking nexus on the hunt results page.
Looking at the data patterns throughout these sites, four possibilities remain out:
- Scrapers or Headless Browser Bots That Also Click Through: If a scraper network or automated crawler lately started clicking through SERP links on Pages 2 through 6 to scrape the underlying leaf satisfied (or resolving Google’s click-tracking redirect parameters to catch the final URL, as one commenter suggested on Search Engine Roundtable), Search Console volition log a 1 click / 1 belief (100% CTR) event on all outcome it visits.
- CTR Manipulation Networks (“Cookie Warming” or Decoy Clicks): Even if a endeavor would never pay for CTR manipulation, automated click-bot networks frequently hit guiltless sites in the identical niche. To create counterfeit headless Desktop browser profiles appearance akin “real humans” to Google’s user-signal systems, CTR manipulation bots are programmed to run searches and click random “decoy” results throughout Pages 2 to 6 to heated up browser cookies (or misfire throughout another listings on the leaf during hunting for their mark URL).
- AI Agent / Query Fan-Out Retrieval: As we move deeper into the agentic web, automated investigation agents are increasingly browsing the web on behalf of users. On Site C, anywhere a sole troubleshooting leaf was clicked throughout 23 slightly reworded variations of the identical inquiry (including systematic figure permutations akin 3 times, 4 times, 5 times, 7 times, 10 times), the query form looks remarkably akin synthetic query fan-out from an AI delegate or investigation tool using a headless browser to open applicant URLs and extract answers.
- A Gap in Google’s Bot-Click Filtering: Google normally filters known automated and bot clicks out of Search Console rearward the scenes. Whether this is a brand-new motion of headless browser bots that bypassed Google’s filters or a impermanent glitch in how Google filters automated click-throughs, those non-human clicks made it into our achievement charts.
How To Filter Your Google Search Console Reports
Because GSC does not let you display the top achievement diagram by ranking stance or CTR, there is no ideal one-click clasp to band only the bot clicks out of your sitewide chart if dozens of pages were affected. However, these three approaches activity fine depending on how your location was impacted:
1. Exclude A Specific Spiked URL (Or Filter By Country)
- If lone one or a few pages spiked (like Site C): Click + Add display > Page… > URLs not containing at the top of the study and act that URL bullet (or a subfolder akin /locations/). This cleanly removes the spiked leaf from the top diagram during keeping 100% of your lawful traffic on the remainder of the location intact.
- If the spike came from a particular country: While Sites A and B saw their spikes arrive from the U.S., Site C’s spike came entirely from Canada (where sitewide Canadian clicks jumped nearly seven times during U.S. clicks stayed flat at 67). Checking the Countries tab in GSC volition quickly inform you if the bot motion hit you from a sole nation that you can display out in the top bar.
2. Use Device: Mobile To Sanity-Check Your Trendline
If dozens of pages throughout your entire location spiked on Desktop (like Sites A & B), you cannot exclude all leaf individually. While filtering the top bar by Device: Mobile evidently hides your lawful Desktop traffic too, it is a awesome sanity inspect to display a client or stakeholder that your Mobile integrated trendline is entirely normal (on Site A, Mobile clicks were 30 on Nov 2 vs. 27-40 on previous days; on Site B, Mobile clicks were 11 on Nov 2 vs. 11 on Nov 1).
3. See Which URLs Were Affected In The Pages Table (Position > 10)
To see the exact pages that were affected on your site:
- Check the boxes for Average CTR and Average stance at the top of the diagram so those columns appear in the array below.
- Click the Pages tab (use the Pages tab fairly than the Queries tab, as GSC hides most one-off single-impression queries for privacy).
- Click the display chimney icon inner the array header, choose Position, choose Greater than, and act 10.
- Sort by Clicks descending to see all Page 2 to Page 6 URL that logged 30% to 100% CTR during the spike.
4. Prompt To Run If Your AI Agent Or LLM Is Connected To The GSC API
If you have Claude, Gemini, ChatGPT, or an agentic coding surroundings (like Antigravity or Cursor) connected to the Google Search Console API or a custom MCP server, you can paste this exact immediate to inspect all of your sites in seconds:
Query the Google Search Console API for my site(s) from October 20, 2026 through the latest accessible date using dataState: "all" (so caller unfinalized data is included): 1. Check regular sitewide clicks and impressions to see if any date between October 31 and November 2, 2026 spiked by additional than 2x compared to the previous 7-day average. 2. For any spiked date, interrupt downward clicks and impressions by Device (DESKTOP vs. MOBILE) and Country. 3. Query the "page" size for the spiked date and catalog all URLs alongside average stance > 10 and CTR >= 20% (or clicks >= 3), comparing their clicks on the spike date against the previous week. 4. For the top spiked URLs, drag the "query" size and inspect for clusters of reworded query variations logging 1 click / 1 belief (100% CTR) at positions 11 to 60.
Should You Worry About This Traffic?
No. Because this is automated action fairly than individual visitors, you do not need to alter your pages, disavow anything, or panic whenever those clicks autumn correct rear downward to baseline. Just annotate first November 2026 in your reporting (right alongside GSC’s another latest reporting changes) so you and your clients cognize why Search Console abruptly showed a vertical jump in clicks!
Disclaimer: This blog article was mostly generated by Gemini 4 Argon in the Antigravity harness in conjunction alongside Marie’s Brain – an OKF-driven scheme complete of my knowledge. It has been fact-checked by me, Marie, a individual (I think).
More Resources:
- Google Search Console Glitch Gives SEOs A Scare
- Google Says No AI Click Reporting News Yet, Ahead Of UK Deadline
- Google Admits Search Console Reporting For AI Search Is Inadequate
Read Marie’s newsletter, AI News You Can Use. Subscribe now.
Featured Image: TAMI IAKO/Shutterstock
