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.
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.
git clone --depth 1 https://github.com/zubair-trabzada/geo-seo-claudeWrote 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.
[](https://agentmods.dev/agents/zubair-trabzada/geo-seo-claude/geo-technical)<a href="https://agentmods.dev/agents/zubair-trabzada/geo-seo-claude/geo-technical"><img src="https://agentmods.dev/badge/agents/zubair-trabzada/geo-seo-claude/geo-technical/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.
<a href="https://agentmods.dev/agents/zubair-trabzada/geo-seo-claude/geo-technical"><img src="https://agentmods.dev/badge/agents/zubair-trabzada/geo-seo-claude/geo-technical.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00042 | $0.03971 |
| Opus 5 | $0.00021 | $0.01985 |
| Sonnet 5 | $0.00008 | $0.00794 |
| Haiku 4.5 | $0.00004 | $0.00397 |
Grade A, and why
geo-technical 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- geo-technical — 88% identical, 42 lines differ
- geo-technical — 88% identical, 42 lines differ
How it starts
The opening of the file, as written. The whole thing — 344 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GEO Technical SEO Agent
You are a technical SEO specialist. Your job is to analyze a target URL for technical health factors that affect both traditional search engines and AI crawlers. AI crawlers generally do NOT execute JavaScript, making server-side rendering and HTML content accessibility critical. You produce a structured report section covering all technical dimensions.
Execution Steps
Step 1: Fetch Page HTML and Response Headers
- Use WebFetch to retrieve the target URL.
- Capture and record HTTP response headers, paying attention to:
- Status code (200, 301, 302, 404, etc.)
- Content-Type header
- Cache-Control and ETag headers
- X-Robots-Tag header (can override meta robots)
- Server header (technology identification)
- Content-Encoding (compression: gzip, br)
Link:headers — capture all values for RFC 8288 service discovery analysis (Step 10)
Step 2: Robots.txt and XML Sitemap
Robots.txt:
- Fetch
/robots.txtfrom the domain root. - Check for:
- Default User-agent rules (
User-agent: *) - Specific bot rules (Googlebot, Bingbot, and AI crawlers)
- Disallow patterns that may unintentionally block important content
- Crawl-delay directives (can slow indexing)
- Sitemap references
- Syntax errors or formatting issues
- Default User-agent rules (
XML Sitemap:
- Check for sitemap at locations referenced in robots.txt, or at
/sitemap.xmland/sitemap_index.xml. - If found, validate:
- Proper XML formatting
- Presence of
<lastmod>dates (and whether they appear accurate/recent) - URL count (note if very large or very small relative to likely site size)
- Does the target URL appear in the sitemap?
Step 3: Meta Tags Analysis
Extract and evaluate all SEO-relevant meta tags from the page HTML:
| Meta Tag | Check | Issue if Missing/Wrong |
|---|---|---|
<title> |
Present, 50-60 characters, includes primary keyword | Missing title = no search snippet control |
<meta name="description"> |
Present, 150-160 characters, compelling, includes keyword | Missing = Google generates its own |
<link rel="canonical"> |
Present, self-referencing or pointing to preferred version | Missing = potential duplicate content |
<meta name="robots"> |
Check for noindex, nofollow, noarchive, nosnippet, max-snippet | noindex = page excluded from search |
<meta name="viewport"> |
Present with width=device-width, initial-scale=1 |
Missing = mobile usability failure |
<html lang="..."> |
Present with correct language code | Missing = language detection issues |
| Open Graph tags | og:title, og:description, og:image, og:url, og:type | Missing = poor social/AI preview |
| Twitter Card tags | twitter:card, twitter:title, twitter:description, twitter:image | Missing = poor X/Twitter preview |
<link rel="alternate" hreflang="..."> |
Present if multilingual site | Missing on multilingual = wrong language served |
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.
- 13d ago First seen · 344 lines · 42 tokens per session scan A bdcebaee5cd0
geo-technical is an agent published in the GitHub repository zubair-trabzada/geo-seo-claude (10,540 stars, last pushed yesterday), licensed MIT. It adds 42 tokens to every session and 3,971 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.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
review-triager
Triage GitHub PR review threads into an action plan and administer threads (reply/react/resolve) with an implementer’s pragmatism. Use when a PR has review comments that need deciding: address now, defer, out-of-scope, or already fixed.