Source profileQuality 83/100

affaan-m/ECC/skills/seo/SKILL.md

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.

Source repository stars
234,327
Declared platforms
0
Static risk flags
1
Last source update
2026-07-27
Source checked
2026-07-28

Decision brief

What it does—and where it fits

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

Best for

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

Not for

  • Tasks that require unconfirmed production actions or broad system permissions.
  • Environments where the pinned source and install steps cannot be inspected.

Compatibility matrix

Platform support, with evidence labels

PlatformStatusEvidenceWhat to check
CodexNot declaredNo explicit evidencePortability before use
Claude CodeNot declaredNo explicit evidencePortability before use
CursorNot declaredNo explicit evidencePortability before use
Gemini CLINot declaredNo explicit evidencePortability before use
Open the compatibility checker

Installation

Inspect first. Install second.

The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.

Source-detected install commandSource
npx skills add https://github.com/affaan-m/ECC --skill "skills/seo"
Safe inspection promptEditorial

Inspect the Agent Skill "seo" from https://github.com/affaan-m/ECC/blob/4e973d3eaf92d97f8d2e2d8abb39d8bdc8711b38/skills/seo/SKILL.md at commit 4e973d3eaf92d97f8d2e2d8abb39d8bdc8711b38. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.

Workflow

What the source asks the agent to do

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

    auditing crawlability, indexability, canonicals, or redirectsimproving title tags, meta descriptions, and heading structureadding or validating structured data
  2. 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-…

    Fix technical blockers before content optimization.One page should have one clear primary search intent.Prefer long-term quality signals over manipulative patterns.
  3. 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-…

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

    Technical SEO checklist

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

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

    Crawlability

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

    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

Permission review

Static risk signals and limitations

Network access

medium · line 110

The documentation includes network, browsing, or remote request actions.

"@context": "https://schema.org",

Evidence record

Why each signal appears

EvidenceSourceComputedTestedEditorial
SignalValueEvidence typeMeaning
Quality score83/100ComputedDocumentation, specificity, maintenance, and trust rules
Repository stars234,327SourceRepository attention, not individual Skill quality
Compatibility0 platformsSourceDeclared in the catalog source record
Usage guideautomated source guideEditorialGenerated or reviewed according to the visible evidence level

Pinned source

Provenance and original SKILL.md

Repository
affaan-m/ECC
Skill path
skills/seo/SKILL.md
Commit
4e973d3eaf92d97f8d2e2d8abb39d8bdc8711b38
License
MIT
Collected
2026-07-28
Default branch
main
View the original SKILL.md

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

Alternatives

Compare before choosing