AGBAI Growth BenchGrowth automation portfolio labWork With Me

Reports

Weekly reports that turn experiments into portfolio evidence.

Each report separates shipped work, visible wins, risks, and next actions so a client or employer can see how the system improves.

Report format

Hypothesis, action, evidence, result, next test.

This format turns the site into a case study rather than a list of updates. Each report states what was expected, what changed, what proof exists, what happened, and what should be tested next.

Search Console status

Sitemap endpoint

Ready

The public sitemap is available at https://aigrowthbench.com/sitemap.xml and now includes the case study, evidence log, and published experiment pages.

Homepage URL inspection

Pending evidence

Homepage is ready for URL Inspection, but the public case study does not claim indexed status until Search Console evidence is captured.

Entity page URL inspection

Pending evidence

The entity-definition page is the most important page for answer-engine understanding and should be requested for indexing after sitemap submission.

First query/impression record

Waiting

The domain is too new to claim Search Console performance data. This slot is reserved for first query, impression, and indexed-page observations.

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 XML/text sitemaps, RSS/Atom feeds, robots sitemap references, AI-readable context, and IndexNow notifications, more crawlers can discover updates earlier than relying on one sitemap alone.

Action

Added /search-discovery, /sitemap.txt, /feed.xml, /rss.xml, /atom.xml, an IndexNow key file, and a sitemap-driven IndexNow submit script; robots.txt now advertises the discovery files.

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 sitemap.xml, sitemap.txt, feed.xml, and atom.xml.

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 sitemap.xml, feed.xml, and atom.xml in Google Search Console.
  • 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.

Latest evidence trail

SEO Audit2026-05-24

Search discovery layer added

AI Growth Bench added public discovery endpoints so search engines and feed consumers can find new or updated pages through more than one route.

Deployment2026-05-22

Production deployment baseline

AI Growth Bench was deployed on its own domain with HTTPS, canonical redirects, sitemap, robots.txt, and PM2/Nginx production routing.

Answer Engine2026-05-23

First answer-engine visibility baseline

ChatGPT and Grok recognized AI Growth Bench from the public site, while Gemini missed the current project context and treated the name as ambiguous.