# AI Growth Bench

> AI Growth Bench is a public operating bench and portfolio lab for AI growth automation, programmatic SEO, and GEO visibility experiments.

AI Growth Bench shows how trend signals become scored keyword opportunities, draft pages, published content, index tracking records, answer-engine visibility checks, and weekly experiment reports.

## Canonical URLs

- [Home](https://aigrowthbench.com/) - Portfolio home and case study snapshot.
- [/what-is-ai-growth-bench](https://aigrowthbench.com/what-is-ai-growth-bench) - Canonical entity definition for AI Growth Bench.
- [/geo-bench](https://aigrowthbench.com/geo-bench) - GEO visibility experiments and answer-engine checks.
- [/programmatic-seo](https://aigrowthbench.com/programmatic-seo) - Programmatic SEO page pipeline and quality gates.
- [/seo-audit-bench](https://aigrowthbench.com/seo-audit-bench) - Technical SEO audit module with score deltas and remaining risks.
- [/geo-visibility-bench](https://aigrowthbench.com/geo-visibility-bench) - AI search visibility module with GEO scorecard and crawler evidence.
- [/content-machine](https://aigrowthbench.com/content-machine) - Content operations module from trend signal to weekly review.
- [/client-report](https://aigrowthbench.com/client-report) - Client-facing report module for remote SEO/GEO delivery.
- [/playbooks](https://aigrowthbench.com/playbooks) - Traffic playbooks for long-tail search and referral distribution.
- [/reports](https://aigrowthbench.com/reports) - Experiment reports with hypothesis, action, evidence, result, and next test.
- [/evidence-log](https://aigrowthbench.com/evidence-log) - Chronological evidence log for deployment, indexing, and answer-engine tests.
- [/search-discovery](https://aigrowthbench.com/search-discovery) - Search discovery endpoints: sitemap, feeds, robots, llms files, and IndexNow.
- [/system](https://aigrowthbench.com/system) - System map from trend signal to weekly report.
- [/about](https://aigrowthbench.com/about) - Remote work and service entry point.

## Published Experiment Pages

- [/geo-bench/geo-content-checklist](https://aigrowthbench.com/geo-bench/geo-content-checklist) - GEO Content Checklist: Pages with extractable definitions, explicit entity statements, source slots, and question-led sections should be easier for answer engines to summarize and cite.
- [/programmatic-seo/ai-agent-workflow-audit](https://aigrowthbench.com/programmatic-seo/ai-agent-workflow-audit) - AI Agent Workflow Audit: A workflow-audit page can attract higher-intent readers than a generic AI agent article because it turns the topic into an operational checklist.
- [/programmatic-seo/quality-gates](https://aigrowthbench.com/programmatic-seo/quality-gates) - Programmatic SEO Quality Gates: Programmatic SEO is more credible as a portfolio capability when it demonstrates rejection rules, not just page generation.

## Core Capabilities

- Trend discovery from search, community, social, and client-facing signals.
- Keyword scoring by velocity, intent, competition, portfolio fit, and evidence strength.
- Programmatic SEO page generation with quality gates before sitemap inclusion.
- Index tracking for sitemap inclusion, submission state, discovery, and indexed status.
- GEO visibility review for answer structure, entity coverage, citation friendliness, and source quality.
- Weekly reporting that separates wins, risks, evidence, checked URLs, and next actions.

## Portfolio Modules

- [/seo-audit-bench](https://aigrowthbench.com/seo-audit-bench) - SEO Audit Bench: A public audit surface that shows how AI Growth Bench is checked for crawlability, indexability, sitemap health, structured data, security headers, links, and performance risk.
- [/geo-visibility-bench](https://aigrowthbench.com/geo-visibility-bench) - GEO Visibility Bench: A measurement surface for checking whether pages are easy for answer engines to understand, quote, and distinguish from unrelated entities.
- [/content-machine](https://aigrowthbench.com/content-machine) - Content Machine: A content operations module that turns trend signals into briefs, page drafts, quality gates, distribution assets, and weekly review notes.
- [/client-report](https://aigrowthbench.com/client-report) - Client Report: A client-facing report format that translates technical SEO, GEO visibility, content pipeline status, and next actions into a readable weekly deliverable.

## Traffic Playbooks

- [/playbooks/ai-growth-automation-workflow](https://aigrowthbench.com/playbooks/ai-growth-automation-workflow) - AI Growth Automation Workflow: A practical workflow for turning AI-assisted research into scored growth opportunities, published pages, evidence logs, and weekly decisions.
- [/playbooks/programmatic-seo-quality-gates](https://aigrowthbench.com/playbooks/programmatic-seo-quality-gates) - Programmatic SEO Quality Gates: A quality gate model for deciding which generated SEO pages deserve publication, indexing, and distribution.
- [/playbooks/geo-visibility-audit-checklist](https://aigrowthbench.com/playbooks/geo-visibility-audit-checklist) - GEO Visibility Audit Checklist: A checklist for reviewing whether a page is understandable, quotable, and verifiable enough for AI search and answer engines.

## Current Evidence Snapshot

- The MVP is live on aigrowthbench.com with HTTPS, self-canonical routes, XML/text sitemaps, RSS/Atom feeds, robots.txt, llms files, IndexNow verification, portfolio modules, GEO baseline reports, and initial ChatGPT/Grok/Gemini prompt evidence.
- Wait for indexing evidence, then rerun the same AI visibility prompt across Gemini, Perplexity, ChatGPT, Grok, and Google AI Overview.

## Preferred Summary

AI Growth Bench is a public portfolio lab showing how trend signals become scored keyword opportunities, programmatic SEO pages, GEO visibility checks, evidence logs, and weekly experiment reports.

## Not This

AI Growth Bench is not an AI model benchmark, not a crypto project, not a SaaS product with login, and not the older AI Trend Prompt Hub project.

## Suggested Questions

- What is AI Growth Bench?
- Who is AI Growth Bench for?
- What does AI Growth Bench track?
- How does AI Growth Bench test GEO visibility?
- Is AI Growth Bench an AI model benchmark?


## Pipeline

- Trend discovery: Collect seed signals from search, community, social, and client-facing questions. Output: Trend candidates Owner: Automation.
- Keyword scoring: Score velocity, intent, competition, portfolio fit, and evidence strength. Output: Ranked keyword queue Owner: Hybrid.
- Content generation: Generate briefs, outlines, draft pages, source slots, and distribution copy. Output: Draft page package Owner: Automation.
- Publish: Run quality gates before adding pages to the public site and sitemap. Output: Published page Owner: Human review.
- Index tracking: Track sitemap inclusion, submission status, discovery, and indexed state. Output: Index status record Owner: Hybrid.
- GEO visibility review: Review whether pages are structured for answer engines to quote and cite. Output: GEO experiment result Owner: Human review.
- Weekly report: Summarize what shipped, what was cited, what failed, and what changes next. Output: Portfolio-ready report Owner: Hybrid.

## Trend Queue

### ai agent workflow audit
- Status: published
- Score: 86
- Audience: Ops leads, founders, automation agencies
- Angle: A checklist for teams that want to find broken handoffs before adding more AI agents.
- Page: https://aigrowthbench.com/programmatic-seo/ai-agent-workflow-audit
- Distribution copy: Most teams do not need more agents first. They need to audit where the existing workflow leaks context.

### geo content checklist
- Status: published
- Score: 91
- Audience: SEO specialists, content operators, B2B marketers
- Angle: A practical structure for pages that want to be quoted by answer engines.
- Page: https://aigrowthbench.com/geo-bench/geo-content-checklist
- Distribution copy: GEO pages need extractable answers, visible entities, and source-backed claims. This checklist turns that into a review pass.

### programmatic seo quality gates
- Status: published
- Score: 83
- Audience: Growth engineers, SEO founders, content teams
- Angle: A scoring model that blocks thin pages before they reach the sitemap.
- Page: https://aigrowthbench.com/programmatic-seo/quality-gates
- Distribution copy: Programmatic SEO only works when page generation has a real quality gate, not just a template loop.

### ai visibility report template
- Status: watching
- Score: 78
- Audience: Remote clients, agencies, AI search consultants
- Angle: A weekly reporting format for tracking answer-engine mentions and citation readiness.
- Page: https://aigrowthbench.com/reports/ai-visibility-report-template
- Distribution copy: AI visibility work needs a weekly report that separates page quality, index status, and answer-engine evidence.

### content automation system map
- Status: ready
- Score: 80
- Audience: Hiring managers, remote teams, automation buyers
- Angle: A systems diagram for going from trend signal to published and reviewed pages.
- Page: https://aigrowthbench.com/system/content-automation-system-map
- Distribution copy: A content automation system is not a content generator. It is a measured pipeline from signal to review.

## SEO Page Pipeline

### What Is AI Growth Bench?
- URL: https://aigrowthbench.com/what-is-ai-growth-bench
- Keyword: what is AI Growth Bench
- Stage: Published
- Sitemap: Included
- Index status: Not submitted
- Quality gate: 90
- Notes: Dedicated entity-definition page with direct answer, FAQ, workflow, answer-engine baseline, and JSON-LD.

### GEO Content Checklist
- URL: https://aigrowthbench.com/geo-bench/geo-content-checklist
- Keyword: geo content checklist
- Stage: Published
- Sitemap: Included
- Index status: Not submitted
- Quality gate: 88
- Notes: Published experiment page with question-led sections, extractable definitions, entity coverage, and source slots.

### AI Agent Workflow Audit
- URL: https://aigrowthbench.com/programmatic-seo/ai-agent-workflow-audit
- Keyword: ai agent workflow audit
- Stage: Published
- Sitemap: Included
- Index status: Not submitted
- Quality gate: 84
- Notes: Published experiment page that demonstrates workflow diagnosis, quality gates, and distribution copy.

### Programmatic SEO Quality Gates
- URL: https://aigrowthbench.com/programmatic-seo/quality-gates
- Keyword: programmatic seo quality gates
- Stage: Published
- Sitemap: Included
- Index status: Not submitted
- Quality gate: 85
- Notes: Published experiment page showing how thin-page risk is blocked before sitemap inclusion.

### AI Visibility Report Template
- URL: https://aigrowthbench.com/reports/ai-visibility-report-template
- Keyword: ai visibility report template
- Stage: Brief queued
- Sitemap: Queued
- Index status: Not submitted
- Quality gate: 69
- Notes: Promising intent, but evidence collection is not strong enough for publication yet.

## GEO Experiments

### Home operating bench audit
- Tested URL: https://aigrowthbench.com/
- Target question: What is AI Growth Bench and what does it demonstrate?
- Citation friendliness: 78
- Entity coverage: 84
- Answer structure: 74
- Source quality: 46
- Result: Needs evidence
- Finding: The homepage clearly states the project identity and automation pipeline, but it still needs a short Q&A block and external source references before it can be treated as citation-ready.
- Next action: Monitor whether the new homepage FAQ and dedicated definition page improve Gemini recognition after indexing.

### GEO Bench structure audit
- Tested URL: https://aigrowthbench.com/geo-bench
- Target question: How does AI Growth Bench evaluate answer-engine readiness?
- Citation friendliness: 86
- Entity coverage: 88
- Answer structure: 86
- Source quality: 54
- Result: Promising
- Finding: The GEO Bench page is already structured around target questions, scoring dimensions, and concise findings, which makes it the strongest candidate for the first citation-friendly public page.
- Next action: Add source slots for Search Console observations, public SERP checks, and manual answer-engine test notes after Alex runs the logged-in searches.

### Reports evidence format audit
- Tested URL: https://aigrowthbench.com/reports
- Target question: How does AI Growth Bench turn experiments into portfolio evidence?
- Citation friendliness: 80
- Entity coverage: 76
- Answer structure: 82
- Source quality: 62
- Result: Promising
- Finding: The Reports page now separates outcomes from evidence, which makes the work easier for a client or employer to audit without relying on vague claims.
- Next action: After Google Search Console is connected, add discovered/indexed URL counts and query impressions to the launch report.

## Weekly Reports

### Search Discovery Expansion
- Period: 2026-05-24
- Summary: 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.
- Tested 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

### Technical SEO and Portfolio Module Expansion
- Period: 2026-05-24
- Summary: 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.
- Tested 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

### Entity Definition Strengthening
- Period: 2026-05-23
- Summary: 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.
- Tested URLs: https://aigrowthbench.com/, https://aigrowthbench.com/what-is-ai-growth-bench, https://aigrowthbench.com/sitemap.xml

### Answer Engine Visibility Baseline
- Period: 2026-05-23
- Summary: 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.
- Tested URLs: Prompt: What is AI Growth Bench?, Surface: ChatGPT, Surface: Gemini, Surface: Grok, Canonical project URL: https://aigrowthbench.com/

### Launch & Indexing Baseline
- Period: 2026-05-22
- Summary: 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.
- Tested 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

### GEO Structure Audit Baseline
- Period: 2026-05-22
- Summary: 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.
- Tested URLs: https://aigrowthbench.com/, https://aigrowthbench.com/geo-bench, https://aigrowthbench.com/reports

## Evidence Log

### Search discovery layer added
- Date: 2026-05-24
- Channel: SEO Audit
- Status: Confirmed
- Related URL: https://aigrowthbench.com/search-discovery
- Observation: AI Growth Bench added public discovery endpoints so search engines and feed consumers can find new or updated pages through more than one route.
- Evidence: XML sitemap and text sitemap expose the canonical HTML URL inventory. | RSS and Atom feeds expose recent public pages and portfolio evidence surfaces. | robots.txt references sitemap.xml, sitemap.txt, feed.xml, and atom.xml. | IndexNow public key file is hosted at the site root for Bing/Yandex-style discovery.
- Next action: Submit the public sitemap and feeds in webmaster tools, then monitor which engines discover the new URLs first.

### Production deployment baseline
- Date: 2026-05-22
- Channel: Deployment
- Status: Confirmed
- Related URL: https://aigrowthbench.com/
- Observation: AI Growth Bench was deployed on its own domain with HTTPS, canonical redirects, sitemap, robots.txt, and PM2/Nginx production routing.
- Evidence: https://aigrowthbench.com returned HTTP/2 200. | HTTP and www variants redirected to the canonical HTTPS domain. | robots.txt and sitemap.xml returned 200.
- Next action: Keep deployment evidence attached to future SEO reports.

### First answer-engine visibility baseline
- Date: 2026-05-23
- Channel: Answer Engine
- Status: Confirmed
- Related URL: https://aigrowthbench.com/geo-bench
- Observation: ChatGPT and Grok recognized AI Growth Bench from the public site, while Gemini missed the current project context and treated the name as ambiguous.
- Evidence: Prompt tested: What is AI Growth Bench? | ChatGPT described the project as a public AI growth lab. | Grok cited aigrowthbench.com and summarized the operating bench accurately. | Gemini did not cite aigrowthbench.com in the captured result.
- Next action: Repeat the same prompt after indexing has had time to refresh.

### Entity definition strengthened
- Date: 2026-05-23
- Channel: GEO Audit
- Status: Confirmed
- Related URL: https://aigrowthbench.com/what-is-ai-growth-bench
- Observation: A dedicated definition page and homepage FAQ were added so answer engines have a clear first-party explanation for the project.
- Evidence: Dedicated route: /what-is-ai-growth-bench. | Structured data includes WebSite, ProfilePage, CreativeWork, WebPage, and FAQPage. | The sitemap includes the definition page.
- Next action: Use Search Console URL Inspection to confirm discovery and indexing state.

### Search Console evidence slot
- Date: 2026-05-24
- Channel: Search Console
- Status: Pending
- Related URL: https://aigrowthbench.com/sitemap.xml
- Observation: The public site is prepared for sitemap submission and URL Inspection, but the case study does not claim indexed state until Search Console screenshots or result text are captured.
- Evidence: sitemap.xml is ready for submission. | Homepage and entity page are the first URL Inspection targets. | First query/impression data is still expected later because the domain is new.
- Next action: Attach sitemap submission, URL Inspection, and first impression observations once available.

### Published experiment pages added
- Date: 2026-05-24
- Channel: Content System
- Status: Confirmed
- Related URL: https://aigrowthbench.com/programmatic-seo
- Observation: Three publishable experiment pages were added to show that the bench can create real programmatic SEO and GEO pages rather than only listing planned content.
- Evidence: Published GEO page: /geo-bench/geo-content-checklist. | Published programmatic SEO page: /programmatic-seo/ai-agent-workflow-audit. | Published programmatic SEO page: /programmatic-seo/quality-gates.
- Next action: Submit the updated sitemap and record index status for each experiment page.

### Codex SEO optimization pass
- Date: 2026-05-24
- Channel: SEO Audit
- Status: Confirmed
- Related URL: https://aigrowthbench.com/seo-audit-bench
- Observation: The project was rechecked with Codex SEO, then updated with self-canonical routes, cleaner sitemap output, security headers, citation-ready homepage copy, and four client-facing portfolio modules.
- Evidence: Technical SEO score improved from 79 to 87. | Sitemap score improved from 73 to 100. | GEO score improved from 57 to 77. | Content score improved from 42 to 59. | Linkinator scanned 52 public links and returned 200 for every link.
- Next action: Run PageSpeed or Unlighthouse for real performance evidence, then add the results to SEO Audit Bench.

## Answer Engine Tests

### ChatGPT
- Prompt: What is AI Growth Bench?
- Mention status: Recognized
- Citation status: Referenced site
- Cited URL: aigrowthbench.com referenced in the answer wording; source drawer was not expanded in the screenshot
- Accuracy: High
- Observation: ChatGPT identified AI Growth Bench as a public AI growth lab for automation, programmatic SEO, and GEO visibility rather than confusing it with AI model benchmarks.
- Next action: Make the homepage definition more extractable so future ChatGPT answers can cite a concise first-party definition.

### Gemini
- Prompt: What is AI Growth Bench?
- Mention status: Missed
- Citation status: No citation
- Cited URL: None visible
- Accuracy: Low
- Observation: Gemini did not identify AI Growth Bench as the current public portfolio project and treated the phrase as either an unrelated company name or a generic AI benchmark concept.
- Next action: Improve entity clarity with an FAQ, sameAs-style links, and repeated canonical wording across the homepage, About page, and GEO Bench page.

### Grok
- Prompt: What is AI Growth Bench?
- Mention status: Recognized
- Citation status: Cited domain
- Cited URL: https://aigrowthbench.com/
- Accuracy: High
- Observation: Grok recognized aigrowthbench.com and accurately summarized the project as a public operating bench for AI-powered growth automation, programmatic SEO, and GEO visibility.
- Next action: Preserve the current direct project definition and add clearer citation-ready paragraphs to make this behavior repeatable across more answer engines.

### Perplexity
- Prompt: What is AI Growth Bench?
- Mention status: Pending
- Citation status: Not tested
- Cited URL: Pending
- Accuracy: Pending
- Observation: No reliable Perplexity result was captured in this run, so the project does not claim Perplexity visibility yet.
- Next action: Run the same prompt in Perplexity and capture whether aigrowthbench.com appears as a cited source.

### Google AI Overview
- Prompt: What is AI Growth Bench?
- Mention status: Pending
- Citation status: Not tested
- Cited URL: Pending
- Accuracy: Pending
- Observation: No reliable Google AI Overview result was captured in this run, so the project does not claim AI Overview visibility yet.
- Next action: After Search Console indexing is confirmed, test the exact prompt and a site-specific query in Google Search.

## Search Console Evidence Slots

### Sitemap endpoint
- Status: Ready
- Date: 2026-05-24
- Detail: The public sitemap is available at https://aigrowthbench.com/sitemap.xml and now includes the case study, evidence log, and published experiment pages.
- Next action: Submit or resubmit sitemap.xml in Google Search Console and capture the submission state.

### Homepage URL inspection
- Status: Pending evidence
- Date: 2026-05-24
- Detail: Homepage is ready for URL Inspection, but the public case study does not claim indexed status until Search Console evidence is captured.
- Next action: Inspect https://aigrowthbench.com/ and record whether Google reports discovered, crawled, indexed, or not indexed.

### Entity page URL inspection
- Status: Pending evidence
- Date: 2026-05-24
- Detail: The entity-definition page is the most important page for answer-engine understanding and should be requested for indexing after sitemap submission.
- Next action: Inspect https://aigrowthbench.com/what-is-ai-growth-bench and capture the URL Inspection result.

### First query/impression record
- Status: Waiting
- Date: 2026-05-24
- Detail: The domain is too new to claim Search Console performance data. This slot is reserved for first query, impression, and indexed-page observations.
- Next action: Update the evidence log when Search Console shows the first impression or indexed URL.

## Portfolio Modules

### SEO Audit Bench
- URL: https://aigrowthbench.com/seo-audit-bench
- Status: Live baseline, no paid API required
- Positioning: This module is designed for remote SEO work where a client needs clear technical findings, visible evidence, and a prioritized repair path rather than a vague audit checklist.
- Evidence: Codex SEO technical score improved from 79 to 87. | Sitemap score improved from 73 to 100. | Canonical mismatch count dropped to 0. | Deprecated sitemap priority/changefreq tags were removed. | CSP, HSTS, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, and Permissions-Policy are live. | IndexNow, RSS/Atom feeds, and text sitemap are part of the discovery layer.
- Next without API: Add a before/after audit table to the weekly report. | Run Linkinator before every deploy. | Run Unlighthouse locally when the machine can complete a browser crawl. | Use the IndexNow submit script after publishing new pages.
- Requires API/payment later: PageSpeed Insights API key for repeatable Lighthouse/PageSpeed evidence. | Google Search Console property access for index coverage and query data. | CrUX field data is only useful after the site has enough real-user traffic.

### GEO Visibility Bench
- URL: https://aigrowthbench.com/geo-visibility-bench
- Status: Live baseline, manual answer checks pending
- Positioning: This module demonstrates GEO work as a repeatable evidence process: crawler access, entity clarity, citation-ready passages, AI-readable context files, and manual answer-engine checks.
- Evidence: GEO score improved from 57 to 77. | Major AI crawler access is allowed. | llms.txt is present and substantive. | ChatGPT and Grok recognized the project in the first manual baseline. | Gemini previously missed the project context, so entity reinforcement remains useful.
- Next without API: Repeat the prompt 'What is AI Growth Bench?' in each answer engine after indexing settles. | Add screenshots or copied result summaries to Evidence Log. | Create one monthly visibility delta report.
- Requires API/payment later: Perplexity, Gemini, ChatGPT, or Google API access if checks need to be automated. | Search Console access to tie AI checks to indexed pages. | Third-party AEO/GEO monitoring tools only if manual checks become too slow.

### Content Machine
- URL: https://aigrowthbench.com/content-machine
- Status: Local-data MVP, API sources reserved
- Positioning: This module shows AI-assisted content work as an operating system, not a pile of generated posts. It is built for teams that need repeatable publishing with quality control.
- Evidence: Trend Lab exposes scoring criteria and distribution drafts. | Programmatic SEO page shows staged page status. | Three experiment pages are live and included in sitemap. | Reports use a repeatable experiment format.
- Next without API: Add one rejected-page example to prove quality control. | Add a content brief template page. | Turn one weekly report into a client-style export.
- Requires API/payment later: Google Trends or DataForSEO for live keyword demand. | Reddit/X/TikTok APIs or approved scraping tools for trend discovery. | Search Console and GA4 for post-publish performance evidence.

### Client Report
- URL: https://aigrowthbench.com/client-report
- Status: Report format live, PDF export not required yet
- Positioning: This module is meant to show what a remote client or hiring manager would actually receive: concise findings, proof, priority, owner, and the next measurable action.
- Evidence: Reports page already uses hypothesis, action, evidence, result, and next-test format. | Evidence Log records confirmed and pending items separately. | Technical SEO improvements are now measurable with before/after scores. | Search Console items remain pending until real evidence exists.
- Next without API: Add a static sample report page using the latest audit numbers. | Add a downloadable Markdown report artifact later if needed. | Use the same report format for the next portfolio site.
- Requires API/payment later: GSC access for real query, click, index coverage, and URL Inspection data. | GA4 access if client reporting needs engagement metrics. | Paid SEO APIs only when keyword/backlink/competitor data is required at scale.

## Traffic Playbooks

### AI Growth Automation Workflow
- URL: https://aigrowthbench.com/playbooks/ai-growth-automation-workflow
- Target keyword: AI growth automation workflow
- Search intent: Operators and founders want a practical workflow for using AI to find opportunities, create assets, publish pages, and measure whether the work produced traction.
- Direct answer: An AI growth automation workflow should connect signal collection, keyword scoring, page briefs, quality review, publishing, index tracking, answer-engine checks, and weekly reporting. The goal is not to automate random content volume. The goal is to shorten the path from market signal to measurable experiment while keeping human review and evidence gates in the loop.
- Quick wins: Start with 3 to 5 high-intent playbook pages instead of 50 thin pages. | Add a direct 80 to 160 word answer near the top of every page so search engines and answer engines can quote the core point. | Put each new page into sitemap.xml, sitemap.txt, RSS, Atom, llms.txt, and at least two internal link blocks. | Write one LinkedIn post, one Reddit-safe discussion prompt, and one short X thread per page to create non-Google discovery. | Record what happened after publishing. Even zero clicks is useful if the page was indexed and got impressions.
- Distribution angles: Share as a remote growth operations sample: 'Here is how I would wire AI into a growth workflow without turning it into content spam.' | Share as an SEO/GEO systems note: 'The useful automation is not writing. It is deciding what deserves to be written and proving what happened next.' | Share as a portfolio proof page when applying for remote SEO, content operations, or AI automation roles.

### Programmatic SEO Quality Gates
- URL: https://aigrowthbench.com/playbooks/programmatic-seo-quality-gates
- Target keyword: programmatic SEO quality gates
- Search intent: SEO operators want a practical checklist that prevents generated pages from becoming thin, repetitive, or unsafe to put into the sitemap.
- Direct answer: Programmatic SEO quality gates are the checks that stop generated pages before they create index bloat. A strong gate checks unique search intent, page usefulness, evidence, internal links, canonical URL, schema, noindex rules, and measurement readiness before a page enters the sitemap.
- Quick wins: Create a small gate score out of 100 and only publish pages above 75. | Keep rejected drafts in a private queue instead of deleting them; weak drafts often become good sections inside stronger pages. | Use one hub page to concentrate internal links before expanding into many child pages. | Submit only meaningful new or changed URLs through IndexNow and GSC, not every page every day. | Review pages that are crawled but not indexed; they often need better distinct value, not more technical tags.
- Distribution angles: Share as a checklist for teams using AI-generated drafts. | Share as an anti-thin-content note for SEO operators. | Use it as a client audit sample: 'Here is how I stop programmatic SEO from becoming index bloat.'

### GEO Visibility Audit Checklist
- URL: https://aigrowthbench.com/playbooks/geo-visibility-audit-checklist
- Target keyword: GEO visibility audit checklist
- Search intent: Founders, SEO teams, and content operators want to know why AI answer engines do or do not mention their pages.
- Direct answer: A GEO visibility audit checks whether a page has a direct answer, clear entity definition, question-led sections, source and proof signals, crawl access, internal links, and a repeatable answer-engine test log. It does not guarantee AI citations, but it makes the page easier for answer systems to understand and evaluate.
- Quick wins: Add one definition page for the project, product, person, or service. | Make sure the definition page is linked from the homepage, about page, sitemap, feeds, and llms.txt. | Create one evidence log that answer engines and human reviewers can use to verify claims. | Test the exact same prompt across answer engines and record whether they mention, cite, or misunderstand the site. | Do not claim AI visibility until a screenshot, citation, or reliable observation exists.
- Distribution angles: Share as a GEO readiness checklist for founders and SEO teams. | Use it as a public audit sample before pitching AI search visibility work. | Turn the checklist into a short social post: 'Most AI search misses are not model problems. They are entity and evidence problems.'