An AI visibility index is a scoreboard for generative answers, not a Google ranking report. It asks whether ChatGPT, Claude, Gemini, or Perplexity name your business on the prompts buyers already use. SERP. Keep Search Console next to the checker.
The August hub stays as labeled history.
What is an AI visibility index?
An index, in this job, is a repeatable prompt panel plus a way to score outcomes. It is not:
| Not this | Why |
|---|---|
| A Google average position | Search Console already is that scoreboard |
| A single proprietary number with no prompt list | Un-auditable; dies in a client meeting |
| A replacement for SEO | Buyers still search Google; keep both channels |
| A census of every business in America | Most public “indexes” are optimizing panels or category samples |
Three outcomes get mixed when people say “score”:
| Outcome | What it is | How you log it |
|---|---|---|
| Omit | The engine never names you | Blank / competitor-only answer |
| Mention | Your brand appears in the answer | Text hit, no URL required |
| Citation | The engine points at a URL | Link, footnote, retrieval card |
| Recommendation | The engine picks you or a short shortlist | “Use X” / “start with Y” |
A mention is not a citation. A citation is not a recommendation. How to get cited in AI search is the citation job. GEO next to SEO is the pair. This page is the measurement frame agencies and in-house teams can put on a retainer slide without inventing ranks.
Who already occupies “AI visibility index”?
Condensed from the 7 Oct 2026 US desktop pulls:
| Who | Frame | Steal | Do not copy |
|---|---|---|---|
| Semrush enterprise index downloads | Category PDF / retail playbook | Named category + dated edition | Cloning their chapter list as our product |
| eMarketer / 5W-style PR indexes | Vertical “who owns the answer” | Clear sample window | Treating PR share-of-answer as a Scope feature |
| Score-definition blogs | “What is a good score?” | Formula honesty | Fake universal benchmarks without sample size |
| Tool listicles (xseek, sitespeak, Reddit) | Best platforms 2026 | Buyer is a marketer | Pasting “best of” claims we did not measure |
Pass. Keep the methodology frame. Do not retitle into consumer chatbot comparisons (is gemini a chatbot) even when KeywordTool volume is higher.
How should you build a score without lying?
Honest method you can defend in a QBR:
1. Freeze the prompt set
Ten to twenty non-branded buyer prompts beat fifty vanity ones. Split branded (“Is Scope a good AI visibility tool?”) from category (“best AI visibility platform for agencies”). SEO teams already do this split in Search Console. Keep the text stable for 30 days so a second pass means something.
2. Name the engines
ChatGPT ≠ Claude ≠ Gemini ≠ Perplexity ≠ Google AI Overviews / AI Mode. Profound’s public citation work (often summarized mid-2026) is frequently read as Claude leaning harder on Brave-style retrieval while ChatGPT leans lists, YouTube, and UGC. Treat that as a mechanism hint, not a percentage to paste under every H2. Log each engine alone.
3. Score outcomes, not vibes
Per prompt × engine, record omit / mention / citation / recommendation. Optional: which URL was cited, and whether it was yours. Do not collapse four engines into one vanity “Index 72” unless you show the denominator.
4. Separate Google from generative
Search Console clicks, impressions, coverage, and last crawl stay. Generative answers are a second scoreboard. Checker CTA sessions are not organic SEO clicks.
5. Re-run after the entity changes
Schema, GBP categories, NAP fixes, and third-party list updates move answers. A single screenshot is not a trend. The data methodology is the product-side writeup of how Scope runs checks; this Learn page is the operator frame you can repeat with or without the product.
Google Search Central’s AI-features documentation (confirmed 2 Sep 2026) still applies to Google’s own AI surfaces: no extra AI text file or special schema tickets you in. Indexed + snippet-eligible pages still matter. JSON-LD for AI helps machines parse you. It does not mint an “index rank.”
Counter-example: publishing a vanity index number
Counter-example: a team ships “Average AI Visibility Index: 41 in dental, 58 in SaaS,” links three /for/{niche} pages, and skips the prompt list because “the product has a score.”
What breaks:
- No denominator. Without prompts, engines, and dates, a client cannot reproduce the number. Vendor-own-user panels are not a census of the category.
- Wrong SERP job. “AI visibility index” on Google is already full of enterprise PDFs and PR vertical indexes. A thin product page does not displace Semrush’s download hub by asserting a bigger integer.
- We do not expand that pattern here.
- You still need Google SEO. Pausing technical SEO would not create generative demand. It would only risk the indexation you already have.
- Stat provenance. If you cannot name sample size, window, and engine set, cut the number. Do not paste a roundup’s “10x” under the wrong sentence.
What looks like a win and is not:
- A comparison table that frames generative measurement as a replacement for Search Console. Use both.
- A second slug that restates the same H1.
How do agencies put an index on a retainer?
Practical surface area, in order:
1. Baseline panel (week 0)
Pick 10–20 non-branded prompts. Run the same day across the engines you sell. Log omit / mention / cite / recommend. Screenshot or export with date. Pair with Search Console coverage on the money URLs.
2. Citation gap list
Where the model cited a directory, a competitor, or a roundup, that URL is the fix queue, not a keyword spreadsheet alone. Citation sources and ledger thinking is a different job (and watch student “cite AI” SERPs before you expand that slug). Prefer off-site consensus you can earn over on-page word count alone.
3. Entity sentence everywhere
Same name, category, customer, proof on homepage, About, and the first 40–80 words of money pages. Inconsistent NAP/entity data produces hedges and omissions more often than confident picks.
4. Technical access
Public HTML, bots allowed, no accidental noindex, honest sitemap lastmod. JavaScript rendering and AI crawlers covers empty shells.
5. Second pass after fixes
Re-run the same prompts. Report delta by engine. That before/after is the retainer artifact. How agencies add AI visibility to SEO is the delivery pattern. AEO audit is the first-pass checklist without cloning a competitor’s six-chapter guide.
6. Keep Google’s scoreboard
Impressions can fall while clicks hold when thin URL farms prune. Do not manage the program only to “get impressions back.” Clicks, key events, and generative recommendations are the outcomes that matter.
How should a marketing team spend 30 minutes?
A checklist you can finish before lunch. No new slug required.
- Coverage, last crawl, user vs Google canonical. Indexed is the bar.
- Pull Search Console
page EQUALSthe URL (28 days). Twenty-one impressions is a finding. Pullquerybefore a title rewrite so you do not chase a homonym. - SERP
ai visibility indexandai visibility score methodologyseparately. If PDFs and definition blogs own the query, write methodology, do not invent a census score. - Rewrite the first 40–80 words. Definition, one dated fact from this URL or this SERP, next action.
- Add visible
Q:/A:pairs already in the HTML before you care about FAQ schema. - Freeze 10 buyer prompts and run them once. Log omit / mention / cite / recommend. If an engine UI is blocked, write blocked.
- Link live money URLs only. Checker, agents / MCP, compare, GEO vs SEO, content strategy for AI search. Never internal-link a draft that is not HTTP 200.
How do you read someone else’s “index” report?
When a PDF or PR wire says Brand X “owns” a category:
| Check | Pass | Fail |
|---|---|---|
| Prompt list published? | You can re-ask the questions | Only a leaderboard graphic |
| Engines named? | ChatGPT / Claude / … split | “AI” as one blob |
| Window dated? | Month or quarter | Evergreen with no date |
| Sample described? | Category + count or panel type | “Thousands of brands” with no method |
| Google separated? | Search and generative both shown | Generative number sold as SEO |
Use external indexes as competitive context, not as your internal KPI unless you can reproduce them. Your KPI is your frozen panel plus Search Console on money URLs.
Frequently asked questions
Q: Is the Scope AI Visibility Index a ranking factor Google uses?
A: No. It is a measurement frame for generative-engine recommendations. Google Search Console remains the source of truth for Google search.
Q: How often should I refresh an index score?
A: After you change entity data, citations, or money-page answers, and at least monthly for competitive categories. Weekly is fine for local services. A single score without a second pass is a screenshot.
Q: Can agencies use this with clients?
A: Yes. Baseline 10–20 non-branded prompts, report omit / mention / cite / recommend by engine, attach citation gaps, keep Search Console beside it. That is the retainer artifact, not a keyword spreadsheet alone.
Q: Should we publish industry average scores on this page?
A: Only with sample size, window, engines, and prompt set. Prefer the panel method clients can repeat.
Q: Does Scope replace SEO tools for this work?
A: No. Scope measures whether answer engines name or cite you. Semrush, Ahrefs, and Search Console still do Google. Use both. See Scope next to Profound.
Q: Will llms.txt raise our index score?
A: No. Allow the relevant bots, ship HTML, stay indexed, and earn corroborating sources. llms.txt is not a recommendation ticket. See the llms.txt guide.
Run the AI visibility checker, connect the Scope MCP server, or keep the pair framing in GEO vs SEO. An index is a panel you can re-run. Google is still the other scoreboard.