Google’s Generative AI Report Is Expanding in Search Console — and Cloudflare’s September 15 Deadline Affects Everything You’re About to Track

digital interactive web development hero image

Two Moving Parts, One Narrow Window

Most WordPress site owners are still waiting on the Generative AI tab in Search Console. Some have had it since June. What matters now is not the rollout order — it is understanding what the report does and does not measure before Cloudflare quietly changes the defaults on the crawlers feeding Google’s AI answers.

What the Generative AI Performance Report Actually Shows

Google launched the dedicated Generative AI performance report in Search Console on June 3, 2026, initially as a direct response to the UK Competition and Markets Authority mandate under the Digital Markets Act. The rollout was limited to a subset of UK-based properties first. By August 11, the report was appearing across a significantly larger pool of Search Console properties globally — still not universal, but expanding fast.

The report lives under Performance → Generative AI in the left-hand navigation. It separates AI-specific impression data into its own dedicated view, pulling it out of the standard Performance report where it was previously buried with no way to isolate it. Historical data goes back to May 18, 2026 only. There is no retroactive backfill.

What it measures:

  • Impressions for AI Overviews, AI Mode, and generative features in Google Discover
  • Pages — which specific URLs are being cited inside AI-generated answers
  • Countries and Devices breakdowns
  • Date trends at hourly, daily, weekly, or monthly granularity

What it does not measure: clicks. No CTR, no click data, no query-level breakdown. That gap is real. Industry research puts organic CTR on AI Overview queries somewhere between 0.61% and 2.4% depending on the study period — structurally lower than standard organic results. A page can accumulate thousands of AI impressions and drive almost no measurable session traffic. Pair the GSC report with GA4 or your host’s raw logs. Reading AI impressions in isolation is how teams convince themselves they are winning while conversions flatline.

One terminology distinction worth getting right before touching any settings: the opt-out control added alongside this report (under Settings → Search generative AI) blocks your content from appearing in AI Overviews, AI Mode, and generative Discover features. It does not touch your standard organic rankings. It is also entirely separate from Google-Extended, which governs whether Google trains its models on your content. These are two different switches with two different scopes.

Cloudflare’s September 15 Deadline

On July 1, 2026, Cloudflare reclassified all AI crawler traffic into three behavioral categories: Search (indexing your content to answer questions later), Agent (real-time automated activity on a user’s behalf — an AI assistant fetching your pricing page), and Training (bulk content collection for model training or fine-tuning). Starting September 15, new defaults apply.

For new domains joining Cloudflare on or after September 15: Training and Agent crawlers are blocked by default on pages Cloudflare classifies as displaying ads. Search stays allowed.

For existing free-tier customers: the same defaults activate automatically on September 15 unless you configure your settings before that date. Existing paid (non-Enterprise) zones with configurations already in place are not automatically changed.

The critical catch is multi-purpose crawlers. Googlebot crawls for both search indexing and AI training under a single combined user-agent string. Blocking Training means Cloudflare enforces that restriction across Googlebot’s full combined behavior. You can inadvertently affect indexing on ad-supported pages without intending to. Cloudflare’s own Radar data for June 2026 illustrates exactly why publishers are drawing these lines: Anthropic’s crawl-to-referral ratio sat at approximately 4,580:1, OpenAI at 848:1. Google came in at 5:1. The disparity is structural. Bot traffic has surpassed human traffic on the internet for the first time — that is the context in which Cloudflare is setting September 15 as a deadline.

If your WordPress site runs AdSense, Mediavine, Ezoic, or any display ad network and you are on Cloudflare’s free tier, this default applies to your property in 26 days.

What to Check This Week on a WordPress Site Using Cloudflare

The two silent failure modes if you do nothing: Training crawlers get blocked on your ad pages (which may be fine, depending on your content monetization strategy), or Agent crawlers get blocked, cutting off AI assistants that users actively send to your site to fetch product details, service descriptions, or WooCommerce pricing. The second failure is invisible until a user reports it or you notice a pattern in referral logs.

Two actions, both under 15 minutes:

1. Search Console check. Open your property and look in the Performance section for the Generative AI tab. If the full report is not yet available, go to Settings → Search generative AI regardless — the opt-out toggle may be accessible even before the impression report appears for your property. Make a deliberate choice about that setting before defaulting into either direction.

2. Cloudflare bot audit. Log into your Cloudflare dashboard, select your domain, go to Security → Bots → AI Scrapers and Crawlers. Review your current settings for each of the three categories (Search, Agent, Training). If you previously enabled the legacy “Block AI Bots” toggle, confirm that Googlebot is not caught under a Training block — this is the specific configuration error Cloudflare has flagged as the most common oversight. Changes take effect immediately.

Neither action requires a developer. Both require a decision before September 15.

The Measurement Gap Nobody Is Talking About

The GSC Generative AI report shows impressions. Cloudflare’s new defaults can silently alter which crawlers reach your ad pages. If Training or Agent bots are blocked before Google finalizes its AI Overview citations, you may see impression counts drop without an obvious cause in Search Console. The report will show the outcome. It will not show the infrastructure decision that caused it.

AI Overviews average 13.34 source citations per response as of early 2026, up from approximately 6.8 in 2024. Brands cited inside AI Overviews receive 35% more organic clicks and 91% more paid clicks than non-cited brands appearing on the same SERP. The visibility has real downstream value. Losing it to an unreviewed Cloudflare default is an entirely avoidable outcome.

Sources: