affaan-m/ecc

seo

Audit, plan, and implement SEO improvements across technical SEO, on-page optimization, structured data, Core Web Vitals, and content strategy.

소스 보기

사용 방법

  1. 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
  2. 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
  3. 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/affaan-m/ecc --skill seo

시작 전 확인

  • 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
  • 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 Skill 문서

원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.

SEO

Improve search visibility through technical correctness, performance, and content relevance, not gimmicks.

When to Use

Use this skill when:

  • auditing crawlability, indexability, canonicals, or redirects
  • improving title tags, meta descriptions, and heading structure
  • adding or validating structured data
  • improving Core Web Vitals
  • doing keyword research and mapping keywords to URLs
  • planning internal linking or sitemap / robots changes

How It Works

Principles

  1. Fix technical blockers before content optimization.
  2. One page should have one clear primary search intent.
  3. Prefer long-term quality signals over manipulative patterns.
  4. Mobile-first assumptions matter because indexing is mobile-first.
  5. Recommendations should be page-specific and implementable.

Technical SEO checklist

Crawlability

  • robots.txt should allow important pages and block low-value surfaces
  • no important page should be unintentionally noindex
  • important pages should be reachable within a shallow click depth
  • avoid redirect chains longer than two hops
  • canonical tags should be self-consistent and non-looping

Indexability

  • preferred URL format should be consistent
  • multilingual pages need correct hreflang if used
  • sitemaps should reflect the intended public surface
  • no duplicate URLs should compete without canonical control

Performance

  • LCP < 2.5s
  • INP < 200ms
  • CLS < 0.1
  • common fixes: preload hero assets, reduce render-blocking work, reserve layout space, trim heavy JS

Structured data

  • homepage: organization or business schema where appropriate
  • editorial pages: Article / BlogPosting
  • product pages: Product and Offer
  • interior pages: BreadcrumbList
  • Q&A sections: FAQPage only when the content truly matches

On-page rules

Title tags

  • aim for roughly 50-60 characters
  • put the primary keyword or concept near the front
  • make the title legible to humans, not stuffed for bots

Meta descriptions

  • aim for roughly 120-160 characters
  • describe the page honestly
  • include the main topic naturally

Heading structure

  • one clear H1
  • H2 and H3 should reflect actual content hierarchy
  • do not skip structure just for visual styling

Keyword mapping

  1. define the search intent
  2. gather realistic keyword variants
  3. prioritize by intent match, likely value, and competition
  4. map one primary keyword/theme to one URL
  5. detect and avoid cannibalization

Internal linking

  • link from strong pages to pages you want to rank
  • use descriptive anchor text
  • avoid generic anchors when a more specific one is possible
  • backfill links from new pages to relevant existing ones

Examples

Title formula

text
Primary Topic - Specific Modifier | Brand

Meta description formula

text
Action + topic + value proposition + one supporting detail

JSON-LD example

json
{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "Page Title Here",
  "author": {
    "@type": "Person",
    "name": "Author Name"
  },
  "publisher": {
    "@type": "Organization",
    "name": "Brand Name"
  }
}

Audit output shape

text
[HIGH] Duplicate title tags on product pages
Location: src/routes/products/[slug].tsx
Issue: Dynamic titles collapse to the same default string, which weakens relevance and creates duplicate signals.
Fix: Generate a unique title per product using the product name and primary category.

Anti-Patterns

Anti-patternFix
keyword stuffingwrite for users first
thin near-duplicate pagesconsolidate or differentiate them
schema for content that is not actually presentmatch schema to reality
content advice without checking the actual pageread the real page first
generic “improve SEO” outputstie every recommendation to a page or asset

Related Skills

  • seo-specialist
  • frontend-patterns
  • brand-voice
  • market-research

관련 작업

같은 저장소의 Skills

더 많은 Skills

모든 Skills
affaan-m
커뮤니티

agentic-os

Build persistent multi-agent operating systems on Claude Code. Covers kernel architecture, specialist agents, slash commands, file-based memory, scheduled automation, and state management without external databases. Use when building a persistent multi-agent system on Claude Code with its own memory, commands, and scheduling.

설치 수
4
GitHub Stars
28.6만
업데이트
10월 20일
affaan-m
커뮤니티

autonomous-loops

Patterns and architectures for autonomous Claude Code loops — from simple sequential pipelines to RFC-driven multi-agent DAG systems. Retained for compatibility only: when new autonomous loop guidance is needed, use continuous-agent-loop instead.

설치 수
4
GitHub Stars
28.6만
업데이트
10월 20일
affaan-m
커뮤니티

coding-standards

Baseline cross-project coding conventions for naming, readability, immutability, and code-quality review. Use detailed frontend or backend skills for framework-specific patterns. Use when reviewing code quality or naming with no framework-specific skill that applies.

설치 수
4
GitHub Stars
28.6만
업데이트
10월 20일
affaan-m
커뮤니티

configure-ecc

Run the conversational ECC setup wizard inside the current harness: inventory the install, collect scope (user/project/local) and hook mode (off/minimal/standard/strict) in Claude Code, use Codex's native plugin lifecycle, or install the project surface under ./.kimi-code, then preview, apply, and verify. Use when installing, updating, reconfiguring, or repairing an ECC installation, changing hook profiles, or moving ECC between install scopes.

설치 수
4
GitHub Stars
28.6만
업데이트
10월 20일