/ 디렉터리 / 플레이그라운드 / seo-audit-skill
● 커뮤니티 seo-skills ⚡ 바로 사용

seo-audit-skill

제작: seo-skills · seo-skills/seo-audit-skill

108 SEO audit rules across 12 categories — Core Web Vitals, security headers, structured data, accessibility — run from Claude Code.

SEO Audit Skill wraps a CLI that crawls any URL and evaluates 108 rules across 12 categories: on-page SEO, Core Web Vitals, security headers, structured data, accessibility, crawlability, mobile, i18n, and more. Claude Code invokes it, interprets the report, and drafts actionable fixes grouped by impact.

왜 쓰나요

핵심 기능

라이브 데모

실제 사용 모습

seo-audit-skill.replay ▶ 준비됨
0/0

설치

클라이언트 선택

~/Library/Application Support/Claude/claude_desktop_config.json  · Windows: %APPDATA%\Claude\claude_desktop_config.json
{
  "mcpServers": {
    "seo-audit-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/seo-skills/seo-audit-skill",
        "~/.claude/skills/seo-audit-skill"
      ],
      "_inferred": true
    }
  }
}

Claude Desktop → Settings → Developer → Edit Config 열기. 저장 후 앱 재시작.

~/.cursor/mcp.json · .cursor/mcp.json
{
  "mcpServers": {
    "seo-audit-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/seo-skills/seo-audit-skill",
        "~/.claude/skills/seo-audit-skill"
      ],
      "_inferred": true
    }
  }
}

Cursor는 Claude Desktop과 동일한 mcpServers 스키마 사용. 프로젝트 설정이 전역보다 우선.

VS Code → Cline → MCP Servers → Edit
{
  "mcpServers": {
    "seo-audit-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/seo-skills/seo-audit-skill",
        "~/.claude/skills/seo-audit-skill"
      ],
      "_inferred": true
    }
  }
}

Cline 사이드바의 MCP Servers 아이콘 클릭 후 "Edit Configuration" 선택.

~/.codeium/windsurf/mcp_config.json
{
  "mcpServers": {
    "seo-audit-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/seo-skills/seo-audit-skill",
        "~/.claude/skills/seo-audit-skill"
      ],
      "_inferred": true
    }
  }
}

Claude Desktop과 같은 형식. Windsurf 재시작 후 적용.

~/.continue/config.json
{
  "mcpServers": [
    {
      "name": "seo-audit-skill",
      "command": "git",
      "args": [
        "clone",
        "https://github.com/seo-skills/seo-audit-skill",
        "~/.claude/skills/seo-audit-skill"
      ]
    }
  ]
}

Continue는 맵이 아닌 서버 오브젝트 배열 사용.

~/.config/zed/settings.json
{
  "context_servers": {
    "seo-audit-skill": {
      "command": {
        "path": "git",
        "args": [
          "clone",
          "https://github.com/seo-skills/seo-audit-skill",
          "~/.claude/skills/seo-audit-skill"
        ]
      }
    }
  }
}

context_servers에 추가. 저장 시 Zed가 핫 리로드.

claude mcp add seo-audit-skill -- git clone https://github.com/seo-skills/seo-audit-skill ~/.claude/skills/seo-audit-skill

한 줄 명령. claude mcp list로 확인, claude mcp remove로 제거.

사용 사례

실전 활용법: seo-audit-skill

How to run your first full SEO audit and prioritize fixes

👤 Site owners and SEO practitioners who inherit a site with unknown SEO health ⏱ ~30 min beginner

언제 쓸까: New project, new site, or pre-launch checklist.

사전 조건
  • Skill installed — git clone https://github.com/seo-skills/seo-audit-skill ~/.claude/skills/seo-audit-skill
  • Node 18+ — nvm install 18
흐름
  1. Run full audit
    Run seo-audit-skill on https://example.com — all 108 rules, output markdown.✓ 복사됨
    → Report with per-rule pass/fail and a category summary
  2. Prioritize by impact
    Group the failures into 'ship this week' (high impact, low effort) vs 'backlog'. Explain the cutoff.✓ 복사됨
    → Ranked fix list with rationale
  3. Generate fix PRs
    For the top 5 'ship this week' items, draft the code changes in a PR-ready diff.✓ 복사됨
    → Diffs for meta tags, headers, and structured data

결과: A sprint-sized SEO fix list with drafted diffs.

함정
  • Lighthouse scores vary run-to-run — Run 3 times, take median; skill supports --runs=3
  • Rules flag false positives on JS-heavy SPAs — Use --render=js to enable JS rendering; costs more time
함께 쓰기: trae-skill

Run just the Core Web Vitals checks in CI

👤 Performance engineers wiring SEO to CI ⏱ ~20 min intermediate

언제 쓸까: You want a CI gate that blocks regressions in LCP/CLS/INP.

흐름
  1. Scope to CWV category
    Run seo-audit-skill --category=cwv on our staging URL.✓ 복사됨
    → Just the CWV rules with values
  2. Wrap in CI
    Generate a GitHub Actions step that runs this and fails if LCP > 2.5s.✓ 복사됨
    → YAML snippet with threshold logic

결과: A CI gate that catches perf regressions before prod.

함정
  • CI runner is slower than users — Use field data via CrUX where possible; treat lab data as a regression detector, not absolute target

Validate and fix structured data (JSON-LD)

👤 Developers wanting rich results in SERPs ⏱ ~25 min intermediate

언제 쓸까: Your pages aren't getting rich snippets despite having JSON-LD.

흐름
  1. Scope to structured-data rules
    Run seo-audit-skill --category=structured-data on these 5 URLs.✓ 복사됨
    → Per-URL list of schema errors and missing required fields
  2. Generate corrected JSON-LD
    For each error, produce the corrected JSON-LD snippet keyed to the page type.✓ 복사됨
    → Per-page snippets ready to paste

결과: Schema.org-valid JSON-LD deployed; ready to re-check via Google Rich Results Test.

함정
  • Schema valid but Google still doesn't show rich results — Validity is necessary, not sufficient. Check eligibility guidelines for the specific rich result type.

Audit and set security headers

👤 Developers wanting baseline security + SEO signal ⏱ ~45 min intermediate

언제 쓸까: securityheaders.com gave you an F and you want to understand why.

흐름
  1. Run security category
    Run seo-audit-skill --category=security on https://example.com.✓ 복사됨
    → CSP, HSTS, X-Frame-Options, Referrer-Policy status
  2. Generate headers config
    Produce the nginx and Cloudflare Worker configs to set the missing headers safely (report-only CSP first).✓ 복사됨
    → Copy-paste configs with report-only CSP

결과: A secure header config rolled out behind report-only mode.

함정
  • Enforcing CSP breaks the site — Always start with Content-Security-Policy-Report-Only; watch reports for 1-2 weeks before enforcing

조합

다른 MCP와 조합해 10배 효율

seo-audit-skill + trae-skill

TRAE scaffolds SEO basics, seo-audit verifies them

Scaffold SEO with TRAE, run seo-audit to verify, fix gaps.✓ 복사됨
seo-audit-skill + claude-code-owasp-skill

Security-header subset of SEO overlaps with OWASP checks

Run seo-audit security category, then OWASP skill for deeper security review.✓ 복사됨

도구

이 MCP가 노출하는 것

도구입력언제 호출비용
full_audit url: str, runs?: int, render?: 'js'|'static' First audit on a site 0
category_audit url, category: 'cwv'|'security'|'structured-data'|... Focused checks or CI 0
diff_fix_generator report, top_n? After audit, to turn findings into PRs Claude tokens

비용 및 제한

운영 비용

API 쿼터
None. Runs locally via headless Chromium.
호출당 토큰
Report interpretation uses 5-15k Claude tokens depending on site size
금액
Free
Use --category= to avoid running all 108 rules when you only need a subset.

보안

권한, 시크릿, 파급범위

자격 증명 저장: No credentials
데이터 외부 송신: Fetches the target URL and its assets. Does not send report to any third party.

문제 해결

자주 발생하는 오류와 해결

Puppeteer fails to launch

Install Chrome dependencies: apt-get install libgbm1 libnss3 (Linux) or run npx puppeteer browsers install chrome

확인: node -e 'require("puppeteer").launch().then(b=>b.close())'
Rules flag modern JS framework features as problems

Use --render=js so the audit runs post-hydration

All CWV rules report N/A

Lighthouse lab mode; on slow connections it times out. Increase --timeout.

대안

seo-audit-skill 다른 것과 비교

대안언제 쓰나단점/장점
Google Lighthouse CLIYou only need the canonical CWV/perf subsetNo structured-data or SEO-specific rules
Screaming FrogYou need enterprise-grade crawling of large sitesPaid, desktop app, not LLM-integrated

더 보기

리소스

📖 GitHub에서 공식 README 읽기

🐙 열린 이슈 보기

🔍 400+ MCP 서버 및 Skills 전체 보기