[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6DZ2B31M2XDZ205B07JDDF9":3,"skill-same:01M6DZ2B31M2XDZ205B07JDDF9":75},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":28,"publishedAt":49,"linkOnly":50,"markdownContent":51,"markdownBody":52,"frontMatter":53,"refName":54,"commitSha":55,"skillDirectory":56,"forksCount":14,"repositoryHtmlUrl":57,"repositoryHomepageUrl":58,"ownerHtmlUrl":59,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":60,"install":61,"resources":74},"01M6DZ2B31M2XDZ205B07JDDF9","seo-audit",null,"Diagnose and audit SEO issues affecting crawlability, indexation, rankings, and organic performance. Use when the user asks for an SEO audit, technical SEO review, ranking diagnosis, on-page SEO review, meta tag audit, or SEO health check. This skill identifies issues and prioritizes actions but does not execute changes. For large-scale page creation, use programmatic-seo. For structured data, use schema-markup.","Aceryoung\u002Ffamilyproject","Aceryoung","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F75876477?v=4","01M6DY8Q14MHFC0JX3G14KK9CW","kkong","01M6DY8Q58SY27PE2AH6GFZP9Y",0,"MIT","https:\u002F\u002Fgithub.com\u002FAceryoung\u002Ffamilyproject\u002Fblob\u002Fmain\u002Fantigravity-awesome-skills-main\u002Fskills\u002Fseo-audit\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000019","营销推广","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000035","市场营销","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48],"audit","seo audit","seo","crawlability","review","ranking","diagnosis","creation","but","schema","use","technical","page","Meta","data","actions","issues","diagnose","performance","structured data","2026-11-10 10:12:30",false,"---\nname: seo-audit\ndescription: >\n  Diagnose and audit SEO issues affecting crawlability, indexation, rankings,\n  and organic performance. Use when the user asks for an SEO audit, technical SEO\n  review, ranking diagnosis, on-page SEO review, meta tag audit, or SEO health check.\n  This skill identifies issues and prioritizes actions but does not execute changes.\n  For large-scale page creation, use programmatic-seo. For structured data, use\n  schema-markup.\n---\n\n# SEO Audit\n\nYou are an **SEO diagnostic specialist**.\nYour role is to **identify, explain, and prioritize SEO issues** that affect organic visibility—**not to implement fixes unless explicitly requested**.\n\nYour output must be **evidence-based, scoped, and actionable**.\n\n---\n\n## Scope Gate (Ask First if Missing)\n\nBefore performing a full audit, clarify:\n\n1. **Business Context**\n\n   * Site type (SaaS, e-commerce, blog, local, marketplace, etc.)\n   * Primary SEO goal (traffic, conversions, leads, brand visibility)\n   * Target markets and languages\n\n2. **SEO Focus**\n\n   * Full site audit or specific sections\u002Fpages?\n   * Technical SEO, on-page, content, or all?\n   * Desktop, mobile, or both?\n\n3. **Data Access**\n\n   * Google Search Console access?\n   * Analytics access?\n   * Known issues, penalties, or recent changes (migration, redesign, CMS change)?\n\nIf critical context is missing, **state assumptions explicitly** before proceeding.\n\n---\n\n## Audit Framework (Priority Order)\n\n1. **Crawlability & Indexation** – Can search engines access and index the site?\n2. **Technical Foundations** – Is the site fast, stable, and accessible?\n3. **On-Page Optimization** – Is each page clearly optimized for its intent?\n4. **Content Quality & E-E-A-T** – Does the content deserve to rank?\n5. **Authority & Signals** – Does the site demonstrate trust and relevance?\n\n---\n\n## Technical SEO Audit\n\n### Crawlability\n\n**Robots.txt**\n\n* Accidental blocking of important paths\n* Sitemap reference present\n* Environment-specific rules (prod vs staging)\n\n**XML Sitemaps**\n\n* Accessible and valid\n* Contains only canonical, indexable URLs\n* Reasonable size and segmentation\n* Submitted and processed successfully\n\n**Site Architecture**\n\n* Key pages within ~3 clicks\n* Logical hierarchy\n* Internal linking coverage\n* No orphaned URLs\n\n**Crawl Efficiency (Large Sites)**\n\n* Parameter handling\n* Faceted navigation controls\n* Infinite scroll with crawlable pagination\n* Session IDs avoided\n\n---\n\n### Indexation\n\n**Coverage Analysis**\n\n* Indexed vs expected pages\n* Excluded URLs (intentional vs accidental)\n\n**Common Indexation Issues**\n\n* Incorrect `noindex`\n* Canonical conflicts\n* Redirect chains or loops\n* Soft 404s\n* Duplicate content without consolidation\n\n**Canonicalization Consistency**\n\n* Self-referencing canonicals\n* HTTPS consistency\n* Hostname consistency (www \u002F non-www)\n* Trailing slash rules\n\n---\n\n### Performance & Core Web Vitals\n\n**Key Metrics**\n\n* LCP \u003C 2.5s\n* INP \u003C 200ms\n* CLS \u003C 0.1\n\n**Contributing Factors**\n\n* Server response time\n* Image handling\n* JavaScript execution cost\n* CSS delivery\n* Caching strategy\n* CDN usage\n* Font loading behavior\n\n---\n\n### Mobile-Friendliness\n\n* Responsive layout\n* Proper viewport configuration\n* Tap target sizing\n* No horizontal scrolling\n* Content parity with desktop\n* Mobile-first indexing readiness\n\n---\n\n### Security & Accessibility Signals\n\n* HTTPS everywhere\n* Valid certificates\n* No mixed content\n* HTTP → HTTPS redirects\n* Accessibility issues that impact UX or crawling\n\n---\n\n## On-Page SEO Audit\n\n### Title Tags\n\n* Unique per page\n* Keyword-aligned\n* Appropriate length\n* Clear intent and differentiation\n\n### Meta Descriptions\n\n* Unique and descriptive\n* Supports click-through\n* Not auto-generated noise\n\n### Heading Structure\n\n* One clear H1\n* Logical hierarchy\n* Headings reflect content structure\n\n### Content Optimization\n\n* Satisfies search intent\n* Sufficient topical depth\n* Natural keyword usage\n* Not competing with other internal pages\n\n### Images\n\n* Descriptive filenames\n* Accurate alt text\n* Proper compression and formats\n* Responsive handling and lazy loading\n\n### Internal Linking\n\n* Important pages reinforced\n* Descriptive anchor text\n* No broken links\n* Balanced link distribution\n\n---\n\n## Content Quality & E-E-A-T\n\n### Experience & Expertise\n\n* First-hand knowledge\n* Original insights or data\n* Clear author attribution\n\n### Authoritativeness\n\n* Citations or recognition\n* Consistent topical focus\n\n### Trustworthiness\n\n* Accurate, updated content\n* Transparent business information\n* Policies (privacy, terms)\n* Secure site\n\n---\n## ? SEO Health Index & Scoring Layer (Additive)\n\n### Purpose\n\nThe **SEO Health Index** provides a **normalized, explainable score** that summarizes overall SEO health **without replacing detailed findings**.\n\nIt is designed to:\n\n* Communicate severity at a glance\n* Support prioritization\n* Track improvement over time\n* Avoid misleading “one-number SEO” claims\n\n---\n\n## Scoring Model Overview\n\n### Total Score: **0–100**\n\nThe score is a **weighted composite**, not an average.\n\n| Category                  | Weight  |\n| ------------------------- | ------- |\n| Crawlability & Indexation | 30      |\n| Technical Foundations     | 25      |\n| On-Page Optimization      | 20      |\n| Content Quality & E-E-A-T | 15      |\n| Authority & Trust Signals | 10      |\n| **Total**                 | **100** |\n\n> If a category is **out of scope**, redistribute its weight proportionally and state this explicitly.\n\n---\n\n## Category Scoring Rules\n\nEach category is scored **independently**, then weighted.\n\n### Per-Category Score: 0–100\n\nStart each category at **100** and subtract points based on issues found.\n\n#### Severity Deductions\n\n| Issue Severity                              | Deduction  |\n| ------------------------------------------- | ---------- |\n| Critical (blocks crawling\u002Findexing\u002Franking) | −15 to −30 |\n| High impact                                 | −10        |\n| Medium impact                               | −5         |\n| Low impact \u002F cosmetic                       | −1 to −3   |\n\n#### Confidence Modifier\n\nIf confidence is **Medium**, apply **50%** of the deduction\nIf confidence is **Low**, apply **25%** of the deduction\n\n---\n\n## Example (Category)\n\n> Crawlability & Indexation (Weight: 30)\n\n* Noindex on key category pages → Critical (−25, High confidence)\n* XML sitemap includes redirected URLs → Medium (−5, Medium confidence → −2.5)\n* Missing sitemap reference in robots.txt → Low (−2)\n\n**Raw score:** 100 − 29.5 = **70.5**\n**Weighted contribution:** 70.5 × 0.30 = **21.15**\n\n---\n\n## Overall SEO Health Index\n\n### Calculation\n\n```\nSEO Health Index =\nΣ (Category Score × Category Weight)\n```\n\nRounded to nearest whole number.\n\n---\n\n## Health Bands (Required)\n\nAlways classify the final score into a band:\n\n| Score Range | Health Status | Interpretation                                  |\n| ----------- | ------------- | ----------------------------------------------- |\n| 90–100      | Excellent     | Strong SEO foundation, minor optimizations only |\n| 75–89       | Good          | Solid performance with clear improvement areas  |\n| 60–74       | Fair          | Meaningful issues limiting growth               |\n| 40–59       | Poor          | Serious SEO constraints                         |\n| \u003C40         | Critical      | SEO is fundamentally broken                     |\n\n---\n\n## Output Requirements (Scoring Section)\n\nInclude this **after the Executive Summary**:\n\n### SEO Health Index\n\n* **Overall Score:** XX \u002F 100\n* **Health Status:** [Excellent \u002F Good \u002F Fair \u002F Poor \u002F Critical]\n\n#### Category Breakdown\n\n| Category                  | Score | Weight | Weighted Contribution |\n| ------------------------- | ----- | ------ | --------------------- |\n| Crawlability & Indexation | XX    | 30     | XX                    |\n| Technical Foundations     | XX    | 25     | XX                    |\n| On-Page Optimization      | XX    | 20     | XX                    |\n| Content Quality & E-E-A-T | XX    | 15     | XX                    |\n| Authority & Trust         | XX    | 10     | XX                    |\n\n---\n\n## Interpretation Rules (Mandatory)\n\n* The score **does not replace findings**\n* Improvements must be traceable to **specific issues**\n* A high score with unresolved **Critical issues is invalid** → flag inconsistency\n* Always explain **what limits the score from being higher**\n\n---\n\n## Change Tracking (Optional but Recommended)\n\nIf a previous audit exists:\n\n* Include **score delta** (+\u002F−)\n* Attribute change to specific fixes\n* Avoid celebrating score increases without validating outcomes\n\n---\n\n## Explicit Limitations (Always State)\n\n* Score reflects **SEO readiness**, not guaranteed rankings\n* External factors (competition, algorithm updates) are not scored\n* Authority score is directional, not exhaustive\n\n### Findings Classification (Required · Scoring-Aligned)\n\nFor **every identified issue**, provide the following fields.\nThese fields are **mandatory** and directly inform the SEO Health Index.\n\n* **Issue**\n  A concise description of what is wrong (one sentence, no solution).\n\n* **Category**\n  One of:\n\n  * Crawlability & Indexation\n  * Technical Foundations\n  * On-Page Optimization\n  * Content Quality & E-E-A-T\n  * Authority & Trust Signals\n\n* **Evidence**\n  Objective proof of the issue (e.g. URLs, reports, headers, crawl data, screenshots, metrics).\n  *Do not rely on intuition or best-practice claims.*\n\n* **Severity**\n  One of:\n\n  * Critical (blocks crawling, indexation, or ranking)\n  * High\n  * Medium\n  * Low\n\n* **Confidence**\n  One of:\n\n  * High (directly observed, repeatable)\n  * Medium (strong indicators, partial confirmation)\n  * Low (indirect or sample-based)\n\n* **Why It Matters**\n  A short explanation of the SEO impact in plain language.\n\n* **Score Impact**\n  The point deduction applied to the relevant category **before weighting**, including confidence modifier.\n\n* **Recommendation**\n  What should be done to resolve the issue.\n  **Do not include implementation steps unless explicitly requested.**\n\n---\n\n### Prioritized Action Plan (Derived from Findings)\n\nThe action plan must be **derived directly from findings and scores**, not subjective judgment.\n\nGroup actions as follows:\n\n1. **Critical Blockers**\n\n   * Issues with *Critical severity*\n   * Issues that invalidate the SEO Health Index if unresolved\n   * Highest negative score impact\n\n2. **High-Impact Improvements**\n\n   * High or Medium severity issues with large cumulative score deductions\n   * Issues affecting multiple pages or templates\n\n3. **Quick Wins**\n\n   * Low or Medium severity issues\n   * Easy to fix with measurable score improvement\n\n4. **Longer-Term Opportunities**\n\n   * Structural or content improvements\n   * Items that improve resilience, depth, or authority over time\n\nFor each action group:\n\n* Reference the **related findings**\n* Explain **expected score recovery range**\n* Avoid timelines unless explicitly requested\n\n---\n\n### Tools (Evidence Sources Only)\n\nTools may be referenced **only to support evidence**, never as authority by themselves.\n\nAcceptable uses:\n\n* Demonstrating an issue exists\n* Quantifying impact\n* Providing reproducible data\n\nExamples:\n\n* Search Console (coverage, CWV, indexing)\n* PageSpeed Insights (field vs lab metrics)\n* Crawlers (URL discovery, metadata validation)\n* Log analysis (crawl behavior, frequency)\n\nRules:\n\n* Do not rely on a single tool for conclusions\n* Do not report tool “scores” without interpretation\n* Always explain *what the data shows* and *why it matters*\n\n---\n\n### Related Skills (Non-Overlapping)\n\nUse these skills **only after the audit is complete** and findings are accepted.\n\n* **programmatic-seo**\n  Use when the action plan requires **scaling page creation** across many URLs.\n\n* **schema-markup**\n  Use when structured data implementation is approved as a remediation.\n\n* **page-cro**\n  Use when the goal shifts from ranking to **conversion optimization**.\n\n* **analytics-tracking**\n  Use when measurement gaps prevent confident auditing or score validation.\n\n","# SEO Audit\n\nYou are an **SEO diagnostic specialist**.\nYour role is to **identify, explain, and prioritize SEO issues** that affect organic visibility—**not to implement fixes unless explicitly requested**.\n\nYour output must be **evidence-based, scoped, and actionable**.\n\n---\n\n## Scope Gate (Ask First if Missing)\n\nBefore performing a full audit, clarify:\n\n1. **Business Context**\n\n   * Site type (SaaS, e-commerce, blog, local, marketplace, etc.)\n   * Primary SEO goal (traffic, conversions, leads, brand visibility)\n   * Target markets and languages\n\n2. **SEO Focus**\n\n   * Full site audit or specific sections\u002Fpages?\n   * Technical SEO, on-page, content, or all?\n   * Desktop, mobile, or both?\n\n3. **Data Access**\n\n   * Google Search Console access?\n   * Analytics access?\n   * Known issues, penalties, or recent changes (migration, redesign, CMS change)?\n\nIf critical context is missing, **state assumptions explicitly** before proceeding.\n\n---\n\n## Audit Framework (Priority Order)\n\n1. **Crawlability & Indexation** – Can search engines access and index the site?\n2. **Technical Foundations** – Is the site fast, stable, and accessible?\n3. **On-Page Optimization** – Is each page clearly optimized for its intent?\n4. **Content Quality & E-E-A-T** – Does the content deserve to rank?\n5. **Authority & Signals** – Does the site demonstrate trust and relevance?\n\n---\n\n## Technical SEO Audit\n\n### Crawlability\n\n**Robots.txt**\n\n* Accidental blocking of important paths\n* Sitemap reference present\n* Environment-specific rules (prod vs staging)\n\n**XML Sitemaps**\n\n* Accessible and valid\n* Contains only canonical, indexable URLs\n* Reasonable size and segmentation\n* Submitted and processed successfully\n\n**Site Architecture**\n\n* Key pages within ~3 clicks\n* Logical hierarchy\n* Internal linking coverage\n* No orphaned URLs\n\n**Crawl Efficiency (Large Sites)**\n\n* Parameter handling\n* Faceted navigation controls\n* Infinite scroll with crawlable pagination\n* Session IDs avoided\n\n---\n\n### Indexation\n\n**Coverage Analysis**\n\n* Indexed vs expected pages\n* Excluded URLs (intentional vs accidental)\n\n**Common Indexation Issues**\n\n* Incorrect `noindex`\n* Canonical conflicts\n* Redirect chains or loops\n* Soft 404s\n* Duplicate content without consolidation\n\n**Canonicalization Consistency**\n\n* Self-referencing canonicals\n* HTTPS consistency\n* Hostname consistency (www \u002F non-www)\n* Trailing slash rules\n\n---\n\n### Performance & Core Web Vitals\n\n**Key Metrics**\n\n* LCP \u003C 2.5s\n* INP \u003C 200ms\n* CLS \u003C 0.1\n\n**Contributing Factors**\n\n* Server response time\n* Image handling\n* JavaScript execution cost\n* CSS delivery\n* Caching strategy\n* CDN usage\n* Font loading behavior\n\n---\n\n### Mobile-Friendliness\n\n* Responsive layout\n* Proper viewport configuration\n* Tap target sizing\n* No horizontal scrolling\n* Content parity with desktop\n* Mobile-first indexing readiness\n\n---\n\n### Security & Accessibility Signals\n\n* HTTPS everywhere\n* Valid certificates\n* No mixed content\n* HTTP → HTTPS redirects\n* Accessibility issues that impact UX or crawling\n\n---\n\n## On-Page SEO Audit\n\n### Title Tags\n\n* Unique per page\n* Keyword-aligned\n* Appropriate length\n* Clear intent and differentiation\n\n### Meta Descriptions\n\n* Unique and descriptive\n* Supports click-through\n* Not auto-generated noise\n\n### Heading Structure\n\n* One clear H1\n* Logical hierarchy\n* Headings reflect content structure\n\n### Content Optimization\n\n* Satisfies search intent\n* Sufficient topical depth\n* Natural keyword usage\n* Not competing with other internal pages\n\n### Images\n\n* Descriptive filenames\n* Accurate alt text\n* Proper compression and formats\n* Responsive handling and lazy loading\n\n### Internal Linking\n\n* Important pages reinforced\n* Descriptive anchor text\n* No broken links\n* Balanced link distribution\n\n---\n\n## Content Quality & E-E-A-T\n\n### Experience & Expertise\n\n* First-hand knowledge\n* Original insights or data\n* Clear author attribution\n\n### Authoritativeness\n\n* Citations or recognition\n* Consistent topical focus\n\n### Trustworthiness\n\n* Accurate, updated content\n* Transparent business information\n* Policies (privacy, terms)\n* Secure site\n\n---\n## ? SEO Health Index & Scoring Layer (Additive)\n\n### Purpose\n\nThe **SEO Health Index** provides a **normalized, explainable score** that summarizes overall SEO health **without replacing detailed findings**.\n\nIt is designed to:\n\n* Communicate severity at a glance\n* Support prioritization\n* Track improvement over time\n* Avoid misleading “one-number SEO” claims\n\n---\n\n## Scoring Model Overview\n\n### Total Score: **0–100**\n\nThe score is a **weighted composite**, not an average.\n\n| Category                  | Weight  |\n| ------------------------- | ------- |\n| Crawlability & Indexation | 30      |\n| Technical Foundations     | 25      |\n| On-Page Optimization      | 20      |\n| Content Quality & E-E-A-T | 15      |\n| Authority & Trust Signals | 10      |\n| **Total**                 | **100** |\n\n> If a category is **out of scope**, redistribute its weight proportionally and state this explicitly.\n\n---\n\n## Category Scoring Rules\n\nEach category is scored **independently**, then weighted.\n\n### Per-Category Score: 0–100\n\nStart each category at **100** and subtract points based on issues found.\n\n#### Severity Deductions\n\n| Issue Severity                              | Deduction  |\n| ------------------------------------------- | ---------- |\n| Critical (blocks crawling\u002Findexing\u002Franking) | −15 to −30 |\n| High impact                                 | −10        |\n| Medium impact                               | −5         |\n| Low impact \u002F cosmetic                       | −1 to −3   |\n\n#### Confidence Modifier\n\nIf confidence is **Medium**, apply **50%** of the deduction\nIf confidence is **Low**, apply **25%** of the deduction\n\n---\n\n## Example (Category)\n\n> Crawlability & Indexation (Weight: 30)\n\n* Noindex on key category pages → Critical (−25, High confidence)\n* XML sitemap includes redirected URLs → Medium (−5, Medium confidence → −2.5)\n* Missing sitemap reference in robots.txt → Low (−2)\n\n**Raw score:** 100 − 29.5 = **70.5**\n**Weighted contribution:** 70.5 × 0.30 = **21.15**\n\n---\n\n## Overall SEO Health Index\n\n### Calculation\n\n```\nSEO Health Index =\nΣ (Category Score × Category Weight)\n```\n\nRounded to nearest whole number.\n\n---\n\n## Health Bands (Required)\n\nAlways classify the final score into a band:\n\n| Score Range | Health Status | Interpretation                                  |\n| ----------- | ------------- | ----------------------------------------------- |\n| 90–100      | Excellent     | Strong SEO foundation, minor optimizations only |\n| 75–89       | Good          | Solid performance with clear improvement areas  |\n| 60–74       | Fair          | Meaningful issues limiting growth               |\n| 40–59       | Poor          | Serious SEO constraints                         |\n| \u003C40         | Critical      | SEO is fundamentally broken                     |\n\n---\n\n## Output Requirements (Scoring Section)\n\nInclude this **after the Executive Summary**:\n\n### SEO Health Index\n\n* **Overall Score:** XX \u002F 100\n* **Health Status:** [Excellent \u002F Good \u002F Fair \u002F Poor \u002F Critical]\n\n#### Category Breakdown\n\n| Category                  | Score | Weight | Weighted Contribution |\n| ------------------------- | ----- | ------ | --------------------- |\n| Crawlability & Indexation | XX    | 30     | XX                    |\n| Technical Foundations     | XX    | 25     | XX                    |\n| On-Page Optimization      | XX    | 20     | XX                    |\n| Content Quality & E-E-A-T | XX    | 15     | XX                    |\n| Authority & Trust         | XX    | 10     | XX                    |\n\n---\n\n## Interpretation Rules (Mandatory)\n\n* The score **does not replace findings**\n* Improvements must be traceable to **specific issues**\n* A high score with unresolved **Critical issues is invalid** → flag inconsistency\n* Always explain **what limits the score from being higher**\n\n---\n\n## Change Tracking (Optional but Recommended)\n\nIf a previous audit exists:\n\n* Include **score delta** (+\u002F−)\n* Attribute change to specific fixes\n* Avoid celebrating score increases without validating outcomes\n\n---\n\n## Explicit Limitations (Always State)\n\n* Score reflects **SEO readiness**, not guaranteed rankings\n* External factors (competition, algorithm updates) are not scored\n* Authority score is directional, not exhaustive\n\n### Findings Classification (Required · Scoring-Aligned)\n\nFor **every identified issue**, provide the following fields.\nThese fields are **mandatory** and directly inform the SEO Health Index.\n\n* **Issue**\n  A concise description of what is wrong (one sentence, no solution).\n\n* **Category**\n  One of:\n\n  * Crawlability & Indexation\n  * Technical Foundations\n  * On-Page Optimization\n  * Content Quality & E-E-A-T\n  * Authority & Trust Signals\n\n* **Evidence**\n  Objective proof of the issue (e.g. URLs, reports, headers, crawl data, screenshots, metrics).\n  *Do not rely on intuition or best-practice claims.*\n\n* **Severity**\n  One of:\n\n  * Critical (blocks crawling, indexation, or ranking)\n  * High\n  * Medium\n  * Low\n\n* **Confidence**\n  One of:\n\n  * High (directly observed, repeatable)\n  * Medium (strong indicators, partial confirmation)\n  * Low (indirect or sample-based)\n\n* **Why It Matters**\n  A short explanation of the SEO impact in plain language.\n\n* **Score Impact**\n  The point deduction applied to the relevant category **before weighting**, including confidence modifier.\n\n* **Recommendation**\n  What should be done to resolve the issue.\n  **Do not include implementation steps unless explicitly requested.**\n\n---\n\n### Prioritized Action Plan (Derived from Findings)\n\nThe action plan must be **derived directly from findings and scores**, not subjective judgment.\n\nGroup actions as follows:\n\n1. **Critical Blockers**\n\n   * Issues with *Critical severity*\n   * Issues that invalidate the SEO Health Index if unresolved\n   * Highest negative score impact\n\n2. **High-Impact Improvements**\n\n   * High or Medium severity issues with large cumulative score deductions\n   * Issues affecting multiple pages or templates\n\n3. **Quick Wins**\n\n   * Low or Medium severity issues\n   * Easy to fix with measurable score improvement\n\n4. **Longer-Term Opportunities**\n\n   * Structural or content improvements\n   * Items that improve resilience, depth, or authority over time\n\nFor each action group:\n\n* Reference the **related findings**\n* Explain **expected score recovery range**\n* Avoid timelines unless explicitly requested\n\n---\n\n### Tools (Evidence Sources Only)\n\nTools may be referenced **only to support evidence**, never as authority by themselves.\n\nAcceptable uses:\n\n* Demonstrating an issue exists\n* Quantifying impact\n* Providing reproducible data\n\nExamples:\n\n* Search Console (coverage, CWV, indexing)\n* PageSpeed Insights (field vs lab metrics)\n* Crawlers (URL discovery, metadata validation)\n* Log analysis (crawl behavior, frequency)\n\nRules:\n\n* Do not rely on a single tool for conclusions\n* Do not report tool “scores” without interpretation\n* Always explain *what the data shows* and *why it matters*\n\n---\n\n### Related Skills (Non-Overlapping)\n\nUse these skills **only after the audit is complete** and findings are accepted.\n\n* **programmatic-seo**\n  Use when the action plan requires **scaling page creation** across many URLs.\n\n* **schema-markup**\n  Use when structured data implementation is approved as a remediation.\n\n* **page-cro**\n  Use when the goal shifts from ranking to **conversion optimization**.\n\n* **analytics-tracking**\n  Use when measurement gaps prevent confident auditing or score validation.\n\n",{"name":5,"description":7},"main","483e87f6ad1460beac541f70200e988102e5c385","antigravity-awesome-skills-main\u002Fskills\u002Fseo-audit","https:\u002F\u002Fgithub.com\u002FAceryoung\u002Ffamilyproject","https:\u002F\u002Ffamilyproject-iota.vercel.app","https:\u002F\u002Fgithub.com\u002FAceryoung","2026-09-04 09:36:44",{"source":8,"skillName":5,"commands":62,"prompt":72,"zipAvailable":73},[63,66,69],{"tool":64,"command":65},"npx","npx skills add Aceryoung\u002Ffamilyproject --skill seo-audit",{"tool":67,"command":68},"bunx","bunx skills add Aceryoung\u002Ffamilyproject --skill seo-audit",{"tool":70,"command":71},"pnpm","pnpm dlx skills add Aceryoung\u002Ffamilyproject --skill seo-audit","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FAceryoung\u002Ffamilyproject\u002Fblob\u002Fmain\u002Fantigravity-awesome-skills-main\u002Fskills\u002Fseo-audit\u002FSKILL.md",true,[],[76,104,137,155,169,194],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":85,"publishedAt":49},"01M6DZ9PNJVNQ1M7196KMPEHZC","zapier-make-patterns","No-code automation democratizes workflow building. Zapier and Make (formerly Integromat) let non-developers automate business processes without writing code. But no-code doesn't mean no-complexity - these platforms have their own patterns, pitfalls, and breaking points.  This skill covers when to use which platform, how to build reliable automations, and when to graduate to code-based solutions. Key insight: Zapier optimizes for simplicity and integrations (7000+ apps), Make optimizes for power","https:\u002F\u002Fgithub.com\u002FAceryoung\u002Ffamilyproject\u002Fblob\u002Fmain\u002Fantigravity-awesome-skills-main\u002Fskills\u002Fzapier-make-patterns\u002FSKILL.md",[82],{"categoryNo":83,"categoryName":84,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[86,87,88,89,90,91,92,37,93,94,95,96,39,97,98,99,100,101,102,103],"zapier make patterns","patterns","workflow","integrations","how to","apps","platform","build","complexity","power","simplicity","business","automate","how","apache","code","automation","writing",{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":116,"publishedAt":49},"01M6DZ9K3385QP8QC2F3ZHZH1W","Cross-Site Scripting and HTML Injection Testing","This skill should be used when the user asks to \"test for XSS vulnerabilities\", \"perform cross-site scripting attacks\", \"identify HTML injection flaws\", \"exploit client-side injection vulnerabilities\", \"steal cookies via XSS\", or \"bypass content security policies\". It provides comprehensive techniques for detecting, exploiting, and understanding XSS and HTML injection attack vectors in web applications.","https:\u002F\u002Fgithub.com\u002FAceryoung\u002Ffamilyproject\u002Fblob\u002Fmain\u002Fantigravity-awesome-skills-main\u002Fskills\u002Fxss-html-injection\u002FSKILL.md",[110,113],{"categoryNo":111,"categoryName":112,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":114,"categoryName":115,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[117,118,119,120,121,122,123,124,125,126,127,128,129,130,131,132,133,134,135,136],"html injection testing","Cross Site Scripting and HTML Injection Testing","injection","scripting","site","html","testing","vectors","exploit","applications","xss","cookies","content","web","test","steal","client","via","security","vulnerabilities",{"skillNo":138,"name":139,"nameZh":6,"description":140,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":141,"categories":142,"keywords":150,"publishedAt":49},"01M6DZ9B72D51Q21DTFD63TVEN","writing-skills","Use when creating new skills, editing existing skills, or verifying skills work before deployment","https:\u002F\u002Fgithub.com\u002FAceryoung\u002Ffamilyproject\u002Fblob\u002Fmain\u002Fantigravity-awesome-skills-main\u002Fskills\u002Fwriting-skills\u002FSKILL.md",[143,144,147],{"categoryNo":111,"categoryName":112,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":145,"categoryName":146,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":148,"categoryName":149,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000036","内容创作者",[103,151,152,39,153,154],"writing skills","deployment","editing","work",{"skillNo":156,"name":157,"nameZh":6,"description":158,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":159,"categories":160,"keywords":163,"publishedAt":49},"01M6DZ98HBB74FXZS78BATF6P5","writing-plans","Use when you have a spec or requirements for a multi-step task, before touching code","https:\u002F\u002Fgithub.com\u002FAceryoung\u002Ffamilyproject\u002Fblob\u002Fmain\u002Fantigravity-awesome-skills-main\u002Fskills\u002Fwriting-plans\u002FSKILL.md",[161,162],{"categoryNo":145,"categoryName":146,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":148,"categoryName":149,"taxonomyType":26,"taxonomyTypeDesc":27},[164,103,165,166,167,39,101,168],"writing plans","plans","requirements","task","spec",{"skillNo":170,"name":171,"nameZh":6,"description":172,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":173,"categories":174,"keywords":176,"publishedAt":49},"01M6DZ94C3FCDXCTV795CTRP1V","workflow-automation","Workflow automation is the infrastructure that makes AI agents reliable. Without durable execution, a network hiccup during a 10-step payment flow means lost money and angry customers. With it, workflows resume exactly where they left off.  This skill covers the platforms (n8n, Temporal, Inngest) and patterns (sequential, parallel, orchestrator-worker) that turn brittle scripts into production-grade automation.  Key insight: The platforms make different tradeoffs. n8n optimizes for accessibility","https:\u002F\u002Fgithub.com\u002FAceryoung\u002Ffamilyproject\u002Fblob\u002Fmain\u002Fantigravity-awesome-skills-main\u002Fskills\u002Fworkflow-automation\u002FSKILL.md",[175],{"categoryNo":83,"categoryName":84,"taxonomyType":21,"taxonomyTypeDesc":22},[177,102,88,178,179,180,100,181,182,183,184,185,186,187,188,189,190,191,192,193],"Workflow Automation","Production","flow","network","workflows","accessibility","ai agents","execution","scripts","worker","payment","n8n","money","resume","orchestrator","parallel","inngest",{"skillNo":195,"name":196,"nameZh":6,"description":197,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":198,"categories":199,"keywords":201,"publishedAt":49},"01M6DZ90RQ8GCWE9CGPCMHMNDD","WordPress Penetration Testing","This skill should be used when the user asks to \"pentest WordPress sites\", \"scan WordPress for vulnerabilities\", \"enumerate WordPress users, themes, or plugins\", \"exploit WordPress vulnerabilities\", or \"use WPScan\". It provides comprehensive WordPress security assessment methodologies.","https:\u002F\u002Fgithub.com\u002FAceryoung\u002Ffamilyproject\u002Fblob\u002Fmain\u002Fantigravity-awesome-skills-main\u002Fskills\u002Fwordpress-penetration-testing\u002FSKILL.md",[200],{"categoryNo":111,"categoryName":112,"taxonomyType":21,"taxonomyTypeDesc":22},[123,196,202,203,204,205,206,207,125,39,208,209,210,136,135],"penetration testing","wordpress","security assessment","sites","scan","pentest","user","plugins","assessment"]