seo-geo

agricidaniel/claude-seo · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/agricidaniel/claude-seo --skill seo-geo
0 commentsdiscussion
summary

Brand mentions correlate 3x more strongly with AI visibility than backlinks.

  • (Ahrefs December 2025 study of 75,000 brands)
skill.md

AI Search / GEO Optimization (February 2026)

Key Statistics

Metric Value Source
AI Overviews reach 1.5 billion users/month across 200+ countries Google
AI Overviews query coverage 50%+ of all queries Industry data
AI-referred sessions growth 527% (Jan-May 2025) SparkToro
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%)

Optimal passage length: 134-167 words for AI citation.

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%)

Content with multi-modal elements sees 156% higher selection rates.

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
  • 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%)

AI crawlers do NOT execute JavaScript. Server-side rendering is critical.

Check for:

  • Server-side rendering (SSR) vs client-only content
  • AI crawler access in robots.txt
  • llms.txt file presence and configuration
  • RSL 1.0 licensing terms

AI Crawler Detection

Check robots.txt for these AI crawlers:

Crawler Owner Purpose
GPTBot OpenAI ChatGPT web search
OAI-SearchBot OpenAI OpenAI search features
ChatGPT-User OpenAI ChatGPT browsing
ClaudeBot Anthropic Claude web features
PerplexityBot Perplexity Perplexity AI search
CCBot Common Crawl Training data (often blocked)
anthropic-ai Anthropic Claude training
Bytespider ByteDance TikTok/Douyin AI
cohere-ai Cohere Cohere models

Recommendation: Allow GPTBot, OAI-SearchBot, ClaudeBot, PerplexityBot for AI search visibility. Block CCBot and training crawlers if desired.


llms.txt Standard

The emerging llms.txt standard provides AI crawlers with structured content guidance.

Location: /llms.txt (root of domain)

Format:

# Title of site
> Brief description

## Main sections
- [Page title](url): Description
- [Another page](url): Description

## Optional: Key facts
- Fact 1
- Fact 2

Check for:

  • Presence of /llms.txt
  • Structured content guidance
  • Key page highlights
  • Contact/authority information

RSL 1.0 (Really Simple Licensing)

New standard (December 2025) for machine-readable AI licensing terms.

Backed by: Reddit, Yahoo, Medium, Quora, Cloudflare, Akamai, Creative Commons

Check for: RSL implementation and appropriate licensing terms.


Platform-Specific Optimization

Platform Key Citation Sources Optimization Focus
Google AI Overviews Top-10 ranking pages (92%) Traditional SEO + passage optimization
ChatGPT Wikipedia (47.9%), Reddit (11.3%) Entity presence, authoritative sources
Perplexity Reddit (46.7%), Wikipedia Community validation, discussions
Bing Copilot Bing index, authoritative sites Bing SEO, IndexNow

Output

Generate GEO-ANALYSIS.md with:

  1. GEO Readiness Score: XX/100
  2. Platform breakdown (Google AIO, ChatGPT, Perplexity scores)
  3. AI Crawler Access Status (which crawlers allowed/blocked)
  4. llms.txt Status (present, missing, recommendations)
  5. Brand Mention Analysis (presence on Wikipedia, Reddit, YouTube, LinkedIn)
  6. Passage-Level Citability (optimal 134-167 word blocks identified)
  7. Server-Side Rendering Check (JavaScript dependency analysis)
  8. Top 5 Highest-Impact Changes
  9. Schema Recommendations (for AI discoverability)
  10. Content Reformatting Suggestions (specific passages to rewrite)

Quick Wins

  1. Add "What is [topic]?" definition in first 60 words
  2. Create 134-167 word self-contained answer blocks
  3. Add question-based H2/H3 headings
  4. Include specific statistics with sources
  5. Add publication/update dates
  6. Implement Person schema for authors
  7. Allow key AI crawlers in robots.txt

Medium Effort

  1. Create /llms.txt file
  2. Add author bio with credentials + Wikipedia/LinkedIn links
  3. Ensure server-side rendering for key content
  4. Build entity presence on Reddit, YouTube
  5. Add comparison tables with data
  6. Implement FAQ sections (structured, not schema for commercial sites)

High Impact

  1. Create original research/surveys (unique citability)
  2. Build Wikipedia presence for brand/key people
  3. Establish YouTube channel with content mentions
  4. Implement comprehensive entity linking (sameAs across platforms)
  5. Develop unique tools or calculators

DataForSEO Integration (Optional)

If DataForSEO MCP tools are available, use ai_optimization_chat_gpt_scraper to check what ChatGPT web search returns for target queries (real GEO visibility check) and ai_opt_llm_ment_search with ai_opt_llm_ment_top_domains for LLM mention tracking across AI platforms.

Error Handling

Scenario Action
URL unreachable (DNS failure, connection refused) Report the error clearly. Do not guess site content. Suggest the user verify the URL and try again.
AI crawlers blocked by robots.txt Report exactly which crawlers are blocked and which are allowed. Provide specific robots.txt directives to add for enabling AI search visibility.
No llms.txt found Note the absence and provide a ready-to-use llms.txt template based on the site's content structure.
No structured data detected Report the gap and provide specific schema recommendations (Article, Organization, Person) for improving AI discoverability.
how to use seo-geo

How to use seo-geo on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add seo-geo
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/agricidaniel/claude-seo --skill seo-geo

The skills CLI fetches seo-geo from GitHub repository agricidaniel/claude-seo and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/seo-geo

Reload or restart Cursor to activate seo-geo. Access the skill through slash commands (e.g., /seo-geo) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

Task Automation & Efficiency

Automate repetitive workflows and reduce manual effort

Example

Generate reports, summarize documents, draft communications

Save 3-5 hours per week on routine tasks

Knowledge Enhancement

Learn new skills, understand complex topics, get expert guidance

Example

Explain concepts, provide examples, suggest learning resources

Accelerate learning and skill development by 2x

Quality Improvement

Enhance output quality through reviews, suggestions, and refinements

Example

Review drafts, suggest improvements, catch errors

Improve work quality by 30-40% with less effort

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client with skill support
  • Clear understanding of task or problem to solve
  • Willingness to iterate and refine outputs

Time Estimate

15-45 minutes depending on use case complexity

Installation Steps

  1. 1.Install skill using provided installation command
  2. 2.Test with simple use case relevant to your work
  3. 3.Evaluate output quality and relevance
  4. 4.Iterate on prompts to improve results
  5. 5.Integrate into regular workflow if valuable

Common Pitfalls

  • Expecting perfect results without iteration
  • Not providing enough context in prompts
  • Using skill for tasks outside its intended scope
  • Accepting outputs without review and validation

Best Practices

✓ Do

  • +Start with clear, specific prompts
  • +Provide relevant context and constraints
  • +Review and refine all outputs before using
  • +Iterate to improve output quality
  • +Document successful prompt patterns

✗ Don't

  • Don't use without understanding skill limitations
  • Don't skip validation of outputs
  • Don't share sensitive information in prompts
  • Don't expect skill to replace human judgment

💡 Pro Tips

  • Be specific about desired format and style
  • Ask for multiple options to choose from
  • Request explanations to understand reasoning
  • Combine AI efficiency with human expertise

When to Use This

✓ Use When

Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.

✗ Avoid When

Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.

Learning Path

  1. 1Familiarize yourself with skill capabilities and limitations
  2. 2Start with low-risk, non-critical tasks
  3. 3Progress to more complex and valuable use cases
  4. 4Build expertise through regular use and experimentation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.854 reviews
  • Aarav Diallo· Dec 28, 2024

    seo-geo fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Pratham Ware· Dec 20, 2024

    seo-geo is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Olivia Robinson· Dec 20, 2024

    Useful defaults in seo-geo — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Kwame Gill· Dec 20, 2024

    seo-geo has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Aarav Abebe· Dec 16, 2024

    I recommend seo-geo for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Noah Thompson· Nov 15, 2024

    seo-geo is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Aarav Zhang· Nov 11, 2024

    We added seo-geo from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Jin Ghosh· Nov 11, 2024

    Solid pick for teams standardizing on skills: seo-geo is focused, and the summary matches what you get after install.

  • Aanya Bansal· Nov 7, 2024

    Keeps context tight: seo-geo is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Aanya Gill· Oct 26, 2024

    Registry listing for seo-geo matched our evaluation — installs cleanly and behaves as described in the markdown.

showing 1-10 of 54

1 / 6