SkillAgentSearch skills...

seo-geo

Audit and improve content for AI Overviews and answer engines, including citability, entity clarity, crawler access, brand signals, and passage structure.

Install / Use

npx skills add AgriciDaniel/claude-seo --skill seo-geo

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

95/100

Category

Marketing

Supported Platforms

Universal

Tags

Our assessment of seo-geo

seo-geo scores 95/100 on our quality scale, 45th of 302 Marketing skills we index (top 15%).

Its SKILL.md is 21 KB long, well organised into 27 sections with 1 code example: a thorough specification that gives an agent plenty to work with.

With 17,676 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
30/30
Structure
17/20
Description
15/15
Adoption
18/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated 4 days ago, so seo-geo is actively maintained.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

seo-geo compared with similar skills

All 4 of these similar skills score higher than seo-geo; compare them before choosing.

SkillScoreStarsUpdatedFormat
seo-geo (this skill)by AgriciDaniel9517.7k4d agoSKILL.md
algorithmic-artby anthropics100177.9k5d agoSKILL.md
pptxby anthropics100177.9k5d agoSKILL.md
designby nextlevelbuilder100130.2k6d agoSKILL.md
ui-ux-pro-maxby nextlevelbuilder100130.2k6d agoSKILL.md

Frequently asked questions

How do I install seo-geo?
Run npx skills add AgriciDaniel/claude-seo --skill seo-geo. The install tabs above show the steps for each supported agent.
Which AI agents does seo-geo work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is seo-geo safe to use?
It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is seo-geo still maintained?
The repository was last updated 4 days ago, so seo-geo is actively maintained.

name: seo-geo description: > Audit and improve content for AI Overviews and answer engines, including citability, entity clarity, crawler access, brand signals, and passage structure. user-invocable: true argument-hint: "[url]" license: MIT metadata: author: AgriciDaniel version: "2.4.0" category: seo

AI Search / GEO Optimization (May 2026)

Primary Source: Google's AI Optimization Guide

Google's official position, published under Search Central docs:

"From Google Search's perspective, optimizing for generative AI search is optimizing for the search experience, and thus still SEO."

Read references/google-ai-optimization-guide.md for the full synthesis, myth-busting list (llms.txt, chunking, AI-rephrasing, mention-farming, all rejected by Google as ineffective), and the Who/How/Why test for content quality.

Audits should frame GEO findings as SEO fundamentals applied to AI-search surfaces, not as a separate optimization discipline. When community recommendations contradict Google's primary source, defer to Google and note the contradiction in the report.

Key Statistics

Third-party figures below were not re-verified on 2026-09-23. Quote them only with their source and date, or leave them out.

| Metric | Value | Source | |--------|-------|--------| | AI Overviews reach | 2.5 billion+ monthly active users, reported from Google I/O 2026 keynote coverage; not confirmed on a Google-owned source; 200+ countries | Third-party I/O reporting | | AI Overviews query coverage | ~50% of queries (third-party measurement; varies by country) | Industry data | | AI Mode monthly users | 1B+, reported from Google I/O 2026 keynote coverage; not confirmed on a Google-owned source | Third-party I/O reporting | | AI Mode model | Google upgrades it often (Gemini 3.5 Flash became the default on 2026-05-19, and newer Flash models have shipped since); never tie advice to a model | Google (blog.google) | | AI-referred sessions growth | 527% (Jan-May 2025) | Third-party (attributed to SparkToro; not re-verified) | | ChatGPT weekly active users | 900 million | OpenAI | | Perplexity monthly queries | 500+ million | Perplexity |

Critical Insight: Brand Mentions > Backlinks

Brand mentions correlate 3x more strongly with AI visibility than backlinks. (Ahrefs December 2025 study of 75,000 brands)

| Signal | Correlation with AI Citations | |--------|------------------------------| | YouTube mentions | ~0.737 (strongest) | | Reddit mentions | High | | Wikipedia presence | High | | LinkedIn presence | Moderate | | Domain Rating (backlinks) | ~0.266 (weak) |

Only 11% of domains are cited by both ChatGPT and Google AI Overviews for the same query, so platform-specific optimization is essential.


GEO Analysis Criteria (Updated)

1. Citability Score (25%)

Self-contained answer blocks are easy for AI systems to quote. Third-party studies suggest roughly 130-170 words; this is a readability heuristic, not a Google requirement (Google's AI optimization guide says you do not need to chunk content for AI). And ~44% of AI citations come from the first 30% of a page (SE Ranking study), front-load your most citable, self-contained answer rather than burying it below the fold.

Strong signals:

  • Clear, quotable sentences with specific facts/statistics
  • Self-contained answer blocks (can be extracted without context)
  • Direct answer in first 40-60 words of section
  • Claims attributed with specific sources
  • Definitions following "X is..." or "X refers to..." patterns
  • Unique data points not found elsewhere

Weak signals:

  • Vague, general statements
  • Opinion without evidence
  • Buried conclusions
  • No specific data points

2. Structural Readability (20%)

92% of AI Overview citations come from top-10 ranking pages, but 47% come from pages ranking below position 5, demonstrating different selection logic.

Strong signals:

  • Clean H1->H2->H3 heading hierarchy
  • Question-based headings (matches query patterns)
  • Short paragraphs (2-4 sentences)
  • Tables for comparative data
  • Ordered/unordered lists for step-by-step or multi-item content
  • FAQ sections with clear Q&A format

Weak signals:

  • Wall of text with no structure
  • Inconsistent heading hierarchy
  • No lists or tables
  • Information buried in paragraphs

3. Multi-Modal Content (15%)

Multi-modal content can support selection in AI answers (third-party claims only; no primary source gives a figure).

Check for:

  • Text + relevant images
  • Video content (embedded or linked)
  • Infographics and charts
  • Interactive elements (calculators, tools)
  • Structured data supporting media

4. Authority & Brand Signals (20%)

Strong signals:

  • Author byline with credentials
  • Publication date and last-updated date
  • Recency, content under 3 months old is ~3x more likely to be cited in AI answers; pages left stale 6+ months lose citation eligibility (SE Ranking, 1.3M-citation study). A scheduled refresh program is one of the highest-leverage GEO plays.
  • Citations to primary sources (studies, official docs, data)
  • Organization credentials and affiliations
  • Expert quotes with attribution
  • Entity presence in Wikipedia, Wikidata
  • Mentions on Reddit, YouTube, LinkedIn

Weak signals:

  • Anonymous authorship
  • No dates
  • No sources cited
  • No brand presence across platforms

5. Technical Accessibility (20%)

Many AI crawlers fetch raw HTML without running JavaScript (for example GPTBot and PerplexityBot in public tests), while Googlebot renders JavaScript and feeds AI Overviews and AI Mode. Server-side rendering keeps content visible to all of them.

Check for:

  • Server-side rendering (SSR) vs client-only content
  • AI crawler access in robots.txt
  • llms.txt presence (reported for completeness; it carries no weight in this score, see references/llmstxt-evidence.md)
  • RSL 1.0 licensing terms

AI Crawler Detection

Check robots.txt for these AI crawlers:

| Crawler | Owner | Purpose | Obeys robots.txt? | |---------|-------|---------|---| | GPTBot | OpenAI | Model training only (NOT ChatGPT Search) | yes | | OAI-SearchBot | OpenAI | ChatGPT Search citability (the crawler that decides it) | yes | | ChatGPT-User | OpenAI | ChatGPT browsing (user-triggered) | "may not apply" per OpenAI (user-triggered) | | ClaudeBot | Anthropic | Model training only (NOT Claude's search features) | yes | | Claude-SearchBot | Anthropic | Claude/Claude.ai search-result citability (the crawler that decides it) | yes | | Claude-User | Anthropic | Claude browsing on a user's behalf (user-triggered) | yes (Anthropic: all three bots honor robots.txt) | | PerplexityBot | Perplexity | Perplexity AI search (not used to crawl for foundation-model training) | yes | | Perplexity-User | Perplexity | Fetches for a user's question (user-triggered) | generally ignores | | CCBot | Common Crawl | Training data (often blocked) | yes | | Bytespider | ByteDance | TikTok/Douyin AI | yes | | cohere-ai | Cohere | Cohere models | yes | | Google-Extended | Google | Gemini/Vertex training & grounding only (NOT Google Search) | yes | | Google-CloudVertexBot | Google | Site-owner-requested Vertex AI Agent crawls | yes | | Google-Agent | Google | User-triggered agent fetches (agentic browsing for a user) | no (user-triggered) | | Google-GeminiNotebook | Google | Fetches individual user-added source URLs (replaced Google-NotebookLM, supported until August 2026) | no (user-triggered) | | Google Messages | Google | User-triggered fetch | no (user-triggered) | | Applebot-Extended | Apple | Apple Intelligence / generative-AI training data opt-out only (NOT Siri, Spotlight, or Safari search; does not itself crawl, it labels content already fetched by Applebot) | yes |

Sources: OpenAI crawlers, Google crawlers overview, Anthropic crawler support article, Apple Applebot-Extended support article. Anthropic's current crawler support article documents only ClaudeBot, Claude-User, and Claude-SearchBot; it does not list anthropic-ai, so the previously-unverified anthropic-ai row has been removed rather than kept as a guess.

Recommendation: Allow OAI-SearchBot, Claude-SearchBot, and PerplexityBot for AI search visibility. GPTBot, ClaudeBot, CCBot, and Applebot-Extended are training-only signals -- allow or block them on licensing preference, not on search-visibility grounds.

Check the right bot for the claim you are making

Two pairs are routinely conflated. Each claim below may only be supported by its own bot's robots.txt status -- check them separately and report them separately.

| Claim you want to make | Bot to check | Bot that does NOT support this claim | |---|---|---| | "Content is citable in ChatGPT Search" | OAI-SearchBot | GPTBot | | "Content is available for OpenAI model training" | GPTBot | OAI-SearchBot | | "Content can be used for Gemini/Vertex training & grounding" | Google-Extended | Googlebot | | "Content is eligible for Google Search / AI Overviews" | Googlebot | Google-Extended | | "Content is citable in Claude's search features" | Claude-SearchBot | ClaudeBot | | "Content is available for Anthropic model training" | ClaudeBot | Claude-SearchBot | | "Content can be used for Apple Intelligence training" | Applebot-Extended | Applebot | | "Content is discoverable via Siri, Spotlight, or Safari search" | Applebot | Applebot-Extended |

  • Google-Extended governs Gemini and Vertex AI training and grounding use only. It does not affect inclusion in ordinary Google Search, or in AI Overviews and AI Mode, both of which are served from the Googlebot index. Never score Google-Extended as a "Google Search readiness" signal, and never cite a blocked Google-Extended as evidence that a site is missing from Google Search.
  • OAI-SearchBot is the crawler that determines ChatGPT Search citability. GPTBot is OpenAI's separate training crawler. Checking GPTBot access tells you nothing about whether ChatGPT Search can cite the page. A site that blocks GPTBot and allows OAI-SearchBot is fully citable in ChatGPT Search.
  • Claude-SearchBot is the crawler that determines citability in Claude's own search features. ClaudeBot is Anthropic's separate training crawler (per Anthropic's crawler support article). Checking ClaudeBot access tells you nothing about Claude search citability, and vice versa; report each separately.
  • Applebot-Extended is a training-data opt-out signal, not a crawler that fetches pages itself. Per Apple's support article, disallowing Applebot-Extended opts a site out of Apple Intelligence / generative-model training use, but the page remains discoverable through Siri, Spotlight, and Safari as long as Applebot itself is allowed. Never cite a blocked Applebot-Extended as evidence a site is missing from Apple's search surfaces.

Do not use these names interchangeably in report prose. When reporting crawler access, name the specific user-agent that was checked and the specific capability it governs.

Google's user-triggered fetchers generally ignore robots.txt rules (Google-Agent, Google-GeminiNotebook, Google Messages); OpenAI says robots.txt "may not apply" to ChatGPT-User, while Anthropic's Claude-User honors it. robots.txt cannot block them, use server-side access controls. Google's canonical crawling/robots reference moved to developers.google.com/crawling (migrated 2025-11-20); IP-range files now live at /crawling/ipranges/ and googlebot.json was renamed common-crawlers.json. Emerging: **Web Bot

Truncated for display — read the full file on GitHub.

Related Skills

View on GitHub
GitHub Stars17.7k
CategoryMarketing
Updated4d ago
Forks2.6k

Languages

Python

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions