[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75E5XF413JNDSBKDV8M2134":3,"skill-same:01M75E5XF413JNDSBKDV8M2134":48},{"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":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":30,"ownerHtmlUrl":31,"ownerBlogUrl":32,"ownerDescription":6,"updatedAt":33,"install":34,"resources":47},"01M75E5XF413JNDSBKDV8M2134","tech-seo-audit",null,"Run technical SEO audit. Use when: checking Core Web Vitals, crawlability, indexation, speed, or structured data.","LongLeo287\u002FSEOSONA-OS","LongLeo287","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F141803367?v=4","01M6JK75C62VCNZKR5BRZ386YV","LongLeo","01M75CK60XQGYJY3YDGGFJQDYT",2,"MIT","https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FSEOSONA-OS\u002Fblob\u002Fmain\u002F2_KNOWLEDGE\u002Fframeworks\u002Fdigital-marketing-pro\u002Fskills\u002Ftech-seo-audit\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: tech-seo-audit\ndescription: \"Run technical SEO audit. Use when: checking Core Web Vitals, crawlability, indexation, speed, or structured data.\"\nargument-hint: \"[URL]\"\n---\n\n# \u002Fdigital-marketing-pro:tech-seo-audit\n\n## Purpose\n\nRun a comprehensive technical SEO audit that covers the infrastructure and code-level factors that affect search engine crawling, indexation, and ranking. This audit focuses on the technical foundation rather than content or backlinks. Produces a prioritized report with specific fixes, expected impact, and implementation guidance.\n\n### Important — technical SEO during the May 2026 Core Update\n\n> **Time-boxed guidance — valid until ~2026-08.** This block is specific to the May 2026 Core Update window. After ~August 2026 it is stale: re-check the [Google Search Status Dashboard](https:\u002F\u002Fstatus.search.google.com\u002F) for the current\u002Fmost-recent core update and its dates before applying the timing advice below.\n\nThe Google **broad core update that started 21 May 2026** is primarily a quality\u002Frelevance reweighting, not a technical signal change. If a brand contacts you about ranking volatility in May\u002FJune 2026:\n\n- **Run this audit anyway** — Core Updates frequently surface pre-existing technical debt because relative quality matters more during reweighting. Crawl-budget waste on low-quality pages, broken canonical chains, soft-404s, and orphaned JS-rendered routes all amplify Core Update damage.\n- **Resist crawler\u002Frendering \"fixes\" pitched as Core Update remedies.** No technical change will undo a Core Update hit if the underlying content quality issue isn't addressed. Pair this audit with `\u002Fdigital-marketing-pro:seo-audit` (content\u002FE-E-A-T side) — both are needed.\n- **Hreflang, structured data, and Core Web Vitals carry their normal weight** — the update did not change technical priorities, only how much E-E-A-T deficits hurt.\n\n## Input Required\n\nThe user must provide (or will be prompted for):\n\n- **Website URL** (required): The domain or specific section to audit\n- **CMS\u002FPlatform** (helpful): WordPress, Shopify, Next.js, custom, etc.\n- **Known issues** (optional): Any specific technical concerns\n- **Site size** (helpful): Approximate number of pages\n- **International presence** (optional): Whether site serves multiple countries\u002Flanguages\n- **Access to Google Search Console data** (optional): Enables real data vs estimates\n\n## Process\n\n1. **Load brand context**: Read `~\u002F.claude-marketing\u002Fbrands\u002F_active-brand.json` for the active slug, then load `~\u002F.claude-marketing\u002Fbrands\u002F{slug}\u002Fprofile.json`. Apply brand voice, compliance rules for target markets (`skills\u002Fcontext-engine\u002Fcompliance-rules.md`), and industry context. **Also check for guidelines** at `~\u002F.claude-marketing\u002Fbrands\u002F{slug}\u002Fguidelines\u002F_manifest.json` — if present, load restrictions and relevant category files. Check for custom templates at `~\u002F.claude-marketing\u002Fbrands\u002F{slug}\u002Ftemplates\u002F`. Check for agency SOPs at `~\u002F.claude-marketing\u002Fsops\u002F`. If no brand exists, ask: \"Set up a brand first (\u002Fdigital-marketing-pro:brand-setup)?\" — or proceed with defaults.\n2. **Load reference files**: Read `skills\u002Ftechnical-seo\u002Fcore-web-vitals.md`, `skills\u002Ftechnical-seo\u002Fcrawlability.md`, `skills\u002Ftechnical-seo\u002Fsite-architecture.md`, `skills\u002Ftechnical-seo\u002Findexation.md`, and `skills\u002Ftechnical-seo\u002Finternational-seo.md` for detailed technical SEO frameworks\n3. **Run tech-seo-auditor script** (if Python available): `python \"${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Ftech-seo-auditor.py\" --url {url}` to get automated checks on status codes, redirects, meta tags, and page structure\n4. **Core Web Vitals assessment**: Evaluate LCP, INP, and CLS using known thresholds. If GSC MCP is connected, pull real CrUX data. Otherwise, provide optimization checklist based on CMS\u002Fplatform\n5. **Crawlability audit**: Check robots.txt configuration, XML sitemap presence and structure, crawl budget considerations, JavaScript rendering impact\n6. **Indexation review**: Canonical tag usage, meta robots directives, duplicate content risks, index bloat potential, pagination handling\n7. **Site architecture analysis**: URL structure, internal linking patterns, site depth, navigation efficiency, breadcrumbs\n8. **Page speed optimization**: Image optimization, render-blocking resources, compression, caching, CDN usage\n9. **Mobile-first compliance**: Viewport configuration, responsive design, mobile usability, touch targets\n10. **Redirect health check**: Redirect chain detection, mixed HTTP\u002FHTTPS, trailing slash consistency\n11. **Structured data review**: Schema markup presence, validation, completeness, opportunity identification\n12. **International SEO** (if applicable): Hreflang implementation, language targeting, URL structure\n13. **Security check**: HTTPS enforcement, HSTS, mixed content\n14. Compile prioritized report: Group findings by severity (Critical \u002F High \u002F Medium \u002F Low), include specific fix instructions, estimated effort, and expected impact for each issue\n\n## Output\n\nA structured technical SEO audit report containing:\n\n- **Audit header**: Brand name, URL, date, CMS\u002Fplatform, overall health score (0-100)\n- **Executive summary**: 3-5 sentence overview of technical health\n- **Critical issues** (fix immediately): Issues blocking crawling, indexation, or causing significant ranking impact\n- **High priority** (fix this week): Issues with measurable ranking or UX impact\n- **Medium priority** (fix this month): Optimization opportunities with moderate impact\n- **Low priority** (backlog): Minor improvements and best-practice alignment\n- **Each finding includes**: Description, affected URLs\u002Fpages, specific fix with code\u002Fconfig examples, estimated effort (hours), expected impact (traffic\u002Franking)\n- **Core Web Vitals scorecard**: LCP, INP, CLS with current estimates and target values\n- **Quick wins list**: Top 5 highest-impact, lowest-effort fixes\n- **Implementation roadmap**: Suggested timeline for addressing all findings\n\n## Tips & caveats\n\n- **Core Web Vitals from synthetic tests (Lighthouse, PageSpeed Insights) often disagree with field data (CrUX, GSC).** Field data is what Google ranks against. If lab says PASS but field says FAIL, trust field.\n- **JavaScript rendering is the #1 silent killer** of indexation on modern sites. Always check whether the rendered HTML (post-JS) matches the source HTML at critical content. Use `view-source:` vs DevTools.\n- **Don't fix what isn't broken.** A site at 95th-percentile CWV doesn't need re-engineering — that effort is better spent on content. Tech-SEO is necessary, not sufficient.\n- **Robots.txt + meta robots conflicts** are common. If both fire, Google obeys the most restrictive. Always cross-check.\n- **For a Core Update window,** run this audit anyway — Core Updates often surface pre-existing tech debt, but the fixes are background work, not Core Update remedies.\n- **Link-profile work is out of scope for this technical audit.** This audit covers own-domain *technical* health (crawlability, indexation, redirects, canonicals, CWV, schema) — not backlinks. For own-domain link health see `\u002Fdigital-marketing-pro:seo-audit`; for competitor link-gap analysis hand off to `\u002Fdigital-marketing-pro:backlink-gap`.\n\n## Agents Used\n\n- **seo-specialist** — Runs the technical audit across all dimensions, generates structured data recommendations, provides CMS-specific fix guidance, prioritizes findings by impact\u002Feffort\n","# \u002Fdigital-marketing-pro:tech-seo-audit\n\n## Purpose\n\nRun a comprehensive technical SEO audit that covers the infrastructure and code-level factors that affect search engine crawling, indexation, and ranking. This audit focuses on the technical foundation rather than content or backlinks. Produces a prioritized report with specific fixes, expected impact, and implementation guidance.\n\n### Important — technical SEO during the May 2026 Core Update\n\n> **Time-boxed guidance — valid until ~2026-08.** This block is specific to the May 2026 Core Update window. After ~August 2026 it is stale: re-check the [Google Search Status Dashboard](https:\u002F\u002Fstatus.search.google.com\u002F) for the current\u002Fmost-recent core update and its dates before applying the timing advice below.\n\nThe Google **broad core update that started 21 May 2026** is primarily a quality\u002Frelevance reweighting, not a technical signal change. If a brand contacts you about ranking volatility in May\u002FJune 2026:\n\n- **Run this audit anyway** — Core Updates frequently surface pre-existing technical debt because relative quality matters more during reweighting. Crawl-budget waste on low-quality pages, broken canonical chains, soft-404s, and orphaned JS-rendered routes all amplify Core Update damage.\n- **Resist crawler\u002Frendering \"fixes\" pitched as Core Update remedies.** No technical change will undo a Core Update hit if the underlying content quality issue isn't addressed. Pair this audit with `\u002Fdigital-marketing-pro:seo-audit` (content\u002FE-E-A-T side) — both are needed.\n- **Hreflang, structured data, and Core Web Vitals carry their normal weight** — the update did not change technical priorities, only how much E-E-A-T deficits hurt.\n\n## Input Required\n\nThe user must provide (or will be prompted for):\n\n- **Website URL** (required): The domain or specific section to audit\n- **CMS\u002FPlatform** (helpful): WordPress, Shopify, Next.js, custom, etc.\n- **Known issues** (optional): Any specific technical concerns\n- **Site size** (helpful): Approximate number of pages\n- **International presence** (optional): Whether site serves multiple countries\u002Flanguages\n- **Access to Google Search Console data** (optional): Enables real data vs estimates\n\n## Process\n\n1. **Load brand context**: Read `~\u002F.claude-marketing\u002Fbrands\u002F_active-brand.json` for the active slug, then load `~\u002F.claude-marketing\u002Fbrands\u002F{slug}\u002Fprofile.json`. Apply brand voice, compliance rules for target markets (`skills\u002Fcontext-engine\u002Fcompliance-rules.md`), and industry context. **Also check for guidelines** at `~\u002F.claude-marketing\u002Fbrands\u002F{slug}\u002Fguidelines\u002F_manifest.json` — if present, load restrictions and relevant category files. Check for custom templates at `~\u002F.claude-marketing\u002Fbrands\u002F{slug}\u002Ftemplates\u002F`. Check for agency SOPs at `~\u002F.claude-marketing\u002Fsops\u002F`. If no brand exists, ask: \"Set up a brand first (\u002Fdigital-marketing-pro:brand-setup)?\" — or proceed with defaults.\n2. **Load reference files**: Read `skills\u002Ftechnical-seo\u002Fcore-web-vitals.md`, `skills\u002Ftechnical-seo\u002Fcrawlability.md`, `skills\u002Ftechnical-seo\u002Fsite-architecture.md`, `skills\u002Ftechnical-seo\u002Findexation.md`, and `skills\u002Ftechnical-seo\u002Finternational-seo.md` for detailed technical SEO frameworks\n3. **Run tech-seo-auditor script** (if Python available): `python \"${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Ftech-seo-auditor.py\" --url {url}` to get automated checks on status codes, redirects, meta tags, and page structure\n4. **Core Web Vitals assessment**: Evaluate LCP, INP, and CLS using known thresholds. If GSC MCP is connected, pull real CrUX data. Otherwise, provide optimization checklist based on CMS\u002Fplatform\n5. **Crawlability audit**: Check robots.txt configuration, XML sitemap presence and structure, crawl budget considerations, JavaScript rendering impact\n6. **Indexation review**: Canonical tag usage, meta robots directives, duplicate content risks, index bloat potential, pagination handling\n7. **Site architecture analysis**: URL structure, internal linking patterns, site depth, navigation efficiency, breadcrumbs\n8. **Page speed optimization**: Image optimization, render-blocking resources, compression, caching, CDN usage\n9. **Mobile-first compliance**: Viewport configuration, responsive design, mobile usability, touch targets\n10. **Redirect health check**: Redirect chain detection, mixed HTTP\u002FHTTPS, trailing slash consistency\n11. **Structured data review**: Schema markup presence, validation, completeness, opportunity identification\n12. **International SEO** (if applicable): Hreflang implementation, language targeting, URL structure\n13. **Security check**: HTTPS enforcement, HSTS, mixed content\n14. Compile prioritized report: Group findings by severity (Critical \u002F High \u002F Medium \u002F Low), include specific fix instructions, estimated effort, and expected impact for each issue\n\n## Output\n\nA structured technical SEO audit report containing:\n\n- **Audit header**: Brand name, URL, date, CMS\u002Fplatform, overall health score (0-100)\n- **Executive summary**: 3-5 sentence overview of technical health\n- **Critical issues** (fix immediately): Issues blocking crawling, indexation, or causing significant ranking impact\n- **High priority** (fix this week): Issues with measurable ranking or UX impact\n- **Medium priority** (fix this month): Optimization opportunities with moderate impact\n- **Low priority** (backlog): Minor improvements and best-practice alignment\n- **Each finding includes**: Description, affected URLs\u002Fpages, specific fix with code\u002Fconfig examples, estimated effort (hours), expected impact (traffic\u002Franking)\n- **Core Web Vitals scorecard**: LCP, INP, CLS with current estimates and target values\n- **Quick wins list**: Top 5 highest-impact, lowest-effort fixes\n- **Implementation roadmap**: Suggested timeline for addressing all findings\n\n## Tips & caveats\n\n- **Core Web Vitals from synthetic tests (Lighthouse, PageSpeed Insights) often disagree with field data (CrUX, GSC).** Field data is what Google ranks against. If lab says PASS but field says FAIL, trust field.\n- **JavaScript rendering is the #1 silent killer** of indexation on modern sites. Always check whether the rendered HTML (post-JS) matches the source HTML at critical content. Use `view-source:` vs DevTools.\n- **Don't fix what isn't broken.** A site at 95th-percentile CWV doesn't need re-engineering — that effort is better spent on content. Tech-SEO is necessary, not sufficient.\n- **Robots.txt + meta robots conflicts** are common. If both fire, Google obeys the most restrictive. Always cross-check.\n- **For a Core Update window,** run this audit anyway — Core Updates often surface pre-existing tech debt, but the fixes are background work, not Core Update remedies.\n- **Link-profile work is out of scope for this technical audit.** This audit covers own-domain *technical* health (crawlability, indexation, redirects, canonicals, CWV, schema) — not backlinks. For own-domain link health see `\u002Fdigital-marketing-pro:seo-audit`; for competitor link-gap analysis hand off to `\u002Fdigital-marketing-pro:backlink-gap`.\n\n## Agents Used\n\n- **seo-specialist** — Runs the technical audit across all dimensions, generates structured data recommendations, provides CMS-specific fix guidance, prioritizes findings by impact\u002Feffort\n",{"name":5,"description":7,"argument-hint":24},"[URL]","main","4fd50b1281e8cd978866b6b4556242605cabf708","2_KNOWLEDGE\u002Fframeworks\u002Fdigital-marketing-pro\u002Fskills\u002Ftech-seo-audit",1,"https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FSEOSONA-OS","https:\u002F\u002Fseosona-os.vercel.app","https:\u002F\u002Fgithub.com\u002FLongLeo287","https:\u002F\u002Fwww.facebook.com\u002FResourceRookie2023","2026-10-09 15:14:13",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add LongLeo287\u002FSEOSONA-OS --skill tech-seo-audit",{"tool":40,"command":41},"bunx","bunx skills add LongLeo287\u002FSEOSONA-OS --skill tech-seo-audit",{"tool":43,"command":44},"pnpm","pnpm dlx skills add LongLeo287\u002FSEOSONA-OS --skill tech-seo-audit","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FSEOSONA-OS\u002Fblob\u002Fmain\u002F2_KNOWLEDGE\u002Fframeworks\u002Fdigital-marketing-pro\u002Fskills\u002Ftech-seo-audit\u002FSKILL.md",true,[],[49,56,63,70,77,84],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":19},"01M75F0T3V3W7JQQ05X26NNN2T","web_crawler_katana","High-speed web crawling using Katana patterns for deep site mapping, URL discovery, and content extraction.","https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FSEOSONA-OS\u002Fblob\u002Fmain\u002F2_KNOWLEDGE\u002Fskills\u002Fseo_technical\u002Fweb_crawler_katana\u002FSKILL.md",[],[],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M75F0Q2QJXDGAFKC7D84GT88","server_log_analyzer","Analyzes Nginx\u002FApache server logs to identify Googlebot crawl patterns, errors, and performance bottlenecks.","https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FSEOSONA-OS\u002Fblob\u002Fmain\u002F2_KNOWLEDGE\u002Fskills\u002Fseo_technical\u002Fserver_log_analyzer\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M75F0KZP6D8R8XPN2YT35BAJ","schema_markup_generator","Auto-generates JSON-LD structured data for any page type (Article, Product, FAQ, LocalBusiness, etc.).","https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FSEOSONA-OS\u002Fblob\u002Fmain\u002F2_KNOWLEDGE\u002Fskills\u002Fseo_technical\u002Fschema_markup_generator\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M75F0G3KX4Y86AXJXTKXVEVA","internal_linking_optimizer","Analyzes and optimizes the internal link graph of a website for SEO authority distribution.","https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FSEOSONA-OS\u002Fblob\u002Fmain\u002F2_KNOWLEDGE\u002Fskills\u002Fseo_technical\u002Finternal_linking_optimizer\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M75F0CS1RYX4YPJC7N6RAAQJ","google_trends_analyzer","Detects trending topics and seasonal patterns using Google Trends data for content planning and keyword strategy.","https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FSEOSONA-OS\u002Fblob\u002Fmain\u002F2_KNOWLEDGE\u002Fskills\u002Fseo_technical\u002Fgoogle_trends_analyzer\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M75F0ASMQ1GKPFX82D19SRTN","brand_context_analyzer","Tracks brand mentions, sentiment, and online reputation across web sources.","https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FSEOSONA-OS\u002Fblob\u002Fmain\u002F2_KNOWLEDGE\u002Fskills\u002Fseo_technical\u002Fbrand_context_analyzer\u002FSKILL.md",[],[]]