AI search visibility portfolio module

GEO Visibility Bench

A measurement surface for checking whether pages are easy for answer engines to understand, quote, and distinguish from unrelated entities.

Module status

Live baseline, manual answer checks pending

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.

GEO score

77

Codex SEO GEO score after adding a 136-word answer block.

Citation block

1

One optimal 134-167 word answer-first passage detected.

AI surfaces

5

ChatGPT, Gemini, Grok, Perplexity, and Google AI Overview tracked.

AI files

2

llms.txt and llms-full.txt expose project context and evidence.

Workflow

  1. 01Define the exact question the page should answer.
  2. 02Add entity facts and a self-contained answer block near the top.
  3. 03Allow major AI/search crawlers in robots.txt.
  4. 04Expose llms.txt and llms-full.txt as comprehension aids.
  5. 05Retest answer engines after indexing and record whether the page is cited, paraphrased, or missed.

Client-ready deliverables

  • GEO readiness scorecard.
  • Entity clarity checklist.
  • Crawler access and llms.txt review.
  • Manual answer-engine prompt log.
  • Monthly delta report after new evidence arrives.

Current 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 moves I can do without API access

  • 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, login, or paid data 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.

Portfolio proof path

This module feeds the weekly report.

New evidence from this module should be summarized in Reports and added to Evidence Log before it is treated as a portfolio claim.