technical-seo — Claude Code skill: audits and installation
This skill guides technical SEO checks for crawl and index problems, performance regressions, and structured data gaps. Use it when reviewing a site migration or investigating SEO issues.
Apache-2.0 ★ 450 updated 2026-04-03
npx skills add gtmagents/gtm-agents --skill technical-seo -a claude-codeWhat technical-seo does
The skill organizes an audit around crawl health, performance, indexation signals, structured data, and security and accessibility. It suggests comparing Screaming Frog or JetOctopus results with Search Console coverage and sampled log files. For performance, it calls for checking Lighthouse field data against lab results.
Migration guidance covers checks before and after launch, redirect mapping, and monitoring. Separate playbooks address Core Web Vitals and international SEO. Templates include an issue tracker, a structured data coverage sheet, and KPI guardrails. Pairing log analysis with Search Console stats helps verify how crawlers behave on the live site.
An escalation workflow moves from detection and ownership to fixes, validation, and a short status report. The KPI guidance includes thresholds such as a limit of two positions of decline for priority keyword rankings. Rollback conditions include three guardrail breaches in 24h or crawl errors rising by more than 25% against baseline.
What it helps with
- trace a site's indexing decline
- compare crawl errors with Search Console data
- prioritize Core Web Vitals fixes
- prepare redirect maps for a CMS migration
- audit structured data coverage
Example prompts for the agent
- Audit this site for crawl, indexation, and structured data issues.
- Create a prioritized Core Web Vitals improvement plan.
- Draft a migration checklist with redirect mapping and monitoring steps.
How to install technical-seo
1Skills CLI (Vercel)
npx skills add gtmagents/gtm-agents --skill technical-seo -a claude-code2Manually: put the files in place
~/.claude/skills/technical-seo/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/technical-seo/
1Skills CLI (Vercel)
npx skills add gtmagents/gtm-agents --skill technical-seo -a codex2Manually: put the files in place
.agents/skills/technical-seo/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add gtmagents/gtm-agents --skill technical-seo -a cursor2Manually: put the files in place
.cursor/skills/technical-seo/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install gtmagents/gtm-agents plugins/seo/skills/technical-seo2Manually: put the files in place
.github/skills/technical-seo/SKILL.md1Skills CLI (Vercel)
npx skills add gtmagents/gtm-agents --skill technical-seo -a gemini-cli2Platform CLI
gemini skills install https://github.com/gtmagents/gtm-agents --path plugins/seo/skills/technical-seoManually: put the files in place
.devin/skills/technical-seo/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about technical-seo
How do I install technical-seo in Claude Code?
Run npx skills add gtmagents/gtm-agents --skill technical-seo -a claude-code. The skill file is at ~/.claude/skills/technical-seo/SKILL.md.
What does technical-seo do?
It guides checks for crawling, indexation, performance, SEO signals, and structured data. Its playbooks also cover migrations, Core Web Vitals, and international SEO.
What does the technical audit cover?
It covers crawl health, performance, indexation signals, structured data, security, and accessibility. For crawl diagnosis, it recommends comparing log analysis with Search Console statistics.
Source text
SKILL.md · Apache-2.0
--- name: technical-seo description: Use when diagnosing crawl/index issues, performance regressions, or structured data gaps. --- # Technical SEO Playbooks ## When to Use - Sites experiencing ranking drops despite strong content. - Launching major site changes (CMS migrations, redesigns). - Investigating Core Web Vitals, crawl budget, or indexing issues. ## Framework 1. **Crawl Health** – Screaming Frog/JetOctopus results, search console coverage, log file sampling. 2. **Performance** – Lighthouse field vs lab data, render-blocking assets, code splitting, image optimization. 3. **Indexation & Signals** – robots.txt, canonicals, hreflang, pagination, parameter handling. 4. **Structured Data** – schema coverage, errors, merchant/product feeds. 5. **Security & Compliance** – HTTPS, mixed content, cookie banners, accessibility. ## Playbooks - **Migrations** – pre/post launch checklist, redirect maps, monitoring dashboards. - **CWV Improvements** – prioritized backlog (LCP, INP, CLS fixes) with eng dependencies. - **International SEO** – hreflang matrix, localized sitemaps, translation QA. - **GTM Agents Audit Checklist** – five-pass review (crawl → index → performance → schema → reporting) @puerto/README.md#183-212. - **Issue Escalation Flow** – Marketing Director ↔ DevOps ↔ Content to fast-track blocking defects. ## Templates - Crawl issue tracker (URL, issue, severity, owner, status). - Core Web Vitals monitoring dashboard. - Structured data coverage sheet. - KPI guardrail sheet (sessions, rankings, conversions) with "alert" thresholds matching GTM Agents governance cadence. ## Tips - Pair log-file analysis with Search Console stats to confirm real-world crawl behavior. - Automate regression alerts via Lighthouse CI or SpeedCurve. - Document every infra change with timestamp to correlate with ranking volatility. - Share Guardrail snapshots weekly using GTM Agents-style status packet (target vs actual vs guardrail) to keep Sales + Execs aligned. - Trigger rollback when three guardrail breaches occur in 24h or when crawl errors spike >25% vs baseline. ## GTM Agents SEO Escalation Workflow 1. **Detection** – SEO specialist flags issue via crawl report or KPI guardrail breach. 2. **Triage** – assign severity (P0-P2) + owner across Engineering, Content, or RevOps. 3. **Action** – implement fix, document via Serena patch or CMS change log. 4. **Validation** – rerun crawl/perf audits, update structured data validator. 5. **Comms** – send 3-point summary (issue, fix, KPI impact) in status packet. ## KPI Guardrails - Organic sessions: ±10% vs trailing 4-week baseline (alert beyond 15%). - Priority keyword avg rank: no more than 2 position drop for Tier-1 terms. - Conversion contribution: must stay within 5% of forecasted pipeline; otherwise notify Growth + Sales. ---
© gtmagents · Apache-2.0 · gtmagents/gtm-agents