Search visibility report

2026-08-15 Search Visibility Report

This dated checkpoint separates confirmed indexing, measured search demand, crawler access, analytics, and still-unverified answer-engine citations. It supersedes the August 3 operating snapshot without rewriting the earlier report.

Direct answer

AI Growth Bench is technically discoverable and 19 of its 23 submitted public URLs were indexed in the August 15 inspection snapshot. The Traffic Playbooks hub and all three child playbooks are now indexed, resolving the previous discovery gap. Search visibility remains small: Google Search Console recorded 145 impressions and no clicks from July 18 through August 14, while the domain-matched GA4 property recorded two organic sessions in the same 28-day window and none in the latest seven days. Server logs confirm visits from Googlebot, Bingbot, OAI-SearchBot, ChatGPT-User, PerplexityBot, ClaudeBot, and Applebot. These are crawl and discovery signals, not proof that an AI answer cited the site. The next priority is improving query-to-page fit, earning relevant external references, and recording displayed citations or explicit misses before claiming GEO visibility.

Published 2026-08-15 | Last reviewed 2026-08-15

Indexed URLs

19 / 23

Google URL Inspection snapshot for sitemap HTML routes on 2026-08-15.

GSC impressions

145

2026-07-18 through 2026-08-14; zero clicks.

Organic sessions

2

Domain-matched GA4 property in the same 28-day window.

Playbooks indexed

4 / 4

Hub plus all three child playbooks.

Verified AI citations

0

No displayed source URL has been captured yet.

Index coverage

Traffic Playbooks cluster

Confirmed

Hub and three child pages indexed

The August 3 child-page discovery gap is resolved. Future checks should measure impressions, clicks, referrals, and citations rather than repeatedly requesting indexing.

August 15 inspection set

Measured

19 of 23 inspected URLs indexed

The four URLs still unknown in this snapshot are /client-report, /evidence-log, /system, and /programmatic-seo/ai-agent-workflow-audit.

Technical crawl surface

Confirmed

Healthy

Public checks passed for HTTPS, redirects, canonical tags, crawler files, sitemap output, structured data, internal links, and production responses.

Channel evidence

Google Search Console

Measured

145 impressions, 0 clicks

The latest complete seven-day window produced 32 impressions, compared with 38 in the preceding seven days. Demand exists, but no query has yet converted into a click.

Google Analytics 4

Measured

2 organic sessions

The report used AI Growth Bench property 539587380 and measurement stream G-H70MB3LJL6. The latest seven days recorded no organic sessions.

Search and AI crawlers

Confirmed

Active crawl evidence

Seven-day server logs included Googlebot, Bingbot, OAI-SearchBot, ChatGPT-User, PerplexityBot, ClaudeBot, and Applebot traffic. Crawl access does not prove ranking or citation.

Answer-engine citations

Pending

Not yet verified

ChatGPT and Grok recognized the project in earlier manual checks, but no current displayed citation URL has been captured for ChatGPT, Gemini, Perplexity, Grok, or Google AI Overview.

Content priorities

  1. 1.Strengthen the Programmatic SEO hub so it answers quality, architecture, and measurement questions instead of functioning mainly as a status table.
  2. 2.Turn the AI Agent Workflow Audit into a complete, source-backed operating checklist with an original audit visual and visible review date.
  3. 3.Use existing indexed playbooks in relevant public distribution and job-application contexts; record the referring URL and resulting sessions instead of adding a large batch of pages.
  4. 4.Rewrite titles or lead sections only after GSC exposes query-level impressions that show a real mismatch between the search phrase and the current page promise.

Next actions

  1. 1.Deploy the evidence refresh and the two strengthened programmatic SEO pages after local verification.
  2. 2.After deployment, inspect only materially changed high-value URLs; do not repeatedly request indexing for the already indexed playbook cluster.
  3. 3.Publish one relevant external reference to an indexed playbook and record the source URL, date, landing page, sessions, and follow-up outcome.
  4. 4.Run the fixed answer-engine prompt set and capture the exact displayed source URL or an explicit no-citation result.
  5. 5.Review GSC page and query data after the next complete seven-day window before deciding whether to add more long-tail pages.

Evidence boundaries

Indexing status comes from Google URL Inspection and is a point-in-time snapshot, not a ranking guarantee.

Search demand comes from Google Search Console; analytics comes only from the domain-matched AI Growth Bench GA4 property.

Crawler user agents in server logs prove requests reached the site, not that a response ranked, appeared in an answer, or was cited.

AI citation status remains pending until a result visibly displays aigrowthbench.com or a canonical page URL as a source.