Skip to main content
skill CX Codex

seo-technical · rampstackco — Claude Code skill: technical SEO audit

seo-technical runs a technical SEO audit covering crawlability, indexability, rendering, site architecture, structured data, Core Web Vitals, security and internationalization.

MIT 347 installs ★ 1,107 updated 2026-10-19

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add rampstackco/claude-skills --skill seo-technical -a claude-code
Open on GitHub

What seo-technical does

The skill checks six technical SEO layers: crawlability (robots.txt, sitemap, blocked resources), indexability (canonical tags, noindex, duplicates), rendering (does the bot see content in SPAs), site structure (internal links, redirect chains, orphan pages), markup (Schema.org, JSON-LD, breadcrumbs) and Page Experience (HTTPS, Core Web Vitals, mobile usability). For each layer the skill scores the state, lists issues with example URLs and prioritizes fixes.

Output is seo-technical-audit.md with scores for the six layers, critical findings that block indexing or drop traffic, and a sequenced roadmap. For migrations the skill can generate a redirect map as CSV. Without Search Console access, server logs or a crawler some checks will be incomplete — the skill notes what data was missing and which parts of the output are affected.

Not for single-page optimization (see seo-onpage) or competitor analysis (seo-competitor).

What it helps with

  • audit crawlability and indexability before a site migration
  • diagnose the root cause of an organic traffic drop
  • set up sitemap, canonical and robots.txt on a new project
  • check Core Web Vitals and mobile usability
  • find redirect chains and orphan pages

Example prompts for the agent

  • Run a technical SEO audit on example.com
  • Check crawlability and indexability for staging.site.dev
  • Find canonical and robots.txt issues on the production site

How to install seo-technical

1Skills CLI (Vercel)

npx skills add rampstackco/claude-skills --skill seo-technical -a claude-code

2Manually: put the files in place

~/.claude/skills/seo-technical/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/seo-technical/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about seo-technical

How to install seo-technical in Claude Code?

Run npx skills add rampstackco/claude-skills --skill seo-technical -a claude-code, the skill will be in ~/.claude/skills/seo-technical/SKILL.md.

What does seo-technical do?

Runs a technical SEO audit across six layers: crawlability, indexability, rendering, site architecture, markup and Page Experience. Finds robots.txt blocks, canonical duplicates, Core Web Vitals issues and mobile usability problems, writes a markdown report.

What does seo-technical need to run?

The skill needs a site or staging URL and access to robots.txt, sitemap and rendered HTML. For a full audit Search Console, server logs and a crawler help. If data is unavailable the skill notes which checks were incomplete.

Source text

SKILL.md · MIT
---
name: seo-technical
description: "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, security headers, render-blocking, JavaScript SEO. Also triggers when a site has indexing problems, traffic drops, or migration concerns, even if 'technical SEO' is not said explicitly."
category: seo-foundation
catalog_summary: "Crawlability, indexability, rendering, schema, page experience"
display_order: 2
---

# 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 does not block important paths
- No accidental `noindex` on indexable pages
- No accidental `disallow` patterns blocking CSS or JS (rendering breaks)
- Sitemap is present, returns 200, and lists canonical URLs only
- Sitemap is referenced in robots.txt
- No infinite spaces (faceted nav generating endless URLs)
- Crawl budget is not wasted on low-value URLs

### 2. Indexability
Of crawlable URLs, which should be indexed?

- One canonical URL per piece of content (no duplicates)
- Canonical tags self-reference on canonical pages
- `noindex` on staging, search results, filter pages, thank-you pages, internal admin
- No mixed signals (canonical pointing one way, sitemap another, internal links a third)
- Pagination handled correctly (rel=next/prev is deprecated, but consistent canonicals matter)
- Parameter handling deliberate (UTM, session IDs, sort orders)

### 3. Rendering
Does the rendered HTML match what crawlers see?

- Critical content visible without JavaScript (or properly server-rendered)
- For SPAs: confirm Googlebot sees the rendered content (test with the URL Inspection tool)
- No cloaking (showing different content to bots vs users)
- Lazy-loaded content has proper loading attributes
- Hydration errors do not strip content from the rendered DOM

### 4. Site architecture
Is the site structured for both users and crawlers?

- Clear URL hierarchy that mirrors site structure
- Important pages reachable in 3 clicks or fewer from the homepage
- Internal linking distributes authority logically
- Breadcrumb navigation present and marked up with schema
- No orphan pages (pages with no internal links)
- No redirect chains (one redirect max)
- No 4xx errors on internally-linked URLs

### 5. Structured data and signals
Does the site speak crawler language?

- Schema.org markup on appropriate page types
- JSON-LD format (preferred over microdata)
- Validates in the Rich Results Test
- Organization or LocalBusiness schema on the homepage or about page
- BreadcrumbList schema on nested pages
- Author and publisher schema linked correctly on content pages
- llms.txt present at the root (for AI crawlers, see `seo-aeo-geo`)

### 6. Page experience and security
Does the site meet the page experience baseline?

- HTTPS on all pages, no mixed content
- HSTS header set
- Core Web Vitals pass (LCP, INP, CLS within thresholds)
- Mobile-friendly (responsive, no horizontal scroll, tap targets sized correctly)
- No intrusive interstitials on mobile
- Stable URL structure (no random URL changes between deploys)
- 404 pages return 404, not 200 with "page not found" content (soft 404)

---

## Workflow

1. **Define scope.** Whole site, a subfolder, a migration check, or a specific issue.
2. **Confirm access.** What can you actually see (HTML, robots, sitemap, search console, server logs, staging)?
3. **Crawl.** Use a crawler to enumerate URLs and statuses. Sample if the site is huge.
4. **Run the 6-layer framework.** Score each, note specific issues with example URLs.
5. **Cross-reference.** Search console for what's actually indexed. Compare to sitemap and crawl output.
6. **Prioritize.** Critical (blocks indexing or causes traffic loss), Important (suboptimal), Nice-to-have (polish).
7. **Write the report.** Use the template in [`references/audit-template.md`](references/audit-template.md).

---

## Failure patterns

- **Optimizing rankings on a page that is `noindex`.** Always check indexability before content work.
- **Adding sitemaps without fixing canonical issues.** A sitemap of duplicate URLs is worse than no sitemap.
- **Blocking crawlers from CSS or JS.** Breaks Google's rendering. Common in over-aggressive robots.txt files.
- **Over-relying on canonical tags.** Canonicals are hints, not directives. Use redirects when content actually moved.
- **Migrating without a redirect map.** Single biggest cause of post-migration traffic loss.
- **Treating Core Web Vitals as the only ranking signal.** Page experience matters but does not override relevance.

---

## Output format

Default output is a markdown audit at `seo-technical-audit.md`. Structure:

1. Scope and methodology
2. Executive summary (3 to 5 critical findings)
3. 6-layer score
4. Critical issues (with example URLs)
5. Important issues
6. Nice-to-have polish
7. Implementation roadmap (sequenced)

For migrations, include a redirect map as a CSV alongside the report.

---

## If required data is unavailable

This skill's output depends on data, measurements, or tool results it cannot generate on its own. When a required input, tool, or data source is unavailable or unverifiable, the sanctioned output is the deliverable with the gap stated: what was needed, what was actually obtained or verified, and which parts of the output are affected. Fabricating, estimating, or interpolating a required number to complete the deliverable is never sanctioned. A stated gap is a complete answer.

---

## Reference files

- [`references/audit-template.md`](references/audit-template.md) - Fillable technical SEO audit template.
- [`references/migration-checklist.md`](references/migration-checklist.md) - Pre and post-migration checklist (covers the highest-risk scenario).

© rampstackco · MIT · rampstackco/claude-skills

Similar skills

All skills for SEO and GEO →

seo-technical by other authors comes first.

seo-technical AgriciDaniel seo-technical audits a site's crawlability, indexing, rendering, and speed-related SEO checks. Use it when crawler access, sitemaps, canonical URLs, or mobile behaviour need investigation. CX Codex +1 8,400installs seo-audit coreyhaines31 A skill for Claude Code, Codex, and Cursor that guides technical SEO audits. Diagnoses traffic drops, indexing issues, canonical tags, and multilingual setups. CX Codex +1 257,200installs seo-technical-optimization Seth Hobson seo-technical-optimization — a Claude Code plugin that handles technical SEO: meta tags, keywords, page structure, and featured snippet markup. Runs when you need to optimize site indexing and search visibility. CX Codex ★ 42,780repo stars Librecrawl — Technical SEO Audit MCP Server adityaarsharma Librecrawl — Technical SEO Audit MCP Server is an MCP server for Claude Code that crawls a site and ranks technical SEO issues by impact. It also returns suggested fixes. CX Codex +1 ★ 49repo stars seo-specialist VoltAgent seo-specialist — a subagent for diagnosing search indexation issues: crawlability, metadata, site structure, Core Web Vitals. Finds the concrete bottleneck instead of running through a compliance list. CX Codex ★ 6,505repo stars technical-seo-stinger Legion Code Inc. technical-seo-stinger is a Claude Code skill that audits technical SEO across 100 pages, checking crawlability, indexability, sitemaps, robots.txt, canonicalization, and crawl-budget use to assess an external site's technical health. CX Codex +1 ★ 96repo stars technical-seo gtmagents 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. CX Codex +1 ★ 450repo stars

From the same set102

The whole set →
brand-discovery brand-discovery is a Claude Code skill that researches audiences, competitors, and category dynamics before a brand or website project. It helps explore positioning options before a creative brief. CX Codex +1 366installs accessibility-audit accessibility-audit audits web interfaces against WCAG 2.1 AA standards and builds a prioritized remediation plan. Helps prepare sites for ADA, Section 508, or routine health checks. CX Codex +1 364installs information-architecture The information-architecture skill plans website or product structure: sitemaps, navigation, URLs, content types, and taxonomies. Use it for new IA work or a restructure. CX Codex +1 354installs creative-brief creative-brief turns a vague idea into a concrete brief that a designer or developer can pick up and run with. Use it to lock down scope, audience, and success metrics before the first line of code. CX Codex +1 354installs seo-onpage seo-onpage runs one page through eight on-page checks: title, meta description, headings, copy, internal links, images, slug and schema. Returns a prioritised report. CX Codex +1 347installs quiz-and-assessment-design quiz-and-assessment-design is a Claude Code skill that plans quizzes and assessments, linking outcomes to recommendations. It supports lead magnets and diagnostics. CX Codex +1 345installs multi-step-form-design multi-step-form-design helps plan multi-step forms with progress, conditional fields, and save-and-resume flows. Use it when scoping a new form or reviewing a long one. CX Codex +1 338installs qa-testing qa-testing is a Claude Code skill for three-tier web page checks using browser console snippets, from post-deploy smoke tests to pre-launch QA. CX Codex +1 335installs

Project sponsors

Companies that keep this analytics open