[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CNACMS1CGPV74P1FW2QQSA":3,"skill-same:01M7CNACMS1CGPV74P1FW2QQSA":56},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":15,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":31,"commitSha":32,"skillDirectory":33,"forksCount":13,"repositoryHtmlUrl":34,"repositoryHomepageUrl":35,"ownerHtmlUrl":36,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":37,"install":38,"resources":50},"01M7CNACMS1CGPV74P1FW2QQSA","seo-page",null,"Deep single-page SEO analysis covering on-page elements, content quality, technical meta tags, schema, images, and performance. Use when user says \"analyze this page\", \"check page SEO\", \"single URL\", \"check this page\", \"page analysis\", or provides a single URL for review.","bwpahmed\u002FLifeOS","bwpahmed","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F234085842?v=4","01M7CMXA48YN1ZAY7M1JFFE6C3","01M7CMXA50BHWABHN32GWXPDDP",0,"MIT","https:\u002F\u002Fgithub.com\u002Fbwpahmed\u002FLifeOS\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fseo-page\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fbwpahmed\u002FLifeOS\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fseo-page\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: seo-page\ndescription: >\n  Deep single-page SEO analysis covering on-page elements, content quality,\n  technical meta tags, schema, images, and performance. Use when user says\n  \"analyze this page\", \"check page SEO\", \"single URL\", \"check this page\",\n  \"page analysis\", or provides a single URL for review.\nuser-invocable: true\nargument-hint: \"[url]\"\nlicense: MIT\nmetadata:\n  author: AgriciDaniel\n  version: \"2.3.1\"\n  category: seo\n---\n\n# Single Page Analysis\n\n## What to Analyze\n\n### On-Page SEO\n- Title tag: 50-60 characters, includes primary keyword, unique\n- Meta description: 150-160 characters, compelling, includes keyword\n- Meta description is not a restatement of the title: run\n  `\"$(git rev-parse --show-toplevel)\u002F.agents\u002Fvendor\u002Fclaude-seo\u002Fscripts\u002Fclaude-seo\" run metadata_template.py --title \"\u003Ctitle>\" --description \"\u003Cdesc>\" --json`\n  (heuristic, deterministic string comparison). A description that opens by\n  repeating its own title and closes on a stock CTA (\"Try it free now.\",\n  \"Start free!\") is templated metadata, the shape bulk generation jobs produce\n  site-wide, and duplicated or templated metadata is a documented\n  content-quality problem regardless of how original the body copy is\n- H1: exactly one, matches page intent, includes keyword\n- H2-H6: logical hierarchy (no skipped levels), descriptive\n- URL: short, descriptive, hyphenated, no parameters\n- Internal links: sufficient, relevant anchor text, no orphan pages\n- External links: to authoritative sources, reasonable count\n\n### Content Quality\n- Word count vs page type minimums (see quality-gates.md)\n- Readability: Flesch Reading Ease score, grade level\n- Keyword density: natural (1-3%), semantic variations present\n- E-E-A-T signals: author bio, credentials, first-hand experience markers\n- Content freshness: publication date, last updated date\n\n### Technical Elements\n- Canonical tag: present, self-referencing or correct\n- Meta robots: index\u002Ffollow unless intentionally blocked\n- Open Graph: og:title, og:description, og:image, og:url\n- Twitter Card: twitter:card, twitter:title, twitter:description\n- Hreflang: if multi-language, correct implementation\n\n### Schema Markup\n- Detect all types (JSON-LD preferred)\n- Validate required properties\n- Identify missing opportunities\n- Never recommend HowTo (deprecated) or FAQ for rich results (retired May 2026); existing FAQPage need not be removed, use QAPage for genuine Q&A\n\n### Images\n- Alt text: present, descriptive, includes keywords where natural\n- File size: flag >200KB (warning), >500KB (critical)\n- Format: recommend WebP\u002FAVIF over JPEG\u002FPNG\n- Dimensions: width\u002Fheight set for CLS prevention\n- Lazy loading: report `lazy_method` per image (native | perfmatters | ewww | js-generic | none). Do not flag \"not lazy-loaded\" when JS lazy-loaders (Perfmatters, EWWW, lazysizes) are detected, they intentionally strip the native `loading=\"lazy\"` attribute and use `data-src` placeholders\n\n### Core Web Vitals (reference only, not measurable from HTML alone)\n- Flag potential LCP issues (huge hero images, render-blocking resources)\n- Flag potential INP issues (heavy JS, no async\u002Fdefer)\n- Flag potential CLS issues (missing image dimensions, injected content)\n\n## Output\n\n### Page Score Card\n```\nOverall Score: XX\u002F100\n\nOn-Page SEO:     XX\u002F100  ████████░░\nContent Quality: XX\u002F100  ██████████\nTechnical:       XX\u002F100  ███████░░░\nSchema:          XX\u002F100  █████░░░░░\nImages:          XX\u002F100  ████████░░\n```\n\n### Issues Found\nOrganized by priority: Critical -> High -> Medium -> Low\n\n### Recommendations\nSpecific, actionable improvements with expected impact\n\n### Schema Suggestions\nReady-to-use JSON-LD code for detected opportunities\n\n## DataForSEO Integration (Optional)\n\nIf DataForSEO MCP tools are available, use `serp_organic_live_advanced` for real SERP positions and `backlinks_summary` for backlink data and spam scores.\n\n## Error Handling\n\n| Scenario | Action |\n|----------|--------|\n| URL unreachable (DNS failure, connection refused) | Report the error clearly. Do not guess page content. Suggest the user verify the URL and try again. |\n| Page requires authentication (401\u002F403) | Report that the page is behind authentication. Suggest the user provide the rendered HTML directly or a publicly accessible URL. |\n| JavaScript-rendered content (empty body in HTML) | Note that key content may be rendered client-side. Analyze the available HTML and flag that results may be incomplete. Suggest using a browser-rendered snapshot if available. |\n","# Single Page Analysis\n\n## What to Analyze\n\n### On-Page SEO\n- Title tag: 50-60 characters, includes primary keyword, unique\n- Meta description: 150-160 characters, compelling, includes keyword\n- Meta description is not a restatement of the title: run\n  `\"$(git rev-parse --show-toplevel)\u002F.agents\u002Fvendor\u002Fclaude-seo\u002Fscripts\u002Fclaude-seo\" run metadata_template.py --title \"\u003Ctitle>\" --description \"\u003Cdesc>\" --json`\n  (heuristic, deterministic string comparison). A description that opens by\n  repeating its own title and closes on a stock CTA (\"Try it free now.\",\n  \"Start free!\") is templated metadata, the shape bulk generation jobs produce\n  site-wide, and duplicated or templated metadata is a documented\n  content-quality problem regardless of how original the body copy is\n- H1: exactly one, matches page intent, includes keyword\n- H2-H6: logical hierarchy (no skipped levels), descriptive\n- URL: short, descriptive, hyphenated, no parameters\n- Internal links: sufficient, relevant anchor text, no orphan pages\n- External links: to authoritative sources, reasonable count\n\n### Content Quality\n- Word count vs page type minimums (see quality-gates.md)\n- Readability: Flesch Reading Ease score, grade level\n- Keyword density: natural (1-3%), semantic variations present\n- E-E-A-T signals: author bio, credentials, first-hand experience markers\n- Content freshness: publication date, last updated date\n\n### Technical Elements\n- Canonical tag: present, self-referencing or correct\n- Meta robots: index\u002Ffollow unless intentionally blocked\n- Open Graph: og:title, og:description, og:image, og:url\n- Twitter Card: twitter:card, twitter:title, twitter:description\n- Hreflang: if multi-language, correct implementation\n\n### Schema Markup\n- Detect all types (JSON-LD preferred)\n- Validate required properties\n- Identify missing opportunities\n- Never recommend HowTo (deprecated) or FAQ for rich results (retired May 2026); existing FAQPage need not be removed, use QAPage for genuine Q&A\n\n### Images\n- Alt text: present, descriptive, includes keywords where natural\n- File size: flag >200KB (warning), >500KB (critical)\n- Format: recommend WebP\u002FAVIF over JPEG\u002FPNG\n- Dimensions: width\u002Fheight set for CLS prevention\n- Lazy loading: report `lazy_method` per image (native | perfmatters | ewww | js-generic | none). Do not flag \"not lazy-loaded\" when JS lazy-loaders (Perfmatters, EWWW, lazysizes) are detected, they intentionally strip the native `loading=\"lazy\"` attribute and use `data-src` placeholders\n\n### Core Web Vitals (reference only, not measurable from HTML alone)\n- Flag potential LCP issues (huge hero images, render-blocking resources)\n- Flag potential INP issues (heavy JS, no async\u002Fdefer)\n- Flag potential CLS issues (missing image dimensions, injected content)\n\n## Output\n\n### Page Score Card\n```\nOverall Score: XX\u002F100\n\nOn-Page SEO:     XX\u002F100  ████████░░\nContent Quality: XX\u002F100  ██████████\nTechnical:       XX\u002F100  ███████░░░\nSchema:          XX\u002F100  █████░░░░░\nImages:          XX\u002F100  ████████░░\n```\n\n### Issues Found\nOrganized by priority: Critical -> High -> Medium -> Low\n\n### Recommendations\nSpecific, actionable improvements with expected impact\n\n### Schema Suggestions\nReady-to-use JSON-LD code for detected opportunities\n\n## DataForSEO Integration (Optional)\n\nIf DataForSEO MCP tools are available, use `serp_organic_live_advanced` for real SERP positions and `backlinks_summary` for backlink data and spam scores.\n\n## Error Handling\n\n| Scenario | Action |\n|----------|--------|\n| URL unreachable (DNS failure, connection refused) | Report the error clearly. Do not guess page content. Suggest the user verify the URL and try again. |\n| Page requires authentication (401\u002F403) | Report that the page is behind authentication. Suggest the user provide the rendered HTML directly or a publicly accessible URL. |\n| JavaScript-rendered content (empty body in HTML) | Note that key content may be rendered client-side. Analyze the available HTML and flag that results may be incomplete. Suggest using a browser-rendered snapshot if available. |\n",{"name":5,"license":14,"metadata":24,"description":28,"argument-hint":29,"user-invocable":30},{"author":25,"version":26,"category":27},"AgriciDaniel","2.3.1","seo","Deep single-page SEO analysis covering on-page elements, content quality, technical meta tags, schema, images, and performance. Use when user says \"analyze this page\", \"check page SEO\", \"single URL\", \"check this page\", \"page analysis\", or provides a single URL for review.\n","[url]",true,"main","998cbddccf9c36b4a009e502b8e00b3264d51071",".agents\u002Fskills\u002Fseo-page","https:\u002F\u002Fgithub.com\u002Fbwpahmed\u002FLifeOS","https:\u002F\u002Flife-os-wine-ten.vercel.app","https:\u002F\u002Fgithub.com\u002Fbwpahmed","2026-10-18 20:00:14",{"source":8,"skillName":5,"commands":39,"prompt":49,"zipAvailable":30},[40,43,46],{"tool":41,"command":42},"npx","npx skills add bwpahmed\u002FLifeOS --skill seo-page",{"tool":44,"command":45},"bunx","bunx skills add bwpahmed\u002FLifeOS --skill seo-page",{"tool":47,"command":48},"pnpm","pnpm dlx skills add bwpahmed\u002FLifeOS --skill seo-page","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fbwpahmed\u002FLifeOS\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fseo-page\u002FSKILL.md",[51],{"path":52,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":55,"sourceHtmlUrl":15},"LICENSE.txt","LICENSE","许可证",143,[57,64,72,79,87,95],{"skillNo":58,"name":27,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":60,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":19},"01M7CNPWGWX5D37WT9B3FK679N","Comprehensive SEO analysis for any website or business type. Full site audits, single-page analysis, technical SEO (crawlability, indexability, Core Web Vitals with INP), schema markup, content quality (E-E-A-T), image optimization, sitemap analysis, and GEO for AI Overviews\u002FChatGPT\u002FPerplexity. Industry detection for SaaS, e-commerce, local, publishers, agencies. Triggers on: SEO, audit, schema, Core Web Vitals, sitemap, E-E-A-T, AI Overviews, GEO, technical SEO, content quality, page speed.","https:\u002F\u002Fgithub.com\u002Fbwpahmed\u002FLifeOS\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fseo\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fbwpahmed\u002FLifeOS\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fseo\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":68,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M7CNPK20PRGBDPTZ3SP01473","seo-technical","Technical SEO audit across 9 categories: crawlability, indexability, security, URL structure, mobile, Core Web Vitals, structured data, JavaScript rendering, and IndexNow protocol. Use when user says \"technical SEO\", \"crawl issues\", \"robots.txt\", \"Core Web Vitals\", \"site speed\", or \"security headers\".","https:\u002F\u002Fgithub.com\u002Fbwpahmed\u002FLifeOS\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fseo-technical\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fbwpahmed\u002FLifeOS\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fseo-technical\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M7CNPC0TYTSBMNXT3DZZAQJY","seo-sxo","Search Experience Optimization: reads Google SERPs backwards to detect page-type mismatches, derives user stories from search intent signals, and scores pages from multiple persona perspectives. Identifies why well-optimized pages fail to rank by analyzing what Google rewards for each keyword. Use when user says \"SXO\", \"search experience\", \"page type mismatch\", \"SERP analysis\", \"user story\", \"persona scoring\", \"why isn't my page ranking\", \"intent mismatch\", or \"wireframe\".","https:\u002F\u002Fgithub.com\u002Fbwpahmed\u002FLifeOS\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fseo-sxo\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":83,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M7CNP6X05M85F9XS60R5WRJ4","seo-sitemap","Analyze existing XML sitemaps or generate new ones with industry templates. Validates format, URLs, and structure. Use when user says \"sitemap\", \"generate sitemap\", \"sitemap issues\", or \"XML sitemap\".","https:\u002F\u002Fgithub.com\u002Fbwpahmed\u002FLifeOS\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fseo-sitemap\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fbwpahmed\u002FLifeOS\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fseo-sitemap\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":91,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":19},"01M7CNNZ6VJSDJ0N0GXFSDAB7H","seo-schema","Detect, validate, and generate Schema.org structured data. JSON-LD format preferred. Use when user says \"schema\", \"structured data\", \"rich results\", \"JSON-LD\", or \"markup\".","https:\u002F\u002Fgithub.com\u002Fbwpahmed\u002FLifeOS\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fseo-schema\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fbwpahmed\u002FLifeOS\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fseo-schema\u002FSKILL.md",[],[],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":99,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":19},"01M7CNNS10EC7WGE463XPFKHS2","seo-programmatic","Programmatic SEO planning and analysis for pages generated at scale from data sources. Covers template engines, URL patterns, internal linking automation, thin content safeguards, and index bloat prevention. Use when user says \"programmatic SEO\", \"pages at scale\", \"dynamic pages\", \"template pages\", \"generated pages\", or \"data-driven SEO\".","https:\u002F\u002Fgithub.com\u002Fbwpahmed\u002FLifeOS\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fseo-programmatic\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fbwpahmed\u002FLifeOS\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fseo-programmatic\u002FSKILL.md",[],[]]