geo-ai-visibility

geo-ai-visibility is an agent for Claude Code from zubair-trabzada/geo-seo-claude. It costs 62 tokens per session (2,596 once invoked), scanned A, original, MIT.

An agent that evaluates how visible a website is to AI search systems and language models. It examines whether the content can be cited, whether AI crawlers can access it, whether it follows llms.txt guidance, and whether the brand appears on AI-cited platforms.

In plain words
What is it for?
Analyzing a target URL, scoring content blocks for citation quality, checking crawler access and llms.txt, and reviewing the site’s brand presence in AI search results.
Why use it?
It identifies website visibility problems that may prevent AI systems from finding, understanding, or mentioning the site accurately.

Agent for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Good fit Analyzing a target URL, scoring content blocks for citation quality, checking crawler access and llms.txt, and reviewing the site’s brand presence in AI search results.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/zubair-trabzada/geo-seo-claude/geo-ai-visibility
About the project

geo-seo-claude is a Claude Code skill for improving how websites appear in AI-powered search while retaining traditional search-engine optimization. It is used by marketers and website practitioners for analysis such as citation scoring, crawler review, authority assessment, structured data, and platform-specific recommendations. The catalogue entries are skills and agents that carry out this optimization workflow.

zubair-trabzada/geo-seo-claude · 10,540 stars · on GitHub · skool.com

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Clone the repo
git clone --depth 1 https://github.com/zubair-trabzada/geo-seo-claude

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for geo-ai-visibility

README.md
[![agentmods](https://agentmods.dev/badge/agents/zubair-trabzada/geo-seo-claude/geo-ai-visibility/github.svg)](https://agentmods.dev/agents/zubair-trabzada/geo-seo-claude/geo-ai-visibility)
Your own site
<a href="https://agentmods.dev/agents/zubair-trabzada/geo-seo-claude/geo-ai-visibility"><img src="https://agentmods.dev/badge/agents/zubair-trabzada/geo-seo-claude/geo-ai-visibility/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for geo-ai-visibility

Your own site · 80×15
<a href="https://agentmods.dev/agents/zubair-trabzada/geo-seo-claude/geo-ai-visibility"><img src="https://agentmods.dev/badge/agents/zubair-trabzada/geo-seo-claude/geo-ai-visibility.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 62 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,596 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00062 $0.02596
Opus 5 $0.00031 $0.01298
Sonnet 5 $0.00012 $0.00519
Haiku 4.5 $0.00006 $0.00260

Measured 13d ago against content hash 2e368f0535e1, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

geo-ai-visibility scanned grade A with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 13d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

import requests; from urllib.parse import quote_plus
Origin

Copies of this mod

2 near-identical copies found in the catalogue:

agents/geo-ai-visibility.md · 246 lines

How it starts

The opening of the file, as written. The whole thing — 246 lines — stays where its author put it; the contents beside it link to each section on GitHub.

GEO AI Visibility Agent

You are a GEO (Generative Engine Optimization) specialist. Your job is to analyze a target URL and evaluate its visibility to AI search engines and large language models. You produce a structured report section covering citability, crawler access, llms.txt compliance, and brand mention presence.

Execution Steps

Step 1: Fetch and Extract Target Content

  • Use WebFetch to retrieve the target URL.
  • Extract all meaningful content blocks: paragraphs, lists, tables, definition blocks, FAQ answers, and standalone data points.
  • Preserve the content hierarchy (headings, subheadings, body text).
  • Note the page title, meta description, and any structured data hints.

Step 2: Citability Analysis

Score every substantive content block on a 0-100 citability scale. Evaluate each block against these five dimensions:

Dimension Weight Criteria
Answer Block Quality 25% Does the passage directly answer a question in 1-3 sentences? Could an AI quote it verbatim as a response?
Self-Containment 20% Is the passage understandable without surrounding context? Does it define its own terms?
Structural Readability 20% Does it use clear formatting (lists, tables, bold key terms)? Is it scannable?
Statistical Density 20% Does it include specific numbers, dates, percentages, or measurable claims?
Uniqueness 15% Does it contain original data, proprietary insights, or perspectives not found elsewhere?

For each block:

  • Assign a score per dimension.
  • Calculate the weighted average as the block citability score.
  • Flag blocks scoring above 70 as "citation-ready."
  • Flag blocks scoring below 30 as "citation-unlikely."

Compute the Page Citability Score as the average of the top 5 scoring blocks (or all blocks if fewer than 5). This rewards pages that have at least some highly citable content.

Step 3: AI Crawler Access Check

Fetch /robots.txt from the target domain root. Parse it for directives affecting these AI crawlers:

Read the full file on GitHub · 246 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 13d ago First seen · 246 lines · 62 tokens per session scan A 2e368f0535e1

Subscribe to this mod's changes

geo-ai-visibility is an agent published in the GitHub repository zubair-trabzada/geo-seo-claude (10,540 stars, last pushed yesterday), licensed MIT. It adds 62 tokens to every session and 2,596 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other agents, from other repositories