[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EVXEP2AMGC150DG5HSSQEX":3,"skill-same:01M7EVXEP2AMGC150DG5HSSQEX":45},{"skillNo":4,"name":5,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M7EVXEP2AMGC150DG5HSSQEX","ams-seo-site-auditor",null,"TanNhatCMS\u002Fjarvis","TanNhatCMS","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F113796420?v=4","01M753MV17KG5CD3152G3WQEQY","KietNT","01M7EKEDYVYQ6PWVJJMZ911VMX",0,"MIT","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-seo-site-auditor\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: seo-site-auditor\ndescription: Audit websites for SEO: crawling, technical checks, metadata, Core Web Vitals, structured data, and prioritized fixes. Use when diagnosing search visibility problems.\ncategory: web-development\n---\n\n# SEO Site Auditor\n\nA systematic approach to technical SEO audits: crawling a site, checking indexability, metadata, structured data, performance, and content signals — then prioritizing fixes by impact and effort.\n\n## Overview\n\nSEO audits fail when they're 200-line checklists with no priorities. This skill is a **triage method**: crawl → identify what's blocking indexing\u002Franking → verify the high-impact basics (titles, canonicals, sitemaps, speed, structured data) → prioritize by (traffic at stake × effort). Most sites' SEO problems are a handful of fixable technical issues, not mysterious algorithm behavior.\n\n## When to use\n\n- Traffic drops or pages not appearing in search.\n- Pre-launch SEO review of a new site or migration.\n- Periodic technical health checks.\n- Evaluating an agency\u002Ffreelancer SEO proposal (know what good looks like).\n\n## Core concepts\n\n- **Crawlability.** Can bots fetch and render pages? Check robots.txt, meta robots, HTTP status codes, redirect chains, and JS-rendering (view-source vs rendered DOM for key content).\n- **Indexability.** `noindex` tags, canonical tags (self-referencing where appropriate), sitemap.xml accuracy, Search Console coverage report.\n- **Metadata.** Unique `\u003Ctitle>` (50–60 chars, keyword-front-loaded naturally), meta descriptions (compelling, ~150 chars — they don't rank you but earn clicks), one H1 per page, logical heading hierarchy.\n- **Structured data.** JSON-LD schema.org (Article, Product, FAQ, BreadcrumbList, Organization) — validates in Rich Results Test; enables rich snippets.\n- **Core Web Vitals.** LCP \u003C 2.5s, INP \u003C 200ms, CLS \u003C 0.1 — measured via PageSpeed Insights \u002F CrUX (field data beats lab data).\n- **Content signals.** Thin\u002Fduplicate content, keyword cannibalization (multiple pages targeting the same query), internal linking depth (important pages ≤ 3 clicks from home).\n- **Migration risks.** URL changes without 301s, lost metadata, staging `noindex` leaking to production.\n\n## Practical workflow\n\n**1. Crawl.**\n```bash\n# CLI crawl for status codes, titles, canonicals, noindex\nnpx broken-link-checker https:\u002F\u002Fexample.com --ordered\n# or: screaming-frog-style desktop crawler for full audits\ncurl -sI https:\u002F\u002Fexample.com\u002Frobots.txt\ncurl -s https:\u002F\u002Fexample.com\u002Fsitemap.xml | head -50\n```\nCheck: 200s where expected, no redirect chains (>2 hops), noindex only where intended, canonicals absolute and self-consistent.\n\n**2. Indexation check.** Search Console: coverage errors, \"discovered not indexed\" (crawl budget\u002Fcontent quality signal), sitemap submission status. `site:example.com` for a rough indexed-page count.\n\n**3. Page-level audit (top 20 pages).**\n- Title unique and descriptive? Meta description present and click-worthy?\n- H1 present, single, matching intent? Headings hierarchical?\n- Canonical correct? Open Graph\u002FTwitter cards render (test with validators)?\n- JSON-LD valid? (Rich Results Test)\n- Images: descriptive alt, compressed, modern formats, width\u002Fheight set (CLS)?\n\n**4. Performance.** PageSpeed Insights per template (not just homepage): LCP element identified, INP interactions, CLS sources. Fix images\u002Ffonts\u002FJS bloat first — they're usually the cause.\n\n**5. Content.** Identify: thin pages (\u003C few hundred useful words), duplicates\u002Fnear-duplicates, cannibalization (Search Console: two pages ranking for the same query — consolidate).\n\n**6. Prioritize.** Score each finding: impact (traffic at stake) × effort (dev hours). Fix order: blocking (noindex leaks, 5xx) → high-impact quick wins (titles, canonicals) → structural (internal linking, speed) → content (consolidation, new content).\n\n## Common pitfalls\n\n- **`noindex` on production.** Staging configs leaking to prod — the single most expensive one-line SEO bug. Check after every deploy.\n- **JS-rendered critical content.** If the title, headings, or body text only exist after JS runs, crawlers may miss or delay them. SSR critical content.\n- **Canonical chaos.** Canonicals pointing to wrong URLs, chains, or http\u002Fhttps mismatches. Every indexable page: self-referencing absolute canonical.\n- **Sitemap fiction.** Sitemaps listing 404s, noindexed pages, or missing new content. Regenerate automatically; keep under 50k URLs per file.\n- **Title\u002Fdescription duplication.** Same title on 500 product pages = missed clicks. Templates with unique variables (product name, category).\n- **Chasing scores over users.** Perfect Lighthouse 100 with thin content ranks worse than useful content at 85. Technical SEO is table stakes; content wins.\n- **Ignoring Search Console.** The only source of truth for how Google sees your site. Check coverage, enhancements, and manual actions regularly.\n- **Migration without redirects.** Relaunching with new URLs and no 301 map = traffic cliff. Map every old URL → new (or closest equivalent) before launch.\n- **Keyword stuffing.** 2010 called. Write for the query's intent; use the keyword naturally in title\u002FH1\u002Fearly body.\n","# SEO Site Auditor\n\nA systematic approach to technical SEO audits: crawling a site, checking indexability, metadata, structured data, performance, and content signals — then prioritizing fixes by impact and effort.\n\n## Overview\n\nSEO audits fail when they're 200-line checklists with no priorities. This skill is a **triage method**: crawl → identify what's blocking indexing\u002Franking → verify the high-impact basics (titles, canonicals, sitemaps, speed, structured data) → prioritize by (traffic at stake × effort). Most sites' SEO problems are a handful of fixable technical issues, not mysterious algorithm behavior.\n\n## When to use\n\n- Traffic drops or pages not appearing in search.\n- Pre-launch SEO review of a new site or migration.\n- Periodic technical health checks.\n- Evaluating an agency\u002Ffreelancer SEO proposal (know what good looks like).\n\n## Core concepts\n\n- **Crawlability.** Can bots fetch and render pages? Check robots.txt, meta robots, HTTP status codes, redirect chains, and JS-rendering (view-source vs rendered DOM for key content).\n- **Indexability.** `noindex` tags, canonical tags (self-referencing where appropriate), sitemap.xml accuracy, Search Console coverage report.\n- **Metadata.** Unique `\u003Ctitle>` (50–60 chars, keyword-front-loaded naturally), meta descriptions (compelling, ~150 chars — they don't rank you but earn clicks), one H1 per page, logical heading hierarchy.\n- **Structured data.** JSON-LD schema.org (Article, Product, FAQ, BreadcrumbList, Organization) — validates in Rich Results Test; enables rich snippets.\n- **Core Web Vitals.** LCP \u003C 2.5s, INP \u003C 200ms, CLS \u003C 0.1 — measured via PageSpeed Insights \u002F CrUX (field data beats lab data).\n- **Content signals.** Thin\u002Fduplicate content, keyword cannibalization (multiple pages targeting the same query), internal linking depth (important pages ≤ 3 clicks from home).\n- **Migration risks.** URL changes without 301s, lost metadata, staging `noindex` leaking to production.\n\n## Practical workflow\n\n**1. Crawl.**\n```bash\n# CLI crawl for status codes, titles, canonicals, noindex\nnpx broken-link-checker https:\u002F\u002Fexample.com --ordered\n# or: screaming-frog-style desktop crawler for full audits\ncurl -sI https:\u002F\u002Fexample.com\u002Frobots.txt\ncurl -s https:\u002F\u002Fexample.com\u002Fsitemap.xml | head -50\n```\nCheck: 200s where expected, no redirect chains (>2 hops), noindex only where intended, canonicals absolute and self-consistent.\n\n**2. Indexation check.** Search Console: coverage errors, \"discovered not indexed\" (crawl budget\u002Fcontent quality signal), sitemap submission status. `site:example.com` for a rough indexed-page count.\n\n**3. Page-level audit (top 20 pages).**\n- Title unique and descriptive? Meta description present and click-worthy?\n- H1 present, single, matching intent? Headings hierarchical?\n- Canonical correct? Open Graph\u002FTwitter cards render (test with validators)?\n- JSON-LD valid? (Rich Results Test)\n- Images: descriptive alt, compressed, modern formats, width\u002Fheight set (CLS)?\n\n**4. Performance.** PageSpeed Insights per template (not just homepage): LCP element identified, INP interactions, CLS sources. Fix images\u002Ffonts\u002FJS bloat first — they're usually the cause.\n\n**5. Content.** Identify: thin pages (\u003C few hundred useful words), duplicates\u002Fnear-duplicates, cannibalization (Search Console: two pages ranking for the same query — consolidate).\n\n**6. Prioritize.** Score each finding: impact (traffic at stake) × effort (dev hours). Fix order: blocking (noindex leaks, 5xx) → high-impact quick wins (titles, canonicals) → structural (internal linking, speed) → content (consolidation, new content).\n\n## Common pitfalls\n\n- **`noindex` on production.** Staging configs leaking to prod — the single most expensive one-line SEO bug. Check after every deploy.\n- **JS-rendered critical content.** If the title, headings, or body text only exist after JS runs, crawlers may miss or delay them. SSR critical content.\n- **Canonical chaos.** Canonicals pointing to wrong URLs, chains, or http\u002Fhttps mismatches. Every indexable page: self-referencing absolute canonical.\n- **Sitemap fiction.** Sitemaps listing 404s, noindexed pages, or missing new content. Regenerate automatically; keep under 50k URLs per file.\n- **Title\u002Fdescription duplication.** Same title on 500 product pages = missed clicks. Templates with unique variables (product name, category).\n- **Chasing scores over users.** Perfect Lighthouse 100 with thin content ranks worse than useful content at 85. Technical SEO is table stakes; content wins.\n- **Ignoring Search Console.** The only source of truth for how Google sees your site. Check coverage, enhancements, and manual actions regularly.\n- **Migration without redirects.** Relaunching with new URLs and no 301 map = traffic cliff. Map every old URL → new (or closest equivalent) before launch.\n- **Keyword stuffing.** 2010 called. Write for the query's intent; use the keyword naturally in title\u002FH1\u002Fearly body.\n",{},"main","af388a77c2fe5e0b4fd879cca4300a0ffa9a6579","skills\u002Fams-seo-site-auditor",1,"https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis","https:\u002F\u002Fgithub.com\u002FTanNhatCMS","https:\u002F\u002Fmrkiet.name.vn","2026-11-07 14:23:08",{"source":7,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add TanNhatCMS\u002Fjarvis --skill ams-seo-site-auditor",{"tool":37,"command":38},"bunx","bunx skills add TanNhatCMS\u002Fjarvis --skill ams-seo-site-auditor",{"tool":40,"command":41},"pnpm","pnpm dlx skills add TanNhatCMS\u002Fjarvis --skill ams-seo-site-auditor","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-seo-site-auditor\u002FSKILL.md",true,[],[46,53,61,68,75,82],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":18},"01M7EWYJR0J8DARY7E59Z6Y9MV","web-scrape","Turn web pages into LLM-ready markdown via the Firecrawl API (renders JS, anti-bot handling). Use when browser_open\u002Ffetch fails on JS-heavy pages, or when you need clean markdown\u002Fstructured extraction from a site. Requires FIRECRAWL_API_KEY.","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fweb-scrape\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":57,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":18},"01M7EWYBN5P6F2AJG3FR24T9BP","design-taste-frontend","tasteskill v2, the anti-slop frontend skill. Art direction for websites, distilled from a study of 247 curated gallery sites (One Page Love, Awwwards Sites of the Day). Deals researched directions (idea, composition, type, palette, photographs, section blueprints) from a library, enforces a strict no-slop house style with a real-browser inspector, and runs a look-and-fix loop on screenshots. Use this whenever you build, design, redesign, restyle, polish or review a landing page, marketing site, portfolio, product page, one-pager, hero or any public-facing web page, in any stack (HTML\u002FCSS, React, Next.js, Vue, Svelte, Astro, Tailwind) — also when the user says a page looks generic, templated, \"AI-made\", sloppy, or asks to make it look designed, premium, award-level or less like every other site. Not for dashboards or app screens.","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Ftaste-design\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Ftaste-design\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":18},"01M7EWY8FQFNQ2GB7NZZWGSSDX","test-driven-development","Use when implementing any feature or bugfix, before writing implementation code","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-tdd\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":18},"01M7EWY5SHBFRH1HDHVWM9K7TV","systematic-debugging","Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-debugging\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":18},"01M7EWY3NM0Z0JAKS7HDZ24K66","requesting-code-review","Use when completing tasks, implementing major features, or before merging to verify work meets requirements","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-code-review\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":18},"01M7EWY0WRMWX4M9ZFY0WKC593","brainstorming","You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-brainstorming\u002FSKILL.md",[],[]]