Agent skill · Security

seo-technical

Run a comprehensive technical SEO audit covering crawlability, indexability, rendering, site architecture, structured data, page experience, security, and internationalization. Use this skill whenever the user asks about technical SEO, crawl issues, indexing problems, sitemaps, robots.txt, canonical tags, schema markup, page speed, Core Web Vitals, hreflang, redirects, or site-wide search performance. Triggers on technical SEO, site audit, crawlability, indexability, sitemap, robots.txt, canonical, redirect chain, schema, JSON-LD, Core Web Vitals, page speed, hreflang, mobile usability, HTTPS,

RampStack477★ · 1 repos on radarProfile →
claude-codeMIT
Install
npx skills add rampstackco/claude-skills --skill seo-technical --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 3
SKILL.md size: 7 KB
Bundled scripts: none
Path: skills/seo-technical/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 515
Language: Python
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Technical SEO Audit and fix the layer beneath the content: how search engines crawl, render, index, and trust a site. Stack-agnostic. --- ## When to use - Site-wide audit before or after a migration - Investigating indexing or ranking drops - Setting up SEO foundations on a new site - Auditing Core Web Vitals or page experience signals - Fixing crawl waste, redirect chains, or canonical issues - Setting up multilingual or multi-regional sites ## When NOT to use - Single-page on-page optimization (use `seo-onpage`) - Keyword strategy or content planning (use `seo-keyword`) - Competitor backlink or SERP analysis (use `seo-competitor`) - Pure performance optimization without SEO context (use `performance-optimization`) --- ## Required inputs - The site URL or staging URL - Access to (at minimum) view the rendered HTML, robots.txt, and sitemap - Ideally: search console access, server logs, and a crawler If the site is large (10K+ URLs), confirm whether the audit is a full crawl or a sample. --- ## The framework: 6 layers Technical SEO has six layers, stacked. A failure in a lower layer breaks everything above it. ### 1. Crawlability Can search engines access the URLs? - robots.txt do

What's inside
Steps it walks through
  1. When to use
  2. When NOT to use
  3. Required inputs
  4. The framework: 6 layers
  5. 1. Crawlability
  6. 2. Indexability
  7. 3. Rendering
  8. 4. Site architecture
  9. 5. Structured data and signals
  10. 6. Page experience and security
  11. Workflow
  12. Failure patterns
  13. Output format
  14. Reference files
Ships with 2 files
  • references/audit-template.md
  • references/migration-checklist.md
More from claude-skills
All skills →
About this skill
What does the seo-technical skill do?

Run a comprehensive technical SEO audit covering crawlability, indexability, rendering, site architecture, structured data, page experience, security, and internationalization. Use this skill whenever the user asks about technical SEO, crawl issues, indexing problems, sitemaps, robots.txt, canonical tags, schema markup, page speed, Core Web Vitals, hreflang, redirects, or site-wide search performance. Triggers on technical SEO, site audit, crawlability, indexability, sitemap, robots.txt, canonical, redirect chain, schema, JSON-LD, Core Web Vitals, page speed, hreflang, mobile usability, HTTPS,

How do I install it?

Run `npx skills add rampstackco/claude-skills --skill seo-technical --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From rampstackco/claude-skills, a repository with 515 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going