本文へ移動
cccskills
無料GitHub で公開

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, 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.

インストール方法を見る

含まれるファイル(4)

  • SKILL.md7.2 KB
  • README.md354 B
  • references/audit-template.md9.8 KB
  • references/migration-checklist.md4.9 KB

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 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.

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

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Run a comprehensive WCAG accessibility audit covering perceivable, operable, understandable, and robust principles. Use this skill whenever the user wants to audit accessibility, review WCAG compliance, fix accessibility issues, prepare for accessibility certification, address an accessibility lawsuit risk, or systematically improve a site's accessibility. Triggers on accessibility audit, WCAG audit, a11y audit, accessibility compliance, ADA compliance, screen reader test, keyboard navigation, accessibility report, fix accessibility, axe scan. Also triggers when accessibility issues have been reported and need systematic remediation.

日本語の概要は準備中です。原文の説明を表示しています。

rampstackco/claude-skills9462026年10月7日 更新

How to produce ad creative that converts at performance scale. Hook patterns, format selection, video pacing, variation systems, sequential testing methodology, fatigue detection, brand-voice alignment without conversion dilution, and platform-specific creative norms. Triggers on ad creative, ad design, hook patterns, ad video pacing, creative testing, ad variations, creative refresh, creative fatigue, refresh ad creative, video ads for Meta, TikTok creative, LinkedIn ad creative, ad asset library. Also triggers when a team is producing creative at scale, planning a creative test cycle, or auditing why creative is not converting.

日本語の概要は準備中です。原文の説明を表示しています。

rampstackco/claude-skills9462026年10月7日 更新

How to read paid media dashboards without fooling yourself. Attribution models, platform reporting quirks, multi-platform reconciliation, ROAS vs LTV horizon traps, statistical noise in performance metrics, incrementality testing, and the failure modes that produce expensive lessons. Triggers on read paid media dashboard, attribution analysis, ROAS vs LTV, multi-platform reconciliation, ad incrementality, geo holdout, conversion lift study, ghost bidding, paid media reporting, board-deck paid media metrics, blended CAC, MMM, MTA, last-click attribution. Also triggers when a marketer is about to scale, kill, or rebudget a campaign based on platform metrics, or when reconciling platform reports against warehouse revenue.

日本語の概要は準備中です。原文の説明を表示しています。

rampstackco/claude-skills9462026年10月7日 更新

Run a structured after-action review (postmortem, retrospective) on a launch, incident, or completed project to capture timeline, root cause analysis, contributing factors, and actionable lessons. Use this skill whenever the user wants to run a postmortem, retrospective, AAR, or after-action review on any past event. Triggers on after-action report, AAR, postmortem, retrospective, retro, post-incident review, what went well what didn't, lessons learned, blameless postmortem, root cause analysis, RCA, five whys. Also triggers when the user has just shipped something or just resolved an incident and wants to capture learnings.

日本語の概要は準備中です。原文の説明を表示しています。

rampstackco/claude-skills9462026年10月7日 更新

How humans and AI compose in content workflows. Where AI legitimately participates, where humans must own, hybrid workflow patterns, voice ownership preservation, the AI slop problem, disclosure and transparency, team calibration, and the ethics of intellectually honest AI-assisted content production. Triggers on AI content workflow, AI-assisted writing, hybrid content production, AI in editorial, AI slop, AI disclosure, AI usage policy, AI content ethics, voice preservation with AI, team AI calibration. Also triggers when content feels generic despite quality tools, when team AI usage has drifted into inconsistency, or when a regulated or trust-sensitive context requires explicit AI policy.

日本語の概要は準備中です。原文の説明を表示しています。

rampstackco/claude-skills9462026年10月7日 更新

Design measurement frameworks including event taxonomy, KPI hierarchy, dashboard architecture, attribution models, and analytics implementation strategy. Use this skill whenever the user wants to plan analytics, design dashboards, build event taxonomies, define KPIs, set up tracking, or audit existing measurement. Triggers on analytics strategy, measurement plan, event taxonomy, tracking plan, KPI framework, dashboard design, north star metric, attribution model, conversion tracking, GA4 setup, Mixpanel setup, analytics audit. Also triggers when the user has data but no clear way to use it, or wants to make decisions but doesn't know what to track.

日本語の概要は準備中です。原文の説明を表示しています。

rampstackco/claude-skills9462026年10月7日 更新

rampstackco のスキルをすべて見る

このスキルの問題を報告する