Seo Technical
Run a structured technical SEO audit on a live or staging URL before launch or during growth refreshes.
Overview
seo-technical is an agent skill most often used in Launch (also Ship, Grow) that runs a nine-category technical SEO audit on a URL.
Install
npx skills add https://github.com/agricidaniel/claude-seo --skill seo-technicalWhat is this skill?
- 9-category technical audit: crawlability, indexability, security, URLs, mobile, Core Web Vitals, structured data, JS ren
- robots.txt, XML sitemap, noindex, crawl depth, and JavaScript rendering checks
- AI crawler management table (GPTBot, ClaudeBot, etc.) via robots.txt tokens
- Security headers and site-speed guidance aligned with ranking signals
- Argument hint accepts a target URL for scoped review
- 9 audit categories
- crawl depth guideline within 3 clicks of homepage
- AI crawler table for major bots
Adoption & trust: 2.1k installs on skills.sh; 8.5k GitHub stars; 1/3 security scanners passed (skills.sh audits).
What problem does it solve?
You are about to launch or grow a site but do not know if crawlers, speed, security headers, or schema will silently cap organic traffic.
Who is it for?
Solo builders auditing their own marketing site, docs, or storefront URL before launch or after a major template change.
Skip if: Pure content strategy or keyword research without a URL to inspect, or teams that only need off-page link building.
When should I use this skill?
User says technical SEO, crawl issues, robots.txt, Core Web Vitals, site speed, or security headers.
What do I get? / Deliverables
You get a categorized technical SEO report with actionable fixes across crawl, index, performance, and structured data so pages can rank and appear in AI search.
- Nine-category technical SEO findings list
- Prioritized fix recommendations per category
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Technical SEO fixes unblock indexing and rich results—the canonical shelf is launch because audits usually gate go-live or relaunch. Covers crawlability, CWV, schema, and security headers—the core technical SEO subfacet under launch.
Where it fits
Audit staging URL for sitemap, noindex, and schema before flipping DNS.
Tie Core Web Vitals and mobile checks to launch readiness after a performance pass.
Re-audit after adding programmatic pages to ensure indexability and JS rendering still work.
Periodic technical sweep when search console shows coverage or security header regressions.
How it compares
Structured nine-category audit checklist—not a generic “write me SEO blog posts” content skill.
Common Questions / FAQ
Who is seo-technical for?
Indie hackers and small teams who ship their own web properties and need agent-guided technical SEO without hiring an agency first.
When should I use seo-technical?
During launch SEO hardening, after a redesign in ship/perf review, or in grow when rankings drop and you suspect crawl, CWV, or schema issues.
Is seo-technical safe to install?
It is MIT-licensed guidance text; review the Security Audits panel on this Prism page before trusting any third-party SEO repo in your agent.
SKILL.md
READMESKILL.md - Seo Technical
MIT License - see repository root LICENSE file for complete terms. Copyright (c) 2026 AgriciDaniel https://github.com/AgriciDaniel/claude-seo --- name: seo-technical description: > Technical SEO audit across 9 categories: crawlability, indexability, security, URL structure, mobile, Core Web Vitals, structured data, JavaScript rendering, and IndexNow protocol. Use when user says "technical SEO", "crawl issues", "robots.txt", "Core Web Vitals", "site speed", or "security headers". user-invokable: true argument-hint: "[url]" license: MIT metadata: author: AgriciDaniel version: "1.9.9" category: seo --- # Technical SEO Audit ## Categories ### 1. Crawlability - robots.txt: exists, valid, not blocking important resources - XML sitemap: exists, referenced in robots.txt, valid format - Noindex tags: intentional vs accidental - Crawl depth: important pages within 3 clicks of homepage - JavaScript rendering: check if critical content requires JS execution - Crawl budget: for large sites (>10k pages), efficiency matters #### AI Crawler Management As of 2025-2026, AI companies actively crawl the web to train models and power AI search. Managing these crawlers via robots.txt is a critical technical SEO consideration. **Known AI crawlers:** | Crawler | Company | robots.txt token | Purpose | |---------|---------|-----------------|---------| | GPTBot | OpenAI | `GPTBot` | Model training | | ChatGPT-User | OpenAI | `ChatGPT-User` | Real-time browsing | | ClaudeBot | Anthropic | `ClaudeBot` | Model training | | PerplexityBot | Perplexity | `PerplexityBot` | Search index + training | | Bytespider | ByteDance | `Bytespider` | Model training | | Google-Extended | Google | `Google-Extended` | Gemini training (NOT search) | | CCBot | Common Crawl | `CCBot` | Open dataset | **Key distinctions:** - Blocking `Google-Extended` prevents Gemini training use but does NOT affect Google Search indexing or AI Overviews (those use `Googlebot`) - Blocking `GPTBot` prevents OpenAI training but does NOT prevent ChatGPT from citing your content via browsing (`ChatGPT-User`) - ~3-5% of websites now use AI-specific robots.txt rules **Example, selective AI crawler blocking:** ``` # Allow search indexing, block AI training crawlers User-agent: GPTBot Disallow: / User-agent: Google-Extended Disallow: / User-agent: Bytespider Disallow: / # Allow all other crawlers (including Googlebot for search) User-agent: * Allow: / ``` **Recommendation:** Consider your AI visibility strategy before blocking. Being cited by AI systems drives brand awareness and referral traffic. Cross-reference the `seo-geo` skill for full AI visibility optimization. ### 2. Indexability - Canonical tags: self-referencing, no conflicts with noindex - Duplicate content: near-duplicates, parameter URLs, www vs non-www - Thin content: pages below minimum word counts per type - Pagination: rel=next/prev or load-more pattern - Hreflang: correct for multi-language/multi-region sites - Index bloat: unnecessary pages consuming crawl budget ### 3. Security - HTTPS: enforced, valid SSL certificate, no mixed content - Security headers: - Content-Security-Policy (CSP) - Strict-Transport-Security (HSTS) - X-Frame-Options - X-Content-Type-Options - Referrer-Policy - HSTS preload: check preload list inclusion for high-security sites ### 4. URL Structure - Clean URLs: descriptive, hyphenated, no query parameters for content - Hierarchy: logical folder structure reflecting site architecture - Redirects: no chains (max 1 hop), 301 for permanent moves - URL length: flag >100 characters - Trailing slashes: consistent usage ### 5. Mobile Optimization - Responsive design: viewport meta tag, responsive CSS - Touch targets: minimum 48x48px with 8px spacing - Font size: minimum 16px base - No horizontal scroll - Mobile-first indexing: Google indexes mobile version. **Mobile-first indexing is 100% complete as of July 5, 2024.** Google now crawls and indexes ALL websites exclusively w