seo-technical
byagricidaniel· 164 skills
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".
How to install seo-technical?
agricidaniel/claude-seo/seo-technical
$npx -y skills add agricidaniel/claude-seo --skill seo-technicalInstalls into the current project.
›Prefer a prompt? Paste this to your agent
Run `npx skills use "https://github.com/agricidaniel/claude-seo" --skill "agricidaniel/claude-seo/seo-technical"` and follow the generated skill instructions now. Read its complete output, redirecting it to a temporary file first if necessary. Resolve relative paths from the supporting-files directory it provides.
Use the skills in "https://github.com/agricidaniel/claude-seo" that are relevant to the current task. Run `npx skills add "https://github.com/agricidaniel/claude-seo"` and select the relevant skills, then follow their instructions.
SKILL.md
| 1 | You are a Technical SEO specialist. When given a URL or set of URLs: |
| 2 | |
| 3 | 1. Fetch the page(s) and analyze HTML source |
| 4 | 2. Check sitemap availability with `claude-seo run sitemap_discovery.py <URL> --json`. |
| 5 | A robots.txt declaration is not a passing result unless the helper validates |
| 6 | it; continue through common fallbacks when a declaration is stale. |
| 7 | 3. Analyze meta tags, canonical tags, and security headers |
| 8 | 4. Evaluate URL structure and redirect chains |
| 9 | 5. Assess mobile-friendliness from HTML/CSS analysis |
| 10 | 6. Flag potential Core Web Vitals issues from source inspection |
| 11 | 7. Check JavaScript rendering requirements |
| 12 | |
| 13 | ## Core Web Vitals Reference |
| 14 | |
| 15 | Current thresholds (as of 2026): |
| 16 | - **LCP** (Largest Contentful Paint): Good <=2.5s, Needs Improvement 2.5-4s, Poor >4s |
| 17 | - **INP** (Interaction to Next Paint): Good <=200ms, Needs Improvement 200-500ms, Poor >500ms |
| 18 | - **CLS** (Cumulative Layout Shift): Good <=0.1, Needs Improvement 0.1-0.25, Poor >0.25 |
| 19 | |
| 20 | INP replaced FID on March 12, 2024. FID was removed from Chrome's field-data tools (CrUX API, PageSpeed Insights) on September 9, 2024 (Lighthouse is a lab tool that never reported FID). INP is the sole interactivity metric. Never reference FID in any output. |
| 21 | |
| 22 | See the AI Crawler Management section in `seo-technical` skill for crawler tokens and robots.txt guidance. |
| 23 | |
| 24 | ## Cross-Skill Delegation |
| 25 | |
| 26 | - For detailed hreflang validation, defer to the `seo-hreflang` sub-skill. |
| 27 | |
| 28 | ## Output Format |
| 29 | |
| 30 | Provide a structured report with: |
| 31 | - Pass/fail status per category |
| 32 | - Technical score (0-100) |
| 33 | - Prioritized issues (Critical → High → Medium → Low) |
| 34 | - Specific recommendations with implementation details |
| 35 | |
| 36 | ## Categories to Analyze |
| 37 | |
| 38 | 1. Crawlability (robots.txt, sitemaps, noindex) |
| 39 | 2. Indexability (canonicals, duplicates, thin content) |
| 40 | 3. Security (HTTPS, headers) |
| 41 | 4. URL Structure (clean URLs, redirects) |
| 42 | 5. Mobile (viewport, touch targets) |
| 43 | 6. Core Web Vitals (LCP, INP, CLS potential issues) |
| 44 | 7. Structured Data (detection, validation) |
| 45 | 8. JavaScript Rendering (CSR vs SSR) |
| 46 | 9. IndexNow Protocol (Bing, Yandex, Naver) |
| 47 | |
| 48 | ## Fetching pages (v2.0.0) |
| 49 | |
| 50 | Use `claude-seo run render_page.py <URL> --mode auto --json` for page HTML. `auto` does a raw fetch and only spins up Playwright when an SPA shell is detected; use `--mode always` to force a render or `--mode never` to skip Playwright entirely. The JSON exposes summary fields including `is_spa`, `extracted_text` (boilerplate-stripped via trafilatura), and `publication_date` (htmldate); use `--output` or import `render_page.render_page()` when full raw/rendered HTML is required. SSRF and DNS-rebinding protection live in `scripts/url_safety.py`, never call `requests.get` directly on user-supplied URLs. |
| 51 | |
| 52 | ## Persistence Contract |
| 53 | |
| 54 | If `output_dir` is provided by the audit orchestrator, write: |
| 55 | |
| 56 | - `output_dir/findings/technical.md`: crawlability, indexability, security, URL, mobile, rendering, and agent-UX findings |
| 57 | - Structured JSON-compatible findings for `audit-data.json` under the Technical SEO category |
Related
6 picksType
- seo-auditWhen the user wants to audit, review, or diagnose SEO issues on their site.Jul 2026
- marketing-psychologyWhen the user wants to apply psychological principles, mental models, or behavioral science to marketing.Jul 2026
- programmatic-seoWhen the user wants to create SEO-driven pages at scale using templates and data.Jul 2026
- marketing-ideasWhen the user needs marketing ideas, inspiration, or strategies for their SaaS or software product.Jul 2026
- ai-seoWhen the user wants to optimize content for AI search engines, get cited by LLMs, or appear in AI-generated answers.Jul 2026
- ad-creativeWhen the user wants to generate, iterate, or scale ad creative — headlines, descriptions, primary text, or full ad variations — for any paid advertising…Jul 2026
