affaan-m/ECC

seo

Audit, plan, and implement SEO improvements across technical SEO, on-page optimization, structured data, Core Web Vitals, and content strategy. Use when the user wants better search visibility, SEO remediation, schema markup, sitemap/robots work, or keyword mapping.

83CollectingNetwork access
See how to use itView GitHub source
npx skills add https://github.com/affaan-m/ECC --skill "skills/seo"
Automated source guide

Source checked Jul 28, 2026·Refresh due Oct 26, 2026

Reorganized from the pinned upstream SKILL.md

Turn seo's source instructions into a guide you can follow

According to the pinned SKILL.md from affaan-m/ECC: Improve search visibility through technical correctness, performance, and content relevance, not gimmicks.

npx skills add https://github.com/affaan-m/ECC --skill "skills/seo"
Check the pinned source

Best fit

  • auditing crawlability, indexability, canonicals, or redirects
  • improving title tags, meta descriptions, and heading structure
  • adding or validating structured data

Bring this context

  • A concrete task that matches the documented purpose of seo.
  • The files, examples, or context the task depends on.
  • Your constraints, target environment, and definition of done.

Expected outputs

  • A result that follows the pinned seo instructions.
  • A concise record of assumptions, inputs used, and unresolved questions.
  • A final check against the source workflow and relevant permission signals.

Key source sections

Read seo through these 5 source sections

Sections are extracted automatically from the pinned SKILL.md and link back to the source.

01

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 - planni…

SKILL.md · When to Use
auditing crawlability, indexability, canonicals, or redirectsimproving title tags, meta descriptions, and heading structureadding or validating structured data
02

How It Works

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

SKILL.md · How It Works
Fix technical blockers before content optimization.One page should have one clear primary search intent.Prefer long-term quality signals over manipulative patterns.
03

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

SKILL.md · Principles
Fix technical blockers before content optimization.One page should have one clear primary search intent.Prefer long-term quality signals over manipulative patterns.
04

Technical SEO checklist

robots.txt should allow important pages and block low-value surfaces

SKILL.md · Technical SEO checklist
robots.txt should allow important pages and block low-value surfacesno important page should be unintentionally noindeximportant pages should be reachable within a shallow click depth
05

Crawlability

robots.txt should allow important pages and block low-value surfaces

SKILL.md · Crawlability
robots.txt should allow important pages and block low-value surfacesno important page should be unintentionally noindeximportant pages should be reachable within a shallow click depth

SkillSignal prompt templates

Provide the task, context, and acceptance criteria

These prompts were written by SkillSignal from the source structure; they are not upstream text.

Task-start prompt

Confirm source fit, inputs, and outputs before acting.

Use seo to help me with: [specific task]. Context: [files, data, or background]. Constraints: [environment, scope, and prohibited actions]. Before acting, check the pinned SKILL.md and explain which sections apply, what inputs are still missing, and what you will deliver.

Source-guided execution

Make the Agent explicitly follow the key extracted sections.

Apply the pinned seo source to [task]. Pay particular attention to these source sections: “When to Use”, “How It Works”, “Principles”, “Technical SEO checklist”, “Crawlability”. Preserve the important decision at each step. Mark facts not covered by the source as “needs confirmation” instead of inventing them. Then verify the result against my acceptance criteria: [criteria].

Result-review prompt

Check omissions, permissions, and source drift before delivery.

Review the current seo result: (1) does it satisfy the original task; (2) were any applicable steps or limits in the pinned SKILL.md missed; (3) did it perform any unauthorized file, command, network, or data action; and (4) which conclusions remain unverified? List issues first, then fix only what the source or user authorization supports.

Output checklist

Verify each item before delivery

The task matches the purpose documented in the SKILL.md.

The source section “When to Use” has been checked.

The source section “How It Works” has been checked.

The source section “Principles” has been checked.

The source section “Technical SEO checklist” has been checked.

Inputs, constraints, and acceptance criteria are explicit.

Unverified facts, compatibility, and outcome claims are clearly marked.

Any file, command, network, or data action has been reviewed.

Choose a different workflow

When another Skill is the better fit

seo

テクニカル SEO、オンページ最適化、構造化データ、Core Web Vitals、およびコンテンツ戦略にわたる SEO 改善の監査、計画、実施。ユーザーが検索可視性の向上、SEO 修正、スキーママークアップ、サイトマップ/robots の作業、またはキーワードマッピングを希望する場合に使用します。

A separate implementation from affaan-m/ECC; compare its source, maintenance signals, and permission requirements.

Open source detail

seo

审计、规划并实施SEO改进,涵盖技术SEO、页面优化、结构化数据、核心网页指标和内容策略。当用户希望提升搜索可见性、进行SEO修复、使用架构标记、处理站点地图/robots文件或进行关键词映射时使用。

A separate implementation from affaan-m/ECC; compare its source, maintenance signals, and permission requirements.

Open source detail

site-architecture

When the user wants to plan, map, or restructure their website's page hierarchy, navigation, URL structure, or internal linking. Also use when the user mentions "sitemap," "site map," "visual sitemap," "site structure," "page hierarchy," "information architecture," "IA," "navigation design," "URL structure," "breadcrumbs," "internal linking strategy," "website planning," "what pages do I need," "how should I organize my site," or "site navigation." Use this whenever someone is planning what page

A separate implementation from coreyhaines31/marketingskills; compare its source, maintenance signals, and permission requirements.

Open source detail

FAQ

What does seo do?

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

How do I start using seo?

The catalog detected this source-specific install command: npx skills add https://github.com/affaan-m/ECC --skill "skills/seo". Inspect the command and pinned source before running it.

Which Agent platforms does it declare?

No dedicated Agent platform is declared in the pinned source record.

Repository stars
234,327
Repository forks
35,711
Quality
83/100
Source repository last pushed

Quality breakdown

Based on traceable docs and repository signals; stars are not treated as quality.

83/100
Documentation26/30
Specificity21/25
Maintenance20/20
Trust signals16/25

Compare before choosing

Related Agent Skills and source variants

These links are selected from shared tasks, functions, stacks, platforms, and same-name variants. Compare the source owner, documentation, permissions, and maintenance signals.

seo by affaan-m

テクニカル SEO、オンページ最適化、構造化データ、Core Web Vitals、およびコンテンツ戦略にわたる SEO 改善の監査、計画、実施。ユーザーが検索可視性の向上、SEO 修正、スキーママークアップ、サイトマップ/robots の作業、またはキーワードマッピングを希望する場合に使用します。

seo by affaan-m

审计、规划并实施SEO改进,涵盖技术SEO、页面优化、结构化数据、核心网页指标和内容策略。当用户希望提升搜索可见性、进行SEO修复、使用架构标记、处理站点地图/robots文件或进行关键词映射时使用。

site-architecture by coreyhaines31

When the user wants to plan, map, or restructure their website's page hierarchy, navigation, URL structure, or internal linking. Also use when the user mentions "sitemap," "site map," "visual sitemap," "site structure," "page hierarchy," "information architecture," "IA," "navigation design," "URL structure," "breadcrumbs," "internal linking strategy," "website planning," "what pages do I need," "how should I organize my site," or "site navigation." Use this whenever someone is planning what page

seo-audit by MoizIbnYousaf

When the user wants to audit, review, or diagnose SEO issues, plan site architecture, or implement schema markup. Use when someone says 'SEO audit', 'technical SEO', 'site architecture', 'schema markup', 'internal linking', 'why isn't my site ranking', 'site health check', 'crawl issues', 'fix my SEO', 'my traffic dropped', 'rankings fell', or 'site not ranking'. Also trigger when someone wants to plan URL structure, design navigation, add structured data, or review any website for search perfor

attribution by coreyhaines31

When the user wants to figure out which marketing actually drives conversions and revenue, choose or interpret an attribution model, or reconcile conflicting numbers across tools. Also use when the user mentions "attribution," "attribution model," "first-touch vs last-touch," "multi-touch," "which channel drives revenue," "what's my real CAC," "my dashboards disagree," "Google/Meta says X but GA says Y," "media mix model," "MMM," "incrementality," "geo lift," "holdout test," "how did you hear ab

View original Skill.mdThis page is parsed directly from the repository SKILL.md without editorial rewriting. Collected: Jul 28, 2026 · about 3 min

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

Primary Topic - Specific Modifier | Brand

Meta description formula

Action + topic + value proposition + one supporting detail

JSON-LD example

{
  "@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

[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
Source repo
affaan-m/ECC
Skill path
skills/seo/SKILL.md
Commit SHA
4e973d3eaf92
Repository license
MIT
Data collected