New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

GEO Technical SEO Audit

by zubair-trabzada in zubair-trabzada/geo-seo-claude

Audits a site's technical SEO across eight categories with a focus on AI crawler access and server-side rendering, scoring each and writing a report file.

MITAuto-check: notesMarketing & SEO

Install GEO Technical SEO Audit

skills CLI
$ npx skills add zubair-trabzada/geo-seo-claude --skill geo-technical -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install zubair-trabzada/geo-seo-claude geo-technical --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/zubair-trabzada/geo-seo-claude.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/geo-technical .claude/skills/geo-technical && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
geo-technical
GitHub stars
11k
Used in
2 other repos
Token cost
~5.7k tokens
SKILL.md length
2,564 words
Files
1
Skills in repo
16
Repo updated
First seen
Licence
MIT

At a glance

Audits a site's technical SEO across eight categories with a focus on AI crawler access and server-side rendering, scoring each and writing a report file.

  • Works in 5 steps: Collect the target URL (homepage + 2-3… → Fetch each page using curl/WebFetch to… → Run through each of the 8 audit… → …
  • Checking whether a site's robots.txt blocks AI crawlers like GPTBot or PerplexityBot
  • SKILL.md covers Purpose, How to Use This Skill, Category 1: Crawlability (15… and Category 2: Indexability (12…, plus 4 more sections
  • Calls curl

What it does

The audit fetches a homepage plus two or three inner pages by URL, HTML and headers, then scores eight technical categories, with crawlability worth 15 points in the excerpt shown. Within crawlability it checks robots.txt validity, the presence of a sitemap directive, and specifically AI crawler access: whether directives block GPTBot, Google-Extended, Googlebot, Bingbot, PerplexityBot, ClaudeBot, Amazonbot, CCBot, FacebookExternalHit, Bytespider or Applebot-Extended.

Scoring for AI crawler access ranges from 5 points when all major crawlers are allowed down to 0 when Googlebot itself is blocked, and the skill notes that blocking Google-Extended only affects AI training data use, not search indexing, though it may reduce presence in AI Overviews. The excerpt's rationale is that AI crawlers do not execute JavaScript, so server-side rendering and open AI crawler access are treated as critical to GEO. Results are written to a GEO-TECHNICAL-AUDIT.md file.

When your agent uses it

  • Checking whether a site's robots.txt blocks AI crawlers like GPTBot or PerplexityBot
  • Auditing a site's crawlability and indexability for AI search visibility
  • Verifying server-side rendering before an AI search optimization push

Example prompts

  • “Run a GEO technical audit on example.com and its top two inner pages.”
  • “Check whether our robots.txt is blocking any major AI crawlers.”
  • “Score our site's crawlability and sitemap setup for AI search visibility.”

Requirements

  • Network access to fetch the target site's pages, robots.txt and headers
  • Pre-approved tools (allowed-tools): Read, Grep, Glob, Bash, WebFetch, Write

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Collect the target URL (homepage + 2-3 key inner pages)
  2. Fetch each page using curl/WebFetch to get raw HTML and HTTP headers
  3. Run through each of the 8 audit categories below
  4. Score each category using the rubric
  5. Generate GEO-TECHNICAL-AUDIT.md with results

What it can do on your machine

Read from SKILL.md and the folder at commit 989cae0. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Grep
    • Glob
    • Bash
    • WebFetch
    • Write

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • curl

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use curl, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

GEO Technical SEO Audit loads about 5.7k tokens when it runs. Until then it costs about 35 tokens; SKILL.md has 2,564 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~35
When it runs · the whole SKILL.md, loaded when a task matches
~5.7k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
    allowed-tools: Read, Grep, Glob, Bash, WebFetch, Write

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from zubair-trabzada/geo-seo-claude at commit 989cae0, republished under its MIT licence (© zubair-trabzada). 2,564 words, ~5,669 tokens.

Download SKILL.mdSave it as .claude/skills/geo-technical/SKILL.md (or your agent's skills folder).
name
geo-technical
description
Technical SEO audit with GEO-specific checks — crawlability, indexability, security, performance, SSR, and AI crawler access
allowed-tools
Read, Grep, Glob, Bash, WebFetch, Write
version
1.0.0
author
geo-seo-claude
tags
geo, technical-seo, core-web-vitals, ssr, crawlability, security, performance

GEO Technical SEO Audit

Purpose

Technical SEO forms the foundation of both traditional search visibility and AI search citation. A technically broken site cannot be crawled, indexed, or cited by any platform. This skill audits 8 categories of technical health with specific attention to GEO requirements — most critically, server-side rendering (AI crawlers do not execute JavaScript) and AI crawler access (many sites inadvertently block AI crawlers in robots.txt).

How to Use This Skill

  1. Collect the target URL (homepage + 2-3 key inner pages)
  2. Fetch each page using curl/WebFetch to get raw HTML and HTTP headers
  3. Run through each of the 8 audit categories below
  4. Score each category using the rubric
  5. Generate GEO-TECHNICAL-AUDIT.md with results

Category 1: Crawlability (15 points)

1.1 robots.txt Validity
  • Fetch https://[domain]/robots.txt
  • Check for syntactic validity: proper User-agent, Allow, Disallow directives
  • Check for common errors: missing User-agent, wildcards blocking important paths, Disallow: / blocking entire site
  • Verify XML sitemap is referenced: Sitemap: https://[domain]/sitemap.xml
1.2 AI Crawler Access (CRITICAL for GEO)

Check robots.txt for directives targeting these AI crawlers:

CrawlerUser-AgentPlatform
GPTBotGPTBotChatGPT / OpenAI
Google-ExtendedGoogle-ExtendedGemini / Google AI training
GooglebotGooglebotGoogle Search + AI Overviews
BingbotbingbotBing Copilot + ChatGPT (via Bing)
PerplexityBotPerplexityBotPerplexity AI
ClaudeBotClaudeBotAnthropic Claude
AmazonbotAmazonbotAlexa / Amazon AI
CCBotCCBotCommon Crawl (used by many AI models)
FacebookBotFacebookExternalHitMeta AI
BytespiderBytespiderTikTok / ByteDance AI
Applebot-ExtendedApplebot-ExtendedApple Intelligence

Scoring for AI crawler access:

  • All major AI crawlers allowed: 5 points
  • Some blocked but Googlebot + Bingbot allowed: 3 points
  • GPTBot or PerplexityBot blocked: 1 point (significant GEO impact)
  • Googlebot blocked: 0 points (fatal)

Important nuance: Blocking Google-Extended does NOT block Googlebot. Google-Extended only controls AI training data usage, not search indexing. However, blocking Google-Extended may reduce presence in AI Overviews. Recommend allowing Google-Extended unless there is a specific data licensing concern.

1.3 XML Sitemaps
  • Fetch sitemap (check robots.txt for location, or try /sitemap.xml, /sitemap_index.xml)
  • Validate XML syntax
  • Check for <lastmod> dates (should be present and accurate)
  • Count URLs — compare to expected number of indexable pages
  • Check for sitemap index if large site (50,000+ URLs per sitemap max)
  • Verify all sitemap URLs return 200 status codes (sample check)
1.4 Crawl Depth
  • Homepage = depth 0. Check that all important pages are reachable within 3 clicks (depth 3)
  • Pages at depth 4+ receive significantly less crawl budget and are less likely to be cited by AI
  • Check internal linking: are key content pages linked from the homepage or main navigation?
1.5 Noindex Management
  • Check for <meta name="robots" content="noindex"> on pages that SHOULD be indexed
  • Check for X-Robots-Tag: noindex HTTP headers
  • Common mistakes: noindex on paginated pages, category pages, or key landing pages

Category Scoring:

CheckPoints
robots.txt valid and complete3
AI crawlers allowed5
XML sitemap present and valid3
Crawl depth within 3 clicks2
No erroneous noindex directives2

Category 2: Indexability (12 points)

2.1 Canonical Tags
  • Every indexable page must have a <link rel="canonical" href="..."> tag
  • Canonical must point to itself (self-referencing) for the authoritative version
  • Check for conflicting canonicals (canonical in HTML vs. HTTP header)
  • Check for canonical chains (A canonicals to B, B canonicals to C — should be A to C)
2.2 Duplicate Content
  • Check for www vs. non-www (both should resolve, one should redirect)
  • Check for HTTP vs. HTTPS (HTTP should redirect to HTTPS)
  • Check for trailing slash consistency (pick one pattern and redirect the other)
  • Check for parameter-based duplicates (?sort=price creating duplicate pages)
2.3 Pagination
  • If paginated content exists, check for rel="next" / rel="prev" (note: Google ignores these as of 2019, but Bing still uses them)
  • Preferred: use rel="canonical" on paginated pages pointing to a view-all page or the first page
  • Ensure paginated pages are not noindexed if they contain unique content
2.4 Hreflang (international sites)
  • Check for <link rel="alternate" hreflang="xx"> tags
  • Validate: reciprocal hreflang (if page A points to page B, B must point back to A)
  • Validate: x-default fallback exists
  • Check for language/region code validity (ISO 639-1 / ISO 3166-1)
2.5 Index Bloat
  • Estimate number of indexed pages (check sitemap count, use site:domain.com estimate)
  • Compare indexed pages to actual valuable content pages
  • Flag if indexed pages significantly exceed content pages (index bloat from thin/duplicate/parameter pages)

Category Scoring:

CheckPoints
Canonical tags correct on all pages3
No duplicate content issues3
Pagination handled correctly2
Hreflang correct (if applicable)2
No index bloat2

Category 3: Security (10 points)

3.1 HTTPS Enforcement
  • Site must load over HTTPS
  • HTTP must redirect to HTTPS (301 redirect)
  • No mixed content warnings (HTTP resources on HTTPS pages)
  • SSL/TLS certificate must be valid and not expired
3.2 Security Headers

Check HTTP response headers for:

HeaderRequired ValuePurpose
Strict-Transport-Securitymax-age=31536000; includeSubDomainsForces HTTPS
Content-Security-PolicyAppropriate policyPrevents XSS
X-Content-Type-OptionsnosniffPrevents MIME sniffing
X-Frame-OptionsDENY or SAMEORIGINPrevents clickjacking
Referrer-Policystrict-origin-when-cross-origin or stricterControls referrer data
Permissions-PolicyAppropriate restrictionsControls browser features

Category Scoring:

CheckPoints
HTTPS enforced with valid cert4
HSTS header present2
X-Content-Type-Options1
X-Frame-Options1
Referrer-Policy1
Content-Security-Policy1

Category 4: URL Structure (8 points)

4.1 Clean URLs
  • URLs should be human-readable: /blog/seo-guide not /blog?id=12345
  • No session IDs in URLs
  • Lowercase only (no mixed case)
  • Hyphens for word separation (not underscores)
  • No special characters or encoded spaces
4.2 Logical Hierarchy
  • URL path should reflect site architecture: /category/subcategory/page
  • Flat where appropriate — avoid unnecessarily deep nesting
  • Consistent pattern across the site
4.3 Redirect Chains
  • Check for redirect chains (A redirects to B redirects to C)
  • Maximum 1 hop recommended (A redirects to C directly)
  • Check for redirect loops
  • All redirects should be 301 (permanent), not 302 (temporary), unless intentionally temporary
4.4 Parameter Handling
  • URL parameters should not create duplicate indexable pages
  • Use canonical tags or robots.txt Disallow for parameter variations
  • Configure parameter handling in Google Search Console and Bing Webmaster Tools

Category Scoring:

CheckPoints
Clean, readable URLs2
Logical hierarchy2
No redirect chains (max 1 hop)2
Parameter handling configured2

Category 5: Mobile Optimization (10 points)

Critical Context

As of July 2024, Google crawls ALL sites exclusively with mobile Googlebot. There is no desktop crawling. If your site does not work on mobile, it does not work for Google. Period.

5.1 Responsive Design
  • Check for <meta name="viewport" content="width=device-width, initial-scale=1">
  • Content must not require horizontal scrolling on mobile
  • No fixed-width layouts wider than viewport
5.2 Tap Targets
  • Interactive elements (buttons, links) must be at least 48x48 CSS pixels
  • Minimum 8px spacing between tap targets
  • Check that navigation is usable on mobile
5.3 Font Sizes
  • Base font size should be at least 16px
  • No text requiring zoom to read
  • Sufficient contrast ratio (WCAG AA: 4.5:1 for normal text, 3:1 for large text)
5.4 Mobile Content Parity
  • All content visible on desktop must also be visible on mobile
  • No hidden content behind "read more" toggles that Googlebot cannot expand (though Google has improved at expanding these as of 2025)
  • Images and media must load on mobile

Category Scoring:

CheckPoints
Viewport meta tag correct3
Responsive layout (no horizontal scroll)3
Tap targets appropriately sized2
Font sizes legible2

Category 6: Core Web Vitals (15 points)

2026 Metrics and Thresholds

Core Web Vitals use the 75th percentile of real user data (field data) as the benchmark. Lab data is useful for debugging but field data determines the ranking signal.

MetricGoodNeeds ImprovementPoorNotes
LCP (Largest Contentful Paint)< 2.5s2.5s - 4.0s> 4.0sMeasures loading — time until largest visible element renders
INP (Interaction to Next Paint)< 200ms200ms - 500ms> 500msReplaced FID in March 2024. Measures ALL interactions, not just first
CLS (Cumulative Layout Shift)< 0.10.1 - 0.25> 0.25Measures visual stability — unexpected layout movements
How to Assess Without CrUX Data

When real user data is unavailable, estimate from page characteristics:

  • LCP: Check largest above-fold element. Is it an image (check size/format)? Is it text (check web font loading)? Server response time (TTFB)?
  • INP: Check for heavy JavaScript on page. Long tasks (>50ms) block interactivity. Check for third-party scripts.
  • CLS: Check for images without explicit width/height. Check for dynamically inserted content above the fold. Check for web fonts causing layout shift (FOUT/FOIT).
Common LCP Fixes
  1. Optimize hero images: WebP/AVIF format, correct sizing, preload with <link rel="preload">
  2. Reduce server response time (TTFB < 800ms)
  3. Eliminate render-blocking CSS/JS
  4. Preconnect to critical third-party origins
Common INP Fixes
  1. Break up long tasks (>50ms) into smaller chunks using requestIdleCallback or scheduler.yield()
  2. Reduce third-party JavaScript
  3. Use content-visibility: auto for off-screen content
  4. Debounce/throttle event handlers
Common CLS Fixes
  1. Always include width and height attributes on images and videos
  2. Reserve space for ads and embeds with CSS aspect-ratio or explicit dimensions
  3. Use font-display: swap with size-adjusted fallback fonts
  4. Avoid inserting content above existing content after page load

Category Scoring:

CheckPoints
LCP < 2.5s5
INP < 200ms5
CLS < 0.15

Category 7: Server-Side Rendering (15 points) — CRITICAL FOR GEO

Why SSR Is Mandatory for AI Visibility

AI crawlers (GPTBot, PerplexityBot, ClaudeBot, etc.) do NOT execute JavaScript. They fetch the raw HTML and parse it. If your content is rendered client-side by React, Vue, Angular, or any other JavaScript framework, AI crawlers see an empty page.

Even Googlebot, which does execute JavaScript, deprioritizes JS-rendered content due to the additional crawl budget required. Google processes JS rendering in a separate "rendering queue" that can delay indexing by days or weeks.

Show full SKILL.md (1,014 more words)Show less
Detection Method
  1. Fetch the page with curl (no JavaScript execution): curl -s [URL]
  2. Compare the raw HTML to the rendered DOM (via browser)
  3. If key content (headings, paragraphs, product info, article text) is MISSING from the curl output, the site relies on client-side rendering
What to Check
  • Main content text: Is the article body / product description / page content in the raw HTML?
  • Headings: Are H1, H2, H3 tags present in raw HTML?
  • Navigation: Is the main navigation server-rendered?
  • Structured data: Is JSON-LD in the raw HTML or injected by JavaScript?
  • Meta tags: Are title, description, canonical, OG tags in the raw HTML?
  • Internal links: Are navigation and content links in the raw HTML? (Critical for crawlability)
SSR Solutions to Recommend
FrameworkSSR Solution
ReactNext.js (SSR/SSG), Remix, Gatsby (SSG)
VueNuxt.js (SSR/SSG)
AngularAngular Universal
SvelteSvelteKit
GenericPrerender.io (prerendering service), Rendertron
Scoring Detail
  • All key content server-rendered: 15 points
  • Main content server-rendered but some elements JS-only: 10 points
  • Critical content requires JS (product info, article text): 5 points
  • Entire page is client-rendered (empty body in raw HTML): 0 points

Category Scoring:

CheckPoints
Main content in raw HTML8
Meta tags + structured data in raw HTML4
Internal links in raw HTML3

Category 8: Page Speed & Server Performance (15 points)

8.1 Time to First Byte (TTFB)
  • Target: < 800ms (ideally < 200ms)
  • Measure with curl: curl -o /dev/null -s -w 'TTFB: %{time_starttransfer}s\n' [URL]
  • If TTFB > 800ms: check server location, caching, database queries, CDN usage
8.2 Resource Optimization
  • Total page weight target: < 2MB (critical pages < 1MB)
  • Check for uncompressed resources (gzip/brotli compression should be enabled)
  • Check for unminified CSS and JavaScript
  • Check for unused CSS/JS (can represent 50%+ of downloaded bytes on many sites)
8.3 Image Optimization
  • Check image formats: WebP or AVIF preferred over JPEG/PNG
  • Check for oversized images (images larger than display size)
  • Check for lazy loading: images below fold should have loading="lazy"
  • Check for explicit dimensions (width/height attributes prevent CLS)
  • Above-fold images should NOT be lazy loaded (harms LCP)
8.4 Code Splitting and Lazy Loading
  • JavaScript should be code-split so each page only loads what it needs
  • Check for large JavaScript bundles (> 200KB compressed is a warning, > 500KB is critical)
  • Third-party scripts should load asynchronously (async or defer)
  • Check for render-blocking resources in <head>
8.5 Caching
  • Check Cache-Control headers on static resources (images, CSS, JS)
  • Static assets should have long cache times: max-age=31536000 (1 year) with content-hashed filenames
  • HTML pages should have shorter cache or no-cache with validation (ETag or Last-Modified)
8.6 CDN Usage
  • Check if static resources are served from a CDN (different domain or CDN-specific headers)
  • For global audience, CDN is critical for consistent performance
  • Check for CDN-specific headers: CF-Ray (Cloudflare), X-Cache (AWS CloudFront), X-Served-By (Fastly)

Category Scoring:

CheckPoints
TTFB < 800ms3
Page weight < 2MB2
Images optimized (format, size, lazy)3
JS bundles reasonable (< 200KB compressed)2
Compression enabled (gzip/brotli)2
Cache headers on static resources2
CDN in use1

Category 9: Agent-Readiness Signals (non-scoring)

These checks surface emerging AI agent compatibility signals. None contribute to the numeric score — they produce a pass or a recommendation. The underlying standards are either IETF drafts or early-adoption features; penalizing absence would be unfair.

RFC 8288 (Web Linking) defines the HTTP Link: response header. Servers can use it to advertise related resources — API catalog, service docs, MCP server card — in a machine-readable way, without HTML parsing.

How to check: Capture all Link: response headers from the standard homepage fetch (no extra request).

What to look for:

  • Parse <url>; rel="relation-type" pairs.
  • High-value rel types: api-catalog (RFC 9609), describedby, service-doc, mcp-server-card.

When to surface a recommendation: Only for API-first sites (API docs linked in nav, /api/ or /developers/ paths, swagger/OpenAPI in sitemap). Omit this section entirely for standard business sites — absence is expected and not noteworthy.

StateTreatment
Link: headers present, known rel typesInformational — document what was found
Link: headers present, unknown rel typesInformational — note and explain
Absent, API-first siteRecommendation — explain and suggest implementation
Absent, standard business siteOmit — do not surface
9.2 Markdown Content Negotiation

Checks if the server responds to Accept: text/markdown with Content-Type: text/markdown. Cloudflare's "Markdown for Agents" feature enables this — AI agents receive clean Markdown instead of HTML, eliminating boilerplate stripping and improving content extraction accuracy.

How to check: Send a GET to the homepage with Accept: text/markdown. This is one additional HTTP request per audit.

Evaluation:

  • If response Content-Type is text/markdown (or text/markdown; charset=utf-8): pass — note as a leading-edge capability.
  • Otherwise: forward-looking recommendation, not a failure.
  • If the request errors or returns non-200: skip and note the error. Do not penalize.
StateTreatment
text/markdown returnedBonus — note as a leading-edge capability
Standard HTML returnedForward-looking recommendation
Request errors / non-200Skip, note the error, do not penalize

IndexNow Protocol

What It Is

IndexNow is an open protocol that allows websites to notify search engines instantly when content is created, updated, or deleted. Supported by Bing, Yandex, Seznam, and Naver. Google does NOT support IndexNow but monitors the protocol.

Why It Matters for GEO

ChatGPT uses Bing's index. Bing Copilot uses Bing's index. Faster Bing indexing means faster AI visibility on two major platforms.

Implementation Check
  1. Check for IndexNow key file: https://[domain]/.well-known/indexnow-key.txt or similar
  2. Check if CMS has IndexNow plugin (WordPress: IndexNow plugin; many modern CMS platforms support it natively)
  3. If not implemented, recommend adding it with instructions

Overall Scoring

CategoryMax PointsWeight
Crawlability15Core foundation
Indexability12Core foundation
Security10Trust signal
URL Structure8Crawl efficiency
Mobile Optimization10Google requirement
Core Web Vitals15Ranking signal
Server-Side Rendering15GEO critical
Page Speed & Server15Performance
Total100

Non-scoring checks (Category 9) appear in the output under "Agent-Readiness Signals" and do not affect this total.

Score Interpretation
  • 90-100: Excellent — technically sound for both traditional SEO and GEO
  • 70-89: Good — minor issues to address but fundamentally solid
  • 50-69: Needs Work — significant technical debt impacting visibility
  • 30-49: Poor — major issues blocking crawling, indexing, or AI visibility
  • 0-29: Critical — fundamental technical failures requiring immediate attention

Output Format

Generate GEO-TECHNICAL-AUDIT.md with:

markdown
# GEO Technical SEO Audit — [Domain]
Date: [Date]

## Technical Score: XX/100

## Score Breakdown
| Category | Score | Status |
|---|---|---|
| Crawlability | XX/15 | Pass/Warn/Fail |
| Indexability | XX/12 | Pass/Warn/Fail |
| Security | XX/10 | Pass/Warn/Fail |
| URL Structure | XX/8 | Pass/Warn/Fail |
| Mobile Optimization | XX/10 | Pass/Warn/Fail |
| Core Web Vitals | XX/15 | Pass/Warn/Fail |
| Server-Side Rendering | XX/15 | Pass/Warn/Fail |
| Page Speed & Server | XX/15 | Pass/Warn/Fail |

Status: Pass = 80%+ of category points, Warn = 50-79%, Fail = <50%

## AI Crawler Access
| Crawler | User-Agent | Status | Recommendation |
|---|---|---|---|
| GPTBot | GPTBot | Allowed/Blocked | [Action] |
| Googlebot | Googlebot | Allowed/Blocked | [Action] |
[Continue for all AI crawlers]

## Critical Issues (fix immediately)
[List with specific page URLs and what is wrong]

## Warnings (fix this month)
[List with details]

## Recommendations (optimize this quarter)
[List with details]

## Agent-Readiness Signals (non-scoring)

### RFC 8288 Link Headers (Service Discovery)

**Status:** Present / Absent / Not Applicable

<!-- If present: -->
| Relation Type | URL | Meaning |
|---|---|---|
| api-catalog | /.well-known/api-catalog | Machine-readable index of available APIs |
| mcp-server-card | /.well-known/mcp.json | MCP server capability declaration |

AI agents and API clients can discover your services without parsing HTML.

<!-- If absent, API-first site only: -->
**Informational Recommendation:** This site has API/developer-oriented content but no `Link:` headers advertising discoverable services.

Example: `Link: </.well-known/api-catalog>; rel="api-catalog"`

Relevant for: sites with public APIs, OpenAPI docs, or MCP server integrations.
Reference: RFC 8288, RFC 9609.

<!-- If absent, standard business site: omit this section entirely -->

### Markdown Content Negotiation

**Status:** Supported / Not Supported
**Test:** GET [url] with `Accept: text/markdown`
**Response Content-Type:** [value]

<!-- If supported: -->
This site serves clean Markdown to AI agents on request. AI crawlers that support content negotiation receive formatted text without HTML boilerplate.

<!-- If not supported: -->
**Forward-Looking Recommendation:** Cloudflare Workers/Pages sites can enable Markdown content negotiation with a one-line configuration change. When an AI agent sends `Accept: text/markdown`, the server responds with clean Markdown instead of HTML.

- Currently Cloudflare-specific
- Relevant for: sites already on Cloudflare infrastructure
- Other CDNs and frameworks expected to adopt this pattern as AI agent traffic grows

## Detailed Findings
[Per-category breakdown with evidence]

© zubair-trabzada, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/geo-technical of zubair-trabzada/geo-seo-claude.

Open the folder on GitHubat commit 989cae0

Used in 2 other repositories

We found 6 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 2 other GitHub owners. This page covers the copy in zubair-trabzada/geo-seo-claude, which our catalogue first saw on October 7, 2026.

Compare with similar skills

GEO Technical SEO Audit next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

GEO Technical SEO Audit compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
GEO Technical SEO Audit this skillzubair-trabzada/geo-seo-claude11k2 repos~5.7kAutomated safety check: NotesMIT
SEOBhanunamikaze/Agentic-SEO-Skill960—~4.9kAutomated safety check: NotesMIT
SEOAgriciDaniel/seo-os1372 repos~3.5kAutomated safety check: PassMIT
SEO and GEO Auditdageno-agents/seo-geo-audit176—~2kAutomated safety check: PassMIT
Universal SEO AnalysisAgriciDaniel/claude-seo19k—~4.9kAutomated safety check: PassMIT
SEO AuditAgriciDaniel/codex-seo7992 repos~1.9kAutomated safety check: PassMIT

Similar skills

  • SEO

    Bhanunamikaze/Agentic-SEO-Skill

    Deterministic LLM-first SEO audits for websites, blog posts, and GitHub repositories.

    960 GitHub stars~4.9k tokensUpdated 2 mo ago
    Marketing & SEOAuto-check: notes

  • SEO

    AgriciDaniel/seo-os

    Comprehensive SEO analysis for any website or business type.

    137 GitHub starsUsed in 2 repos~3.5k tokens
    Marketing & SEOAuto-check passed

  • SEO and GEO Audit

    dageno-agents/seo-geo-audit

    Runs one prioritized audit that combines technical SEO, content quality, trust signals, entity clarity and AI search readiness for a page, site or domain.

    176 GitHub stars~2k tokensUpdated 1 mo ago
    Marketing & SEOAuto-check passed

  • Universal SEO Analysis

    AgriciDaniel/claude-seo

    Hub for site-wide SEO work: audits, technical checks, schema, content quality, local, hreflang and AI-search readiness, run through slash commands.

    19k GitHub stars~4.9k tokensUpdated 6 days ago
    Marketing & SEOAuto-check passed

  • SEO Audit

    AgriciDaniel/codex-seo

    Full website SEO audit with parallel subagent delegation. An agent skill from AgriciDaniel/codex-seo.

    799 GitHub starsUsed in 2 repos~1.9k tokens
    Marketing & SEOAuto-check passed

  • SEO

    AgriciDaniel/codex-seo

    Comprehensive SEO analysis for any website, page, business, or topic.

    799 GitHub stars~3.7k tokensUpdated 29 days ago
    Marketing & SEOAuto-check passed

More from zubair-trabzada/geo-seo-claude

All 16 skills in this repo

  • GEO-First SEO Audit Tool

    zubair-trabzada/geo-seo-claude

    Audits a website for AI search visibility across ChatGPT, Claude, Perplexity and Google AI Overviews while checking traditional SEO, schema and E-E-A-T content quality.

    11k GitHub stars~2.8k tokensUpdated yesterday
    Auto-check: notes

  • GEO Monthly Delta Report

    zubair-trabzada/geo-seo-claude

    Compares a baseline and a current GEO audit for a client, calculates score changes and action item progress, and writes a monthly progress report.

    11k GitHub stars~2.4k tokensUpdated yesterday
    Auto-check: notes

  • AI Citability Scorer

    zubair-trabzada/geo-seo-claude

    Scores how likely AI assistants are to quote passages from a web page and suggests rewrites that make those passages easier to extract.

    11k GitHub starsUsed in 2 repos~3.7k tokens
    Auto-check: notes

  • GEO Service Proposal Generator

    zubair-trabzada/geo-seo-claude

    Builds a client-ready AI-search-optimization proposal from an existing GEO audit, with pricing tiers, an ROI estimate and a markdown document ready to send.

    11k GitHub stars~3k tokensUpdated yesterday
    Auto-check: notes

  • GEO Content E-E-A-T Scorer

    zubair-trabzada/geo-seo-claude

    Scores a page's content against Google's E-E-A-T framework and AI-citability structure, then writes a scored gap-analysis report.

    11k GitHub starsUsed in 2 repos~4k tokens
    Auto-check: notes

  • GEO Prospect Tracker

    zubair-trabzada/geo-seo-claude

    Tracks GEO agency leads and clients through a sales pipeline in a local JSON file, with notes, audit scores, deal values and a pipeline summary.

    11k GitHub stars~1.7k tokensUpdated yesterday
    Auto-check: notes

Categories

Questions about GEO Technical SEO Audit

What does GEO Technical SEO Audit do?

Audits a site's technical SEO across eight categories with a focus on AI crawler access and server-side rendering, scoring each and writing a report file. The audit fetches a homepage plus two or three inner pages by URL, HTML and headers, then scores eight technical categories, with crawlability worth 15 points in the excerpt shown.txt validity, the presence of a sitemap directive, and specifically AI crawler access: whether directives block GPTBot, Google-Extended, Googlebot, Bingbot, PerplexityBot, ClaudeBot, Amazonbot, CCBot, FacebookExternalHit, Bytespider or Applebot-Extended.

When should I use GEO Technical SEO Audit?

GEO Technical SEO Audit fits situations like: checking whether a site's robots.txt blocks AI crawlers like GPTBot or PerplexityBot; auditing a site's crawlability and indexability for AI search visibility; verifying server-side rendering before an AI search optimization push.

How do I install GEO Technical SEO Audit in Claude Code?

Run `npx skills add zubair-trabzada/geo-seo-claude --skill geo-technical -a claude-code`. Or copy the skill folder (skills/geo-technical in zubair-trabzada/geo-seo-claude) into .claude/skills/geo-technical in your project. Claude Code loads it when a task matches its description.

How do I install GEO Technical SEO Audit in Codex?

Run `npx skills add zubair-trabzada/geo-seo-claude --skill geo-technical -a codex`. Or copy the skill folder (skills/geo-technical in zubair-trabzada/geo-seo-claude) into .agents/skills/geo-technical in your project. Codex loads it when a task matches its description.

Can I use GEO Technical SEO Audit in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add zubair-trabzada/geo-seo-claude --skill geo-technical -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/geo-technical, .gemini/skills/geo-technical, .github/skills/geo-technical and .opencode/skills/geo-technical in your project.

What does GEO Technical SEO Audit need to run?

Going by SKILL.md and its folder, GEO Technical SEO Audit needs the command-line tools its instructions call (curl). Our summary lists: Network access to fetch the target site's pages, robots.txt and headers. Its frontmatter pre-approves these tools: Read, Grep, Glob, Bash, WebFetch, Write.

Does GEO Technical SEO Audit access the network?

SKILL.md contains no URLs. Its commands use curl, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is GEO Technical SEO Audit safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does GEO Technical SEO Audit use?

GEO Technical SEO Audit is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does GEO Technical SEO Audit use?

About 5.7k tokens (SKILL.md is roughly 23k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to GEO Technical SEO Audit?

Skills that share tags, products or a category with GEO Technical SEO Audit: SEO (Bhanunamikaze/Agentic-SEO-Skill, 960 stars), SEO (AgriciDaniel/seo-os, 137 stars), SEO and GEO Audit (dageno-agents/seo-geo-audit, 176 stars) and Universal SEO Analysis (AgriciDaniel/claude-seo, 19k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains GEO Technical SEO Audit?

zubair-trabzada (a GitHub user) maintains it in zubair-trabzada/geo-seo-claude, which has 10,982 GitHub stars. The repository holds 16 skills in this directory. The repository was last updated on October 10, 2026.

Source: zubair-trabzada/geo-seo-claude on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.