seo
- Use it when:
- You want better search visibility for a site: an SEO audit, schema markup, sitemap or robots work, or keyword mapping.
- It does:
- Checks technical blockers before content, then on-page rules, keyword-to-URL mapping and internal links, each with concrete targets.
- You get:
- Findings with a severity, file location, issue and fix, each tied to a specific page or asset rather than generic advice.
- Targets:
- LCP under 2.5s, INP under 200ms, CLS under 0.1, titles of 50-60 characters and meta descriptions of 120-160.
- Avoids:
- Keyword stuffing, thin near-duplicate pages, and schema for content that isn't actually on the page.
TL;DR
ECC's SEO skill puts technical correctness ahead of content tweaks and gives each page one search intent. Its technical checklist covers crawlability (robots.txt, unintended noindex, shallow click depth, redirect chains of at most two hops, consistent canonicals), indexability (consistent URLs, hreflang, sitemaps that match the public pages, duplicates under canonical control), Core Web Vitals with common fixes such as preloading hero assets and reserving layout space, and which schema.org types fit which pages, with a JSON-LD example. On-page rules set lengths and formulas for titles and meta descriptions and ask for one clear H1. Keyword mapping goes from search intent to realistic variants, ranked by intent, value and competition, with one primary keyword per URL and a check for pages competing for the same one. Internal linking sends links from strong pages with descriptive anchors. Findings come as severity, location, issue and fix, and every recommendation has to point to a page or asset after reading the real page. It runs no crawler or tool of its own.
Summarizes the skill at d2ef268.
npx skills add https://github.com/affaan-m/ecc --skill seo skills.sh pageSource on GitHubAll skills from affaan-m/ecc
- Total Downloads
- 6,000 on skills.sh, Nov 9, 2026
- Repo stars
- 299,776 affaan-m/ecc
- First seen
- May 19, 2026 on skills.sh
Weekly values
| Week to | Installs |
|---|---|
| Sep 21 | 291 |
| Sep 28 | 193 |
| Oct 5 | 170 |
| Oct 12 | 256 |
| Oct 19 | 422 |
| Oct 26 | 418 |
| Nov 2 | 488 |
| Nov 9 | 467 |
| Category |
SEO, copy, conversion, social media and e-commerce. |
|---|---|
| Type |
Knowledge and rules the agent applies while it works: best practices, design principles, API references. |
| Effect |
Adds no side effects of its own. It shapes how the agent thinks, writes or reviews. Guidelines and routers are always effect:none, even when the task they support edits code. |
| Needs |
Instructions only. Works in any agent that supports skills. |
| Publisher |
Everyone else. Unverified vendor claims default to community. |
| Topics |
SKILL.md
From affaan-m/ecc at d2ef268. Checked daily, last changed Nov 6, 2026.
Frontmatter
name: seo
description: 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.
metadata:
origin: ECCSEO
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
- Fix technical blockers before content optimization.
- One page should have one clear primary search intent.
- Prefer long-term quality signals over manipulative patterns.
- Mobile-first assumptions matter because indexing is mobile-first.
- Recommendations should be page-specific and implementable.
Technical SEO checklist
Crawlability
robots.txtshould 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:
ProductandOffer - interior pages:
BreadcrumbList - Q&A sections:
FAQPageonly 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 H2andH3should reflect actual content hierarchy- do not skip structure just for visual styling
Keyword mapping
- define the search intent
- gather realistic keyword variants
- prioritize by intent match, likely value, and competition
- map one primary keyword/theme to one URL
- 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-pattern | Fix |
|---|---|
| keyword stuffing | write for users first |
| thin near-duplicate pages | consolidate or differentiate them |
| schema for content that is not actually present | match schema to reality |
| content advice without checking the actual page | read the real page first |
| generic “improve SEO” outputs | tie every recommendation to a page or asset |
Related Skills
seo-specialistfrontend-patternsbrand-voicemarket-research