{
  "manifest": {
    "id": "seo",
    "name": "SEO",
    "description": "Search engine optimization patterns, technical SEO, structured data, meta tags, sitemaps, Core Web Vitals, and content optimization",
    "version": "1.0.0",
    "author": "Adiuvo",
    "tags": [
      "seo",
      "search",
      "meta",
      "structured-data",
      "performance"
    ],
    "icon": "",
    "created_at": "2026-06-11T01:40:46Z",
    "updated_at": "2026-06-11T01:40:46Z",
    "category": "",
    "pack_type": "enhancement",
    "required_mcp_servers": [],
    "optional_mcp_servers": [],
    "on_install": null,
    "procedure_count": 0,
    "context_file_count": 1,
    "always_loaded": false
  },
  "index": "# SEO\n\nSearch engine optimization patterns covering technical SEO, structured data, and content optimization.\n\n## What's Included\n\n- **SEO** -- Technical SEO, meta tags, Open Graph, structured data (JSON-LD), sitemaps, robots.txt, canonical URLs, Core Web Vitals, and content optimization strategies\n\n## When to Use\n\nActivate this pack when:\n- Implementing technical SEO for web applications\n- Adding structured data and schema markup\n- Optimizing meta tags, Open Graph, and social sharing\n- Configuring sitemaps and robots.txt\n- Improving Core Web Vitals and page performance\n",
  "procedures": [],
  "commands": [],
  "context_files": [
    {
      "filename": "seo-patterns.md",
      "content": "---\nname: seo\ndescription: 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.\norigin: ECC\n---\n\n# SEO\n\nImprove search visibility through technical correctness, performance, and content relevance, not gimmicks.\n\n## When to Use\n\nUse this skill when:\n- auditing crawlability, indexability, canonicals, or redirects\n- improving title tags, meta descriptions, and heading structure\n- adding or validating structured data\n- improving Core Web Vitals\n- doing keyword research and mapping keywords to URLs\n- planning internal linking or sitemap / robots changes\n\n## How It Works\n\n### Principles\n\n1. Fix technical blockers before content optimization.\n2. One page should have one clear primary search intent.\n3. Prefer long-term quality signals over manipulative patterns.\n4. Mobile-first assumptions matter because indexing is mobile-first.\n5. Recommendations should be page-specific and implementable.\n\n### Technical SEO checklist\n\n#### Crawlability\n\n- `robots.txt` should allow important pages and block low-value surfaces\n- no important page should be unintentionally `noindex`\n- important pages should be reachable within a shallow click depth\n- avoid redirect chains longer than two hops\n- canonical tags should be self-consistent and non-looping\n\n#### Indexability\n\n- preferred URL format should be consistent\n- multilingual pages need correct hreflang if used\n- sitemaps should reflect the intended public surface\n- no duplicate URLs should compete without canonical control\n\n#### Performance\n\n- LCP < 2.5s\n- INP < 200ms\n- CLS < 0.1\n- common fixes: preload hero assets, reduce render-blocking work, reserve layout space, trim heavy JS\n\n#### Structured data\n\n- homepage: organization or business schema where appropriate\n- editorial pages: `Article` / `BlogPosting`\n- product pages: `Product` and `Offer`\n- interior pages: `BreadcrumbList`\n- Q&A sections: `FAQPage` only when the content truly matches\n\n### On-page rules\n\n#### Title tags\n\n- aim for roughly 50-60 characters\n- put the primary keyword or concept near the front\n- make the title legible to humans, not stuffed for bots\n\n#### Meta descriptions\n\n- aim for roughly 120-160 characters\n- describe the page honestly\n- include the main topic naturally\n\n#### Heading structure\n\n- one clear `H1`\n- `H2` and `H3` should reflect actual content hierarchy\n- do not skip structure just for visual styling\n\n### Keyword mapping\n\n1. define the search intent\n2. gather realistic keyword variants\n3. prioritize by intent match, likely value, and competition\n4. map one primary keyword/theme to one URL\n5. detect and avoid cannibalization\n\n### Internal linking\n\n- link from strong pages to pages you want to rank\n- use descriptive anchor text\n- avoid generic anchors when a more specific one is possible\n- backfill links from new pages to relevant existing ones\n\n## Examples\n\n### Title formula\n\n```text\nPrimary Topic - Specific Modifier | Brand\n```\n\n### Meta description formula\n\n```text\nAction + topic + value proposition + one supporting detail\n```\n\n### JSON-LD example\n\n```json\n{\n  \"@context\": \"https://schema.org\",\n  \"@type\": \"Article\",\n  \"headline\": \"Page Title Here\",\n  \"author\": {\n    \"@type\": \"Person\",\n    \"name\": \"Author Name\"\n  },\n  \"publisher\": {\n    \"@type\": \"Organization\",\n    \"name\": \"Brand Name\"\n  }\n}\n```\n\n### Audit output shape\n\n```text\n[HIGH] Duplicate title tags on product pages\nLocation: src/routes/products/[slug].tsx\nIssue: Dynamic titles collapse to the same default string, which weakens relevance and creates duplicate signals.\nFix: Generate a unique title per product using the product name and primary category.\n```\n\n## Anti-Patterns\n\n| Anti-pattern | Fix |\n| --- | --- |\n| keyword stuffing | write for users first |\n| thin near-duplicate pages | consolidate or differentiate them |\n| schema for content that is not actually present | match schema to reality |\n| content advice without checking the actual page | read the real page first |\n| generic “improve SEO” outputs | tie every recommendation to a page or asset |\n\n## Related Skills\n\n- `seo-specialist`\n- `frontend-patterns`\n- `brand-voice`\n- `market-research`\n"
    }
  ]
}