2026-09-04
Discovery Increased, but Clicks and Non-Brand GEO Visibility Remain Zero
Search exposure increased to 61 impressions in the latest complete week, but Google clicks and recent GA4 sessions stayed at zero. The fixed GEO baseline completed 30 of 30 checks, with three mentions and two displayed citations limited to the branded definition prompt.
Open current reportHypothesis
If the site consolidates overlapping intent, narrows its index portfolio, and synchronizes its current entity and evidence surfaces, the September 14 fixed-protocol retest will provide a cleaner measure of on-site GEO improvement than publishing more generic pages.
Action
Refreshed GSC property, page, query, and query-page evidence; checked the correct GA4 property; inspected 29 production URLs; verified the completed 30-check baseline; and prepared a local consolidation candidate without deploying, submitting URLs, using paid APIs, or publishing externally.
Result
GSC recorded 189 property-level impressions and 0 clicks from August 5 through September 1. The latest complete seven days reached 61 impressions versus 35 in the preceding seven days. URL Inspection found 24 of 29 inspected URLs indexed. GA4 recorded two sessions in the latest available 28-day window and none in the latest seven days. The GEO baseline recorded three mentions and two displayed citations, all for the branded prompt; 27 non-brand cells were misses.
Next test
After a separately authorized deployment, repeat the same ten prompts across the same three answer engines on September 14 and compare every cell against the preserved baseline.
Evidence
- GSC 2026-08-05 to 2026-09-01: 189 property-level impressions and 0 clicks.
- Page dimensions: 237 URL impressions across 21 pages; visible queries: 54 impressions.
- GSC latest complete seven days: 61 impressions; preceding seven days: 35 impressions.
- AI Growth Bench GA4 property 539587380: 2 sessions in 28 days and 0 in 7 days.
- URL Inspection 2026-09-04: 24 of 29 inspected URLs indexed; five unknown.
- GEO baseline: 30 of 30 complete, 3 mentions, 2 displayed citations, and 27 non-brand misses.
Checked URLs
- https://aigrowthbench.com/
- https://aigrowthbench.com/results
- https://aigrowthbench.com/geo-bench/citation-benchmark
- https://aigrowthbench.com/geo-bench/geo-content-checklist
- https://aigrowthbench.com/playbooks/ai-growth-automation-workflow
- https://aigrowthbench.com/playbooks/programmatic-seo-quality-gates
- https://aigrowthbench.com/programmatic-seo/quality-gates
- https://aigrowthbench.com/reports/2026-09-04-search-visibility-report
Wins
- Latest complete weekly impressions increased from 35 to 61.
- Twenty-four of 29 inspected production URLs are indexed.
- All 30 baseline cells contain explicit observed outcomes rather than inferred or pending claims.
- The strongest quality-gate URL already ranks better than its thinner duplicate, giving a data-backed consolidation target.
Risks
- Search Console still records zero clicks.
- GA4 recorded zero sessions in the latest seven days.
- Twenty-seven non-brand GEO cells produced no mention or citation.
- No external discovery experiment has been executed, and current server referrer/crawler evidence was not refreshed in this checkpoint.
Next
- Verify the local redirect, noindex-follow directives, sitemap and feed filtering, current report links, build, crawl, and responsive output.
- Request deployment separately and record the release identifier if approved.
- Run the unchanged 30-check protocol on September 14.
- Prepare one relevant external reference to an existing query-bearing playbook, but do not publish it without separate authorization.
2026-08-24
Index Coverage Improved, Search Demand Flat
Google now indexes 22 of 28 public URLs, but the latest complete seven-day window remained flat at 47 impressions and produced no clicks. Two organic sessions reached the homepage, while the 30-check answer-engine baseline remains pending.
Open historical reportHypothesis
If the site concentrates on observed GEO checklist, growth workflow, and programmatic SEO queries, earns a relevant external reference, and completes the fixed answer-engine baseline, it can generate stronger discovery evidence without publishing more generic utility pages.
Action
Rechecked the production release, all sitemap routes, public links, metadata, structured data, security headers, GSC date/page/query data, URL Inspection coverage, the domain-matched GA4 property, server crawler logs, GEO Page Check, benchmark status, PageSpeed, tests, lint, and production dependencies.
Result
Twenty-two of 28 public URLs are indexed. GSC recorded 158 property-level impressions and no clicks from July 26 through August 22, with 47 impressions in each of the latest two complete seven-day windows. Page dimensions represented 192 URL impressions across 17 pages. GA4 recorded two organic homepage sessions. Valid pages received search and AI crawler requests, but no current fixed-prompt citation or AI referral session was verified.
Next test
Deploy the evidence refresh, improve the three query-bearing content clusters, publish one relevant external reference, complete the 30 baseline checks, and compare GSC clicks, landing pages, referrals, and displayed source URLs after the next complete seven-day window.
Evidence
- GSC 2026-07-26 to 2026-08-22: 158 property-level impressions and 0 clicks.
- Page dimensions: 192 URL impressions across 17 pages; visible query dimensions: 51 impressions.
- GSC latest seven days: 47 impressions; preceding seven days: 47 impressions.
- AI Growth Bench GA4 property 539587380: 2 organic sessions in 28 days and in the latest seven days.
- URL Inspection 2026-08-24: 22 of 28 public URLs indexed; six URLs remain unknown.
- PageSpeed mobile: performance 80, accessibility 100, best practices 100, SEO 100; LCP 4.7 seconds and CLS 0.
- GEO citation benchmark: 0 of 30 baseline observations complete; AI referral sessions: 0.
Checked URLs
- https://aigrowthbench.com/
- https://aigrowthbench.com/results
- https://aigrowthbench.com/geo-page-check
- https://aigrowthbench.com/geo-bench/citation-benchmark
- https://aigrowthbench.com/geo-bench/geo-content-checklist
- https://aigrowthbench.com/playbooks/ai-growth-automation-workflow
- https://aigrowthbench.com/programmatic-seo
- https://aigrowthbench.com/programmatic-seo/ai-agent-workflow-audit
- https://aigrowthbench.com/reports
Wins
- Index coverage improved from 19 of 23 inspected URLs to 22 of 28 public URLs.
- The Results-loop case study, GEO citation benchmark, three Traffic Playbooks, Reports hub, and August 15 report are indexed.
- All 28 production sitemap pages passed status, canonical, H1, language, metadata, structured-data, and internal-link checks.
- The GEO Page Check returned 100/100 for the entity page and rejected external hosts before fetching.
Risks
- The latest complete seven-day GSC window was flat at 47 impressions and produced no clicks.
- Six public URLs remain unknown to Google.
- Only two organic sessions were measured, both on the homepage.
- All 30 answer-engine baseline cells remain pending, so crawler access still cannot be presented as current citation evidence.
Next
- Deploy the current evidence report after local verification and inspect only the new or still-unknown URLs.
- Improve the GEO checklist, AI growth workflow, and programmatic SEO pages around their observed query language and practical examples.
- Publish one relevant external reference to an indexed playbook and record the source URL plus resulting sessions.
- Run and capture the fixed ChatGPT, Gemini, and Perplexity baseline before the August 31 retest date.
2026-08-15
Index Coverage Resolved, Demand Still Small
Google now indexes the Traffic Playbooks hub and all three child pages, while 19 of 23 inspected sitemap URLs are indexed overall. The site remains discoverable but has not yet converted 145 recent impressions into a click or sustained organic sessions.
Open historical reportHypothesis
If the existing indexed pages better match operational search intent and earn relevant external references, the site can produce measurable clicks and referrals without expanding into a large set of thin pages.
Action
Rechecked production health, sitemap routes, GSC page and date evidence, domain-matched GA4 data, URL Inspection coverage, search and AI crawler logs, content depth, and current dependency advisories.
Result
Nineteen of 23 sitemap HTML routes are indexed, including all four Traffic Playbook URLs. GSC recorded 145 impressions and no clicks from July 18 through August 14. The correct GA4 property recorded two organic sessions in that window and none in the latest seven days. Search and AI crawlers reached the site, but no displayed AI citation URL has been captured. The next bottleneck is page usefulness, query fit, and external discovery rather than crawler access.
Next test
Strengthen the Programmatic SEO hub and AI Agent Workflow Audit, distribute one indexed playbook in a relevant context, and compare GSC queries, referrals, and answer-engine citations after the next complete seven-day window.
Evidence
- GSC 2026-07-18 to 2026-08-14: 145 impressions and 0 clicks.
- GSC latest seven days: 32 impressions; preceding seven days: 38 impressions.
- AI Growth Bench GA4 property 539587380: 2 organic sessions in 28 days and 0 in the latest seven days.
- URL Inspection 2026-08-15: 19 of 23 sitemap URLs indexed; all four Traffic Playbook URLs indexed.
- Unknown URLs: /client-report, /evidence-log, /system, and /programmatic-seo/ai-agent-workflow-audit.
- Server logs show search and AI crawler access, while verified displayed AI citation count remains zero.
Checked URLs
- https://aigrowthbench.com/
- https://aigrowthbench.com/playbooks
- https://aigrowthbench.com/playbooks/ai-growth-automation-workflow
- https://aigrowthbench.com/playbooks/programmatic-seo-quality-gates
- https://aigrowthbench.com/playbooks/geo-visibility-audit-checklist
- https://aigrowthbench.com/programmatic-seo
- https://aigrowthbench.com/programmatic-seo/ai-agent-workflow-audit
Wins
- The complete Traffic Playbooks cluster is submitted and indexed.
- Nineteen of 23 inspected sitemap URLs are indexed.
- Googlebot, Bingbot, OAI-SearchBot, ChatGPT-User, PerplexityBot, ClaudeBot, and Applebot reached public pages.
- Production crawl, metadata, structured data, canonical, feed, and crawler-policy checks remain healthy.
Risks
- The 145 Search Console impressions produced no clicks.
- The domain-matched GA4 property recorded no organic sessions in the latest seven days.
- Four sitemap URLs remained unknown at the inspection checkpoint.
- Crawler requests are not evidence of answer-engine citations, and no displayed source URL has been captured.
Next
- Deploy the evidence correction and the two stronger programmatic SEO pages after verification.
- Use one indexed playbook in a relevant external post or application and record the referring URL plus resulting sessions.
- Repeat the answer-engine prompt set and record citations or explicit misses.
- Use query evidence, not page-count targets, to choose the next long-tail page.
2026-08-03
Search Visibility and GEO Evidence Check
Search impressions improved from a very small base, but the site still has almost no valid organic traffic and three child playbooks that were unknown to Google at the inspection checkpoint. The same-day release closed the identified on-page GEO evidence gaps.
Review the publication gateHypothesis
If the existing child playbooks become more distinct, source-backed, and externally referenced, Google can discover them and the site can earn non-brand impressions without publishing more thin URLs.
Action
Rechecked the server and public routes, crawled all 23 sitemap HTML pages, queried GSC and the domain-matched GA4 property, inspected the playbook cluster, ran PageSpeed, strengthened six priority pages, and reran public content and GEO extraction checks.
Result
The service, redirects, crawler files, sitemap, canonical tags, structured data, internal links, and title uniqueness are healthy. GSC recorded 89 impressions and 1 click through 2026-07-31; the latest seven days reached 35 impressions but no clicks. The correct GA4 property recorded 3 organic sessions in 28 days and none in the latest seven days. The playbook hub is indexed, but GSC still reported all three child playbooks as unknown after the same-day content release. All six strengthened pages score 82 in public GEO analysis and expose an optimal answer block, visible attribution, sources, and a content visual. IndexNow accepted a targeted submission for the three child playbooks. A post-release PageSpeed mobile lab run scored 99 with 2.2 second LCP; no CrUX field data is available.
Next test
Request Google recrawls only for the three strengthened child playbooks, then add one relevant external reference and compare the next complete seven-day window before publishing more URLs.
Evidence
- GSC 2026-07-06 to 2026-07-31: 89 impressions and 1 click.
- GSC 2026-07-25 to 2026-07-31: 35 impressions and 0 clicks; prior seven days: 17 impressions and 0 clicks.
- AI Growth Bench GA4 property 2026-07-06 to 2026-08-02: 3 organic sessions; latest seven days: 0.
- URL Inspection 2026-08-03: /playbooks indexed; three child playbooks unknown.
- Public crawl after release: 23 of 23 HTML URLs returned 200 with no duplicate title pair; six content-image instances appear across the strengthened pages.
- Public GEO analysis: all six strengthened pages scored 82 and each exposed one optimal 134-167 word answer block.
- Targeted IndexNow submission: api.indexnow.org returned HTTP 200 and Yandex returned 202 Accepted for the three child playbooks.
- Post-release PageSpeed mobile lab run: 99 performance, 2.2 second LCP, 0.9 second FCP, 57 millisecond TBT, and zero CLS; CrUX unavailable.
Checked URLs
- https://aigrowthbench.com/
- https://aigrowthbench.com/what-is-ai-growth-bench
- https://aigrowthbench.com/case-studies/ai-trend-prompt-hub
- https://aigrowthbench.com/geo-bench/geo-content-checklist
- https://aigrowthbench.com/playbooks
- https://aigrowthbench.com/playbooks/ai-growth-automation-workflow
- https://aigrowthbench.com/playbooks/programmatic-seo-quality-gates
- https://aigrowthbench.com/playbooks/geo-visibility-audit-checklist
Wins
- The latest complete seven-day GSC window produced 35 impressions, up from 17 in the prior seven days.
- Fourteen pages now have page-level impression evidence in the current GSC window.
- The Playbooks hub remains submitted and indexed with a matching canonical.
- The same-day release removed the duplicate title and added source-backed, review-attributed answer sections and original diagrams to six priority pages.
- IndexNow and Yandex accepted a targeted submission for the three materially changed child playbooks.
Risks
- The impression increase has not produced clicks or deeper organic landing sessions.
- All three child playbooks remain unknown to Google and have no GSC page-level impressions.
- Real citations in Gemini, Perplexity, ChatGPT, Grok, and Google AI features are still unverified after the content refresh.
- Mobile lab results varied from 78 before the release to 99 after it, and no CrUX field data exists yet to establish real-user performance.
Next
- Request indexing only for the three child playbooks that were still unknown at the inspection checkpoint.
- Publish one relevant external reference and run the same answer-engine prompt set with cited-source capture.
2026-07-28
Search Health and Playbook Discovery Check
The site is technically healthy and the Playbooks hub is now indexed, but the three child playbooks remain undiscovered and organic demand is still small.
Hypothesis
If the indexed hub supports three focused child pages with accurate evidence, targeted indexing follow-up, and one external reference, Google can discover the children without expanding the site with more low-signal pages.
Action
Crawled all 23 sitemap HTML URLs, checked redirects, metadata, structured data, internal links, Search Console performance, URL Inspection, and PageSpeed. Separated the duplicated quality-gate title and reconciled the public discovery status with current evidence.
Result
All 23 public HTML URLs return 200 with self-canonical metadata, one H1, valid JSON-LD, and internal outgoing links. PageSpeed scored 95 performance and 100 for accessibility, best practices, and SEO on mobile. GSC recorded 64 impressions and 1 click through 2026-07-25. The /playbooks hub is indexed, while its three child pages remain unknown. The original GA4 baseline was later withdrawn because the default report mapped to another site.
Next test
Deploy the corrected evidence, request indexing for only the three child playbooks, publish one relevant external reference to the strongest child page, and compare discovery plus page-level impressions after the next crawl window.
Evidence
- Public crawl: 23 of 23 sitemap HTML URLs returned 200 with required SEO structure.
- URL Inspection: /playbooks submitted and indexed; three child playbooks unknown on 2026-07-28.
- GSC 2026-06-30 to 2026-07-25: 64 impressions and 1 click.
- GA4 was excluded from this historical report after the property-to-domain mapping was validated on 2026-08-03.
- PageSpeed mobile: 95 performance, 100 accessibility, 100 best practices, and 100 SEO.
Checked URLs
- https://aigrowthbench.com/
- https://aigrowthbench.com/playbooks
- https://aigrowthbench.com/playbooks/ai-growth-automation-workflow
- https://aigrowthbench.com/playbooks/programmatic-seo-quality-gates
- https://aigrowthbench.com/playbooks/geo-visibility-audit-checklist
- https://aigrowthbench.com/programmatic-seo/quality-gates
- https://aigrowthbench.com/reports/2026-07-05-geo-visibility-report
Wins
- The public service, HTTPS redirect chain, sitemap, feeds, robots.txt, llms files, and 23 HTML routes are healthy.
- The Traffic Playbooks hub has moved from unknown to submitted and indexed.
- The site has measurable search and organic-session baselines instead of relying on availability checks alone.
Risks
- Three child playbooks still have no Google discovery evidence.
- Most organic sessions land on the homepage, so deeper portfolio pages have not earned meaningful demand yet.
- No reliable Perplexity, Gemini, or Google AI Overview citation has been captured.
Next
- Deploy this evidence correction and title fix.
- Request indexing only for the three unknown child playbooks.
- Publish one external reference to the strongest playbook instead of adding more pages.
- Run the GEO prompt set and save cited URLs or explicit misses.
2026-07-21
Index Coverage and Playbook Discovery Update
Refreshed Search Console evidence after the July crawl cycle and isolated the remaining discovery problem to the four-page Traffic Playbooks cluster.
Open historical GEO reportHypothesis
If already-indexed hub pages link to the playbooks with descriptive anchors and the changed pages publish truthful lastmod signals, Google will discover the cluster without expanding the site with more thin pages.
Action
Rechecked priority URLs in Google URL Inspection, reconciled public evidence with the current indexed state, audited the sitemap inventory, and prepared stronger contextual internal links for the playbook hub and child pages.
Result
The homepage, GEO report, GEO checklist, GEO benches, entity page, and AI Trend case study are indexed. Search Console recorded 77 impressions and 1 click across 11 pages in the reviewed 28-day window. The /playbooks hub and all three child playbooks remain unknown to Google.
Next test
Deploy the internal-link and lastmod update, resubmit sitemap and IndexNow signals, request indexing for the four playbook URLs, then compare URL Inspection and impression data after the next crawl window.
Evidence
- URL Inspection: homepage, GEO report, GEO checklist, GEO benches, entity page, and AI Trend case study are submitted and indexed.
- URL Inspection: /playbooks and three child playbooks are unknown to Google on 2026-07-21.
- GSC 2026-06-23 to 2026-07-18: 77 impressions and 1 click across 11 pages.
- Sitemap: 23 submitted HTML URLs, zero warnings, and zero errors.
Checked URLs
- https://aigrowthbench.com/
- https://aigrowthbench.com/reports/2026-07-05-geo-visibility-report
- https://aigrowthbench.com/geo-bench/geo-content-checklist
- https://aigrowthbench.com/case-studies/ai-trend-prompt-hub
- https://aigrowthbench.com/playbooks
- https://aigrowthbench.com/playbooks/ai-growth-automation-workflow
- https://aigrowthbench.com/playbooks/programmatic-seo-quality-gates
- https://aigrowthbench.com/playbooks/geo-visibility-audit-checklist
Wins
- The earlier GEO checklist and AI Trend case-study indexing gaps are resolved.
- All 23 sitemap HTML URLs return 200 with self-canonical metadata and gzip compression.
- The remaining crawl-discovery gap is narrow and measurable rather than site-wide.
Risks
- Google may still delay or decline indexing if the playbooks do not earn enough distinct demand or external signals.
- Indexing does not guarantee impressions, clicks, or AI citations.
- Perplexity, Gemini, and Google AI Overview citation claims remain unverified until cited URLs are captured.
Next
- Request indexing for /playbooks and its three child pages after deployment.
- Publish one external reference to the most useful playbook instead of creating more pages immediately.
- Run the GEO prompt set and save cited URLs or explicit misses.
- Review GSC page and query data after the next crawl window.
2026-07-05
GEO Visibility Report
At the July 5 checkpoint, AI Growth Bench separated confirmed technical readiness from still-pending AI citation evidence.
Open historical GEO reportHypothesis
If entity pages, GEO pages, crawler files, and the current report are internally linked and submitted, answer engines will have clearer sources to cite once indexing and external references catch up.
Action
Inspected six priority URLs with Google URL Inspection, reviewed robots.txt and llms.txt, added a current GEO visibility report, and reinforced the entity/About pages with citation-ready relationship facts.
Result
At that checkpoint, four priority pages were submitted and indexed; one GEO checklist URL was unknown to Google; and the AI Trend case study had been crawled but was not indexed yet. The July 21 report above supersedes those index states.
Next test
After requesting indexing for the missing checklist and waiting for crawl refresh, run the same prompts in Gemini, Perplexity, ChatGPT, Grok, and Google Search while capturing cited URLs.
Evidence
- URL Inspection: homepage submitted and indexed.
- URL Inspection: /what-is-ai-growth-bench submitted and indexed.
- URL Inspection: /geo-bench submitted and indexed.
- URL Inspection: /geo-visibility-bench submitted and indexed.
- URL Inspection: /geo-bench/geo-content-checklist unknown to Google.
- URL Inspection: /case-studies/ai-trend-prompt-hub crawled but currently not indexed.
- robots.txt and llms.txt reviewed as crawler and AI-readable discovery sources.
Checked URLs
- https://aigrowthbench.com/
- https://aigrowthbench.com/what-is-ai-growth-bench
- https://aigrowthbench.com/geo-bench
- https://aigrowthbench.com/geo-visibility-bench
- https://aigrowthbench.com/geo-bench/geo-content-checklist
- https://aigrowthbench.com/case-studies/ai-trend-prompt-hub
- https://aigrowthbench.com/reports/2026-07-05-geo-visibility-report
Wins
- The homepage, entity definition page, GEO Bench, and GEO Visibility Bench are indexed.
- robots.txt allows major AI crawlers and llms.txt exposes canonical project context.
- The site now has a public current report that explains what is confirmed, what is missing, and what prompt set to run next.
Risks
- At the July 5 checkpoint, the GEO checklist URL was unknown to Google and needed manual indexing follow-up.
- At the July 5 checkpoint, the external case study was crawled but not indexed.
- Perplexity, Gemini, and Google AI Overview should not be claimed until cited-source evidence is captured.
Next
- Request indexing for https://aigrowthbench.com/geo-bench/geo-content-checklist.
- Retest https://aigrowthbench.com/case-studies/ai-trend-prompt-hub after Google refreshes.
- Run the report prompt set across answer engines and save source panels or cited URLs.
- Publish one external post linking to the entity page and the AI Trend case study.
2026-05-24
Search Discovery Expansion
Added low-cost discovery surfaces that help search engines, feed readers, and AI crawlers find the public portfolio before there is enough traffic data to filter by quality.
Hypothesis
If the site exposes a canonical XML sitemap, linked text/feed discovery endpoints, AI-readable context, and IndexNow notifications, more crawlers can discover updates earlier than relying on one route alone.
Action
Added /search-discovery, /sitemap.txt, /feed.xml, /rss.xml, /atom.xml, an IndexNow key file, and a sitemap-driven IndexNow submit script. The later technical review consolidated robots.txt to advertise only the canonical XML sitemap while keeping the other endpoints linked publicly.
Result
The site now has multiple public discovery paths ready for Google, Bing, Yandex, feed readers, and AI crawlers. IndexNow submission status is recorded separately after the deployed key file is verified.
Next test
Submit the discovery endpoints in webmaster tools, then compare discovered URL counts, crawl dates, and first impressions after search engines refresh.
Evidence
- New route: https://aigrowthbench.com/search-discovery.
- New feed routes: /feed.xml, /rss.xml, and /atom.xml.
- New fallback sitemap: /sitemap.txt.
- New IndexNow key file at the site root.
- robots.txt advertises only sitemap.xml; the Search Discovery page exposes sitemap.txt, feed.xml, and atom.xml without presenting them as XML sitemaps.
Checked URLs
- https://aigrowthbench.com/search-discovery
- https://aigrowthbench.com/sitemap.xml
- https://aigrowthbench.com/sitemap.txt
- https://aigrowthbench.com/feed.xml
- https://aigrowthbench.com/atom.xml
- https://aigrowthbench.com/robots.txt
Wins
- Discovery no longer depends only on /sitemap.xml.
- The public discovery page makes the SEO operations layer visible as portfolio evidence.
- IndexNow is available without storing any API key, password, cookie, or session token.
- RSS and Atom feeds create another route for Google-compatible feed submission and feed readers.
Risks
- Discovery does not guarantee indexing, ranking, or useful traffic.
- Bing, Yandex, and Google webmaster dashboards still require Alex's logged-in accounts for verification and monitoring.
- IndexNow should be used for new or meaningfully updated URLs, not spammed repeatedly.
Next
- Submit only sitemap.xml in Google Search Console and keep the feed endpoints discoverable through HTML and alternate links.
- Add the domain in Bing Webmaster Tools and check the IndexNow tab after submission.
- Add the domain in Yandex Webmaster if Yandex visibility is useful for this portfolio.
2026-05-24
Technical SEO and Portfolio Module Expansion
Turned the Codex SEO audit into visible portfolio proof by fixing canonical and sitemap issues, adding security headers and citation-ready homepage copy, then publishing four client-facing modules.
Hypothesis
If the site exposes real audit deltas and service modules, it will be easier for remote clients or employers to evaluate practical SEO/GEO execution.
Action
Added self-canonical metadata, cleaned sitemap output, added baseline security headers, strengthened homepage GEO copy, created SEO Audit Bench, GEO Visibility Bench, Content Machine, and Client Report pages, then deployed the update.
Result
Codex SEO scores improved: technical 79 to 87, sitemap 73 to 100, GEO 57 to 77, and content 42 to 59. Linkinator scanned 35 links and found all 200-status links.
Next test
Run PageSpeed or Unlighthouse for real performance evidence, then add the result to SEO Audit Bench and the next weekly report.
Evidence
- Codex SEO technical score: 79 -> 87.
- Codex SEO sitemap score: 73 -> 100.
- Codex SEO GEO score: 57 -> 77.
- Codex SEO content score: 42 -> 59.
- Linkinator: 52 links scanned, all 200.
Checked URLs
- https://aigrowthbench.com/
- https://aigrowthbench.com/seo-audit-bench
- https://aigrowthbench.com/geo-visibility-bench
- https://aigrowthbench.com/content-machine
- https://aigrowthbench.com/client-report
- https://aigrowthbench.com/sitemap.xml
Wins
- Canonical mismatch and deprecated sitemap tag issues were removed.
- Security header score moved to a clean baseline.
- The homepage now includes an optimal-length citation-ready passage.
- Four service-style portfolio modules are live and linked from the homepage, navigation, sitemap, and llms files.
Risks
- CWV remains a heuristic warning until PageSpeed, CrUX, or Unlighthouse evidence is captured.
- IndexNow has been moved into the discovery layer; dashboard monitoring still requires webmaster tools access.
- Search Console evidence is still pending and should not be claimed before Alex supplies it.
Next
- Run Unlighthouse or PageSpeed and record real performance evidence.
- Submit the updated sitemap in Search Console or resubmit if already added.
- Use Client Report as the template for the next portfolio case.
2026-05-23
Entity Definition Strengthening
Added a dedicated entity-definition page, homepage FAQ answers, and structured data so answer engines have a clearer first-party source for the prompt 'What is AI Growth Bench?'.
Hypothesis
If the project has a dedicated entity page and repeated canonical wording, answer engines should be less likely to confuse it with unrelated benchmarks or companies.
Action
Created /what-is-ai-growth-bench, added homepage FAQ answers, and added structured data for WebSite, ProfilePage, CreativeWork, WebPage, and FAQPage.
Result
The site now has a first-party entity source that can be submitted for indexing and referenced in future answer-engine tests.
Next test
After Search Console indexing evidence appears, rerun 'What is AI Growth Bench?' in Gemini, Perplexity, ChatGPT, Grok, and Google Search.
Evidence
- New public URL planned for sitemap inclusion: https://aigrowthbench.com/what-is-ai-growth-bench.
- Homepage now includes direct-answer FAQ content for the tested prompt.
- Structured data now covers WebSite, ProfilePage, CreativeWork, WebPage, and FAQPage records.
Checked URLs
- https://aigrowthbench.com/
- https://aigrowthbench.com/what-is-ai-growth-bench
- https://aigrowthbench.com/sitemap.xml
Wins
- Created a direct definition page for AI Growth Bench with a canonical answer, entity facts, workflow, FAQ, and answer-engine baseline.
- Added FAQ and CreativeWork structured data on the homepage and definition page.
- Added WebSite and ProfilePage structured data at the root layout level.
Risks
- Search engines and answer engines still need time to crawl and refresh their understanding.
- Perplexity and Google AI Overview remain pending until manually checked.
Next
- Submit the updated sitemap in Google Search Console.
- After indexing, repeat the prompt 'What is AI Growth Bench?' in Gemini, Perplexity, ChatGPT, Grok, and Google AI Overview.
- If Gemini still misses the project, add external references and stronger About-page entity statements.
2026-05-23
Answer Engine Visibility Baseline
Ran the first manual answer-engine visibility check for the prompt 'What is AI Growth Bench?'. ChatGPT and Grok recognized the project from the public site, Gemini missed the project context, and Perplexity / Google AI Overview remain pending rather than being claimed.
Hypothesis
A clear public homepage should be enough for some answer engines to identify the project, but newer or uncrawled engines may still miss it before indexing settles.
Action
Captured a manual baseline for the same prompt across available answer surfaces and separated recognized, missed, and pending results.
Result
ChatGPT and Grok recognized the project accurately; Gemini missed the current project; Perplexity and Google AI Overview remain unclaimed until tested.
Next test
Repeat the same prompt after sitemap submission and URL Inspection, then compare citation status, answer accuracy, and source visibility.
Evidence
- ChatGPT screenshot: recognized AI Growth Bench as a public AI growth lab and described the trend discovery, keyword scoring, page generation, index tracking, AI answer citation review, and weekly reporting workflow.
- Grok screenshot: recognized AI Growth Bench (aigrowthbench.com) as a public operating bench for AI-powered growth automation, programmatic SEO, and GEO visibility.
- Gemini screenshot: did not recognize the current public project and instead suggested unrelated GrowthBench or AI benchmark meanings.
Checked URLs
- Prompt: What is AI Growth Bench?
- Surface: ChatGPT
- Surface: Gemini
- Surface: Grok
- Canonical project URL: https://aigrowthbench.com/
Wins
- ChatGPT described AI Growth Bench as a public AI growth lab and used wording aligned with the official site.
- Grok recognized aigrowthbench.com and summarized the operating bench, pipeline, and portfolio purpose accurately.
- The test produced a clear baseline for where the project is already understood and where it is still invisible.
Risks
- Gemini did not identify the current public project and interpreted the phrase as a possible company or benchmark concept.
- Perplexity and Google AI Overview have not been verified in this run.
- Screenshots show answer behavior, but future checks should capture source panels or cited URLs more explicitly.
Next
- Add a direct FAQ block to the homepage answering 'What is AI Growth Bench?'.
- Add more explicit entity statements near the top of the homepage and GEO Bench page.
- Repeat the same prompt after Search Console indexing and record whether Gemini, Perplexity, and AI Overview improve.
2026-05-22
Launch & Indexing Baseline
AI Growth Bench is live on its own domain with HTTPS, canonical redirects, sitemap, robots.txt, and core public routes. Search Console submission and confirmed index coverage are still manual follow-up items, so no Google index or answer-engine citation is claimed yet.
Hypothesis
A clean technical launch with HTTPS, canonical redirects, robots.txt, and sitemap gives the project a credible base for future SEO and GEO experiments.
Action
Deployed the Next.js app to the server, configured PM2 and Nginx, enabled canonical redirects, and exposed sitemap and robots endpoints.
Result
The public production domain and supporting SEO endpoints are live; Google index status is intentionally not claimed until Search Console evidence exists.
Next test
Submit the sitemap, request indexing for the homepage and entity page, and record the first discovered/indexed URL evidence.
Evidence
- https://aigrowthbench.com returns HTTP/2 200 with text/html content.
- http://aigrowthbench.com returns 301 to https://aigrowthbench.com/.
- https://www.aigrowthbench.com returns 301 to https://aigrowthbench.com/.
- /sitemap.xml returns HTTP/2 200 with application/xml content and seven URLs.
- /robots.txt returns HTTP/2 200 with text/plain content.
Checked URLs
- https://aigrowthbench.com/
- https://aigrowthbench.com/sitemap.xml
- https://aigrowthbench.com/robots.txt
- https://aigrowthbench.com/trend-lab
- https://aigrowthbench.com/programmatic-seo
- https://aigrowthbench.com/geo-bench
- https://aigrowthbench.com/reports
- https://aigrowthbench.com/system
- https://aigrowthbench.com/about
Wins
- The production domain returns HTTP/2 200 on the canonical HTTPS URL.
- HTTP and www requests redirect to https://aigrowthbench.com.
- The sitemap exposes seven public routes for the MVP portfolio bench.
Risks
- Google Search Console ownership and sitemap submission still require Alex's account.
- The domain is new, so there is no confirmed index coverage or AI citation evidence yet.
Next
- Add aigrowthbench.com in Google Search Console and submit /sitemap.xml.
- Update this report once GSC shows discovered or indexed URL counts.
- Keep answer-engine visibility checks as a separate manual evidence pass.
2026-05-22
GEO Structure Audit Baseline
Reviewed the public homepage, GEO Bench, and Reports pages for citation-friendly structure. The pages now show a real structure baseline, but external sources and logged answer-engine outputs are still needed before claiming visibility.
Hypothesis
Pages that expose target questions, concise findings, scored dimensions, evidence, and next actions should be easier to audit and improve for answer-engine visibility.
Action
Reviewed the homepage, GEO Bench, and Reports pages and scored citation friendliness, entity coverage, answer structure, and source quality.
Result
The structure is promising, but source quality remains the weakest dimension because Search Console and AI citation evidence are still early.
Next test
Attach Search Console observations and rerun answer-engine prompts to turn structure scores into visibility evidence.
Evidence
- Homepage visible text includes AI Growth Bench, Programmatic SEO, GEO Bench, Reports, Top scored keywords, and answer-engine positioning.
- GEO Bench visible text includes ChatGPT, Perplexity, Gemini, Google AI Overview, target questions, and scored experiment records.
- Reports visible text includes Weekly reports, wins, risks, next actions, evidence, and checked URLs after this update.
Checked URLs
- https://aigrowthbench.com/
- https://aigrowthbench.com/geo-bench
- https://aigrowthbench.com/reports
Wins
- The homepage clearly names the project and the growth automation pipeline.
- The GEO Bench page uses target questions, page patterns, score dimensions, findings, evidence, and next actions.
- The Reports page separates wins, risks, next actions, evidence, and tested URLs.
Risks
- Source quality is still the weakest dimension because there are not enough external references attached to claims.
- No ChatGPT, Perplexity, Gemini, or Google AI Overview citation has been confirmed yet.
Next
- Add short Q&A blocks to the homepage and GEO Bench page.
- After Alex runs manual answer-engine searches, record prompt, date, surface, answer summary, citation status, and next change.
- Add Search Console observations once the property is verified.