geo-crawlers

geo-crawlers is a skill for Claude Code from zubair-trabzada/geo-seo-claude. It costs 47 tokens per session (4,391 once invoked), scanned A, original, MIT.

A check of whether AI crawlers can access a website. AI crawlers are automated programs used by AI companies to discover and process web content.

In plain words
What is it for?
Use it to inspect robots.txt, meta tags, and HTTP headers, map crawler access, and identify settings that limit or allow AI services to reach a site.
Why use it?
If these crawlers are blocked by robots.txt, page tags, or HTTP headers, the site’s information may not be available for AI-generated answers.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Good fit Use it to inspect robots.txt, meta tags, and HTTP headers, map crawler access, and identify settings that limit or allow AI services to reach a site.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/zubair-trabzada/geo-seo-claude/geo-crawlers
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.

Any agent
npx skills add zubair-trabzada/geo-seo-claude --skill geo-crawlers
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-crawlers

README.md
[![agentmods](https://agentmods.dev/badge/skills/zubair-trabzada/geo-seo-claude/geo-crawlers/github.svg)](https://agentmods.dev/skills/zubair-trabzada/geo-seo-claude/geo-crawlers)
Your own site
<a href="https://agentmods.dev/skills/zubair-trabzada/geo-seo-claude/geo-crawlers"><img src="https://agentmods.dev/badge/skills/zubair-trabzada/geo-seo-claude/geo-crawlers/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-crawlers

Your own site · 80×15
<a href="https://agentmods.dev/skills/zubair-trabzada/geo-seo-claude/geo-crawlers"><img src="https://agentmods.dev/badge/skills/zubair-trabzada/geo-seo-claude/geo-crawlers.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 47 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,391 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • Socket pass 1 May 2026
  • Snyk warn 1 May 2026
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.00047 $0.04391
Opus 5 $0.00023 $0.02195
Sonnet 5 $0.00009 $0.00878
Haiku 4.5 $0.00005 $0.00439

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

Security

Grade A, and why

geo-crawlers scanned grade A with 0 findings 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.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

Copies of this mod

4 near-identical copies found in the catalogue:

skills/geo-crawlers/SKILL.md · 378 lines

How it starts

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

AI Crawler Access Analysis Skill

Purpose

This skill analyzes a website's accessibility to AI crawlers -- the bots that AI companies use to discover, index, and train on web content. If AI crawlers are blocked, the site's content cannot appear in AI-generated responses regardless of its quality. Crawler access is the foundational technical requirement for GEO.

Key Insight

As of early 2026, many websites inadvertently block AI crawlers through overly aggressive robots.txt rules, inherited from legacy SEO configurations. An Originality.ai 2025 study found that over 35% of the top 1,000 websites block at least one major AI crawler, and 5-10% block all AI crawlers. Blocking AI crawlers is the single fastest way to become invisible in AI-generated search results.


Complete AI Crawler Reference

Tier 1: Critical for AI Search Visibility (RECOMMEND: ALLOW)

These crawlers power the AI search products where users actively look for answers. Blocking them directly reduces your visibility in AI-generated responses.

GPTBot
  • Operator: OpenAI
  • User-Agent: GPTBot
  • Full User-Agent String: Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; GPTBot/1.2; +https://openai.com/gptbot)
  • Purpose: Fetches content for ChatGPT's web browsing, plugins, and search features. Content accessed by GPTBot may be used to improve OpenAI models.
  • Impact of Blocking: Content will NOT appear in ChatGPT Search results or be accessible when users ask ChatGPT to browse the web. This is the highest-impact AI crawler to allow.
  • Recommendation: ALLOW -- ChatGPT has 300M+ weekly active users as of 2025. Blocking GPTBot removes your content from one of the largest AI search surfaces.
OAI-SearchBot
  • Operator: OpenAI
  • User-Agent: OAI-SearchBot
  • Full User-Agent String: Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; OAI-SearchBot/1.0; +https://docs.openai.com/bots/overview)
  • Purpose: Specifically powers ChatGPT's search feature. Unlike GPTBot, content accessed by OAI-SearchBot is NOT used for model training -- only for live search results.
  • Impact of Blocking: Content will not appear in ChatGPT's search results even if GPTBot is allowed.
  • Recommendation: ALLOW -- This is a search-only crawler with no training implications. There is no strategic reason to block it.

Read the full file on GitHub · 378 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 · 378 lines · 47 tokens per session scan A e9429e5b1619

Subscribe to this mod's changes

geo-crawlers is a skill published in the GitHub repository zubair-trabzada/geo-seo-claude (10,540 stars, last pushed yesterday), licensed MIT. It adds 47 tokens to every session and 4,391 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens