Search visibility report

2026-09-04 Search Visibility Report

This checkpoint keeps property impressions, URL impressions, clicks, sessions, indexing, crawler requests, mentions, citations, displayed source URLs, and referrals as distinct evidence classes.

Direct answer

AI Growth Bench remains technically healthy, but its main constraint is discovery and click-through rather than crawlability. Google Search Console recorded 189 property-level impressions and no clicks from August 5 through September 1, 2026. The latest complete seven-day window produced 61 impressions, up from 35 in the preceding seven days, while page-dimension rows represented 237 URL impressions across 21 pages. Google URL Inspection found 24 of 29 inspected URLs indexed and five unknown. The domain-matched GA4 property 539587380 recorded two sessions in the latest available 28-day window and none in the latest seven days. The fixed 30-check GEO baseline is complete: three answers mentioned AI Growth Bench and two displayed an aigrowthbench.com source, all for the branded definition prompt; the 27 non-brand checks produced no mention or citation. The next test is the same 30 checks on September 14 after a synchronized on-site treatment, with external distribution still a separate unexecuted action.

Published 2026-09-04 | Last reviewed 2026-09-04

Indexed URLs

24 / 29

Google URL Inspection snapshot captured on 2026-09-04; five inspected URLs were unknown.

GSC impressions

189

Property-level total for 2026-08-05 through 2026-09-01; zero clicks.

URLs with impressions

Page-dimension rows represented 237 URL impressions in the same window.

Organic sessions

AI Growth Bench GA4 property 539587380 for 2026-08-07 through 2026-09-03; latest seven days zero.

GEO baseline complete

30 / 30

Three mentions and two displayed citations, all on the branded definition prompt.

Index coverage

September 4 inspection set

Measured

24 of 29 inspected URLs indexed

The five unknown URLs were /results, /programmatic-seo/ai-agent-workflow-audit, /geo-page-check, /client-report, and /system.

Query-bearing clusters

Confirmed

GEO, automation, and programmatic SEO pages exposed

Search Console already shows impressions for the GEO checklist, growth automation workflow, and programmatic SEO topics; consolidation is more justified than adding generic pages.

Technical crawl surface

Confirmed

Healthy

The August 28 production audit passed 29 public pages, 103 links, tests, lint, the 42-route build, production dependency audit, and PageSpeed 98 mobile / 100 desktop.

Channel evidence

Google Search Console

Measured

189 impressions, 0 clicks

The latest complete seven days produced 61 impressions versus 35 in the preceding seven days. The increase is directional discovery evidence, not a click or conversion result.

Google Analytics 4

Measured

2 sessions in 28 days; 0 in 7 days

Only the correct AI Growth Bench property 539587380 is used. Both latest-window sessions and pageviews were on the homepage.

Answer-engine baseline

Measured

3 mentions; 2 displayed citations

All three mentions occurred for the branded prompt. Twenty-seven non-brand prompt-engine cells produced neither a mention nor a citation.

Referrers and crawlers

Pending

Not refreshed in this checkpoint

The August 28 server-log audit found no external, search, or AI referrer. Historical crawler user-agent requests remain request evidence only and are not carried forward as a current measurement.

Content priorities

1.Consolidate the thin /programmatic-seo/quality-gates experiment into the stronger Programmatic SEO Quality Gates playbook so two URLs do not compete for one intent.
2.Keep the GEO checklist, AI growth automation workflow, and programmatic SEO cluster as the main search-demand portfolio instead of publishing more broad utility pages.
3.Narrow the index portfolio by keeping utilities and historical reports accessible but noindex-follow and out of discovery feeds.
4.Use the September 14 fixed-protocol retest to measure whether synchronized entity and evidence updates changed answer-engine behavior.

Next actions

1.Verify the synchronized local candidate with tests, build, crawl, links, redirects, noindex directives, and desktop/mobile rendering before requesting deployment.
2.After deployment is separately authorized, treat the synchronized release as the post-baseline on-site treatment and preserve its release identifier.
3.Run the exact ten prompts across ChatGPT, Gemini, and Perplexity on 2026-09-14 and compare all 30 cells without substituting models or wording.
4.Create one relevant external reference to an already exposed playbook only with separate publication authorization, then measure referral and later query movement.

Evidence boundaries

The 189-impression figure is the property-level Search Console total. The 237 page-dimension impressions can be higher because multiple site URLs may receive impressions in one search result.

Visible query rows account for 54 impressions and visible query-page rows for 56; Google may omit low-volume rows for privacy.

Indexing status comes from the Google URL Inspection API on 2026-09-04 and describes the inspected production URLs before this local consolidation candidate.

Analytics uses only AI Growth Bench GA4 property 539587380. It is not mixed with AI Trend Prompt Hub or another site.

A mention names the project; a citation or displayed source URL visibly attributes the answer; a crawler request and an AI referral session are separate evidence classes.