The Web’s New Immune System: How Google’s Parameter Switch and AI Overviews Triggered the First Real Agent Throttle
Stock Psycho Investigative Analysis
Disclaimer: This is my working theory based on verifiable events and public reports. The correlations are real. The causal chain described here is a plausible interpretation, not a confirmed fact.
The first sign was the crash. In late September 2025, multiple dashboards I monitor flatlined almost in unison. Clicks dove. Impressions collapsed. The same pattern appeared in third party panels tracking global platforms. It did not look like drift or seasonality. It looked synchronized and unusually fast.
At first I suspected AI Overviews alone. That would explain lower click through on affected queries. It would not explain a near simultaneous fall across unrelated domains and surfaces. The timing and the shape were too clean. The more likely story is a layered shift. A discovery choke at the search layer. A behavior shift at the results layer. And a new authentication wall at the network edge. Put together, that looks like the web building an immune response to automated agents.
Key facts
- Google disabled the num=100 search parameter in September 2025. Bulk SERP retrieval fell from 100 results to 10 by default.
- Independent reporting shows lower click through when AI summaries appear compared with classic results pages.
- Automated traffic has been estimated near or above half of total web requests in recent years.
- CDNs introduced agent verification and throttling tools that can meter or block unverified automation at the edge.

Figure 1. Coordinated decline visible in analytics, Google Search Console. Late September 2025.

Figure 2. GLOBAL Synchronized pattern across unrelated platforms, Similarweb. Late September 2025.
What changed and why it matters
1) The moment the map broke
Google disabled the num=100 parameter in early September. Rank trackers and scrapers lost easy access to full result sets. Discovery pipes shrank. Visibility models that relied on those responses shifted down even when page one ranking stayed stable.
2) AI Overviews compress click through
When summaries appear, fewer people click out to publishers. That is measurable in independent studies. Even small exposure can move total click volume for certain query classes. It contains attention inside the results page.
3) When bots vanish, graphs collapse
Automated requests account for a large share of the web. Legitimate crawlers, SEO tools, price scrapers, and now AI agents. If discovery is throttled and agents crawl less, that synthetic layer drops out of aggregate metrics. Dashboards that blend human and automated activity will fall faster than real human demand.
4) The firewall forming at the edge
CDN providers introduced agent verification and bot authentication. Sites can segment verified bots from unknown agents and apply allow, meter, or deny rules. That is a practical gate for machine traffic. Combined with search layer changes, it becomes a double lock. One at discovery. One at access.

Figure 3. CrUX field data indicating reddit.com performance stress during the same window. September to October 2025.
Explainer: what is Really Simple Licensing
Really Simple Licensing, or RSL, is an open standard that lets publishers declare machine readable licensing terms for AI and crawler use. Instead of a simple allow or disallow in robots.txt, RSL can express terms like attribution required, pay per crawl, subscription, or pay per inference. RSL is voluntary signaling by itself. The enforcement power arrives when RSL integrates with infrastructure. A CDN can check whether a requesting agent honors the license and then serve, meter, or block. In a tokenized future, this becomes the economic gate that sits beside the technical gates described above.
How a traffic crash appears in dashboards
Component
Observed change
Why dashboards can fall fast
Evidence vs theory
SERP data pipe num=100 removal
Fewer rows per fetch. Rank trackers undercount long tail visibility.
Visibility indices decline even if ranking is stable on page one or two.
Event confirmed. The throttle interpretation is my theory.
UX layer AI Overviews
Lower click through when summaries appear. Rare link clicks inside summaries.
Even small exposure moves total click volume for summary eligible queries.
Click effect reported. Treating it as a soft moat is my theory.
Automation mix bots and agents
Bots represent a large share of requests. Post change, many bots discover less and crawl less.
Analytics that under filter bots show larger declines than human only segments.
Bot share verified. Amplification mechanism is my theory.
Edge controls signed agents and pay per crawl
CDNs can fingerprint and meter AI agents. Sites can charge or block.
Agent swarms face new friction, reducing synthetic traffic while preserving verified bots.
Features exist. Framing them as an agent firewall is my theory.

Figure 5. How RSL Transactions Work
What this likely means
- The free crawl era is ending. Expect tokenized or paid access for agents that need bulk retrieval.
- Separate human and bot time series in GA4 and server logs to avoid false alarms.
- Measure click through separately where AI summaries appear and where they do not.
- Adopt edge policies for signed agents, verified bots, and pay per crawl.
Measurement playbook
- Decompose traffic: build strict bot rules and a human only view. Track both week over week.
- CTR study by class: compare impression and CTR shifts on summary eligible queries against control queries.
- Crawl telemetry: monitor Googlebot and third party crawler volumes at the edge to confirm structural declines after mid September.
- Rank tracker sanity checks: manually sample live results to detect artifacts from the parameter change.
Status check: parts of this story are confirmed facts, such as the parameter removal, the CTR compression with summaries, and the launch of agent verification at the edge. The interpretation that these moves form a coordinated throttle on autonomous agents is my theory. It is consistent with the evidence and testable with better segmentation and telemetry.
Sources
- Pew Research on AI Overviews and user behavior
- Cloudflare posts on verified bots and agent authentication
- GA4 community threads on bot spikes and attribution issues
- Imperva Bad Bot Report on automated traffic share
- SEO practitioner discussions of Google removing num=100
- Trade coverage of AI Overviews and publisher traffic
- RSL standard documentation and legal commentary
These links provide factual context. The synthesis into an agent throttle theory is original analysis.