[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75ANDBA8RXVVBSH7E1XGJ7Y":3,"skill-same:01M75ANDBA8RXVVBSH7E1XGJ7Y":47},{"skillNo":4,"name":5,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":6,"repositoryNo":11,"starsCount":12,"licenseSpdxId":13,"licenseFileUrl":6,"sourceHtmlUrl":14,"categories":15,"keywords":16,"publishedAt":17,"linkOnly":18,"markdownContent":19,"markdownBody":20,"frontMatter":21,"refName":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":30,"ownerHtmlUrl":31,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":32,"install":33,"resources":46},"01M75ANDBA8RXVVBSH7E1XGJ7Y","seo-technical",null,"0xRayAI\u002Fxray","0xRayAI","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F274879952?v=4","01M75AEEVWK4S4G4N25HAYGB9V","01M75AEEWMHN7H4PQVCJS2938J",2,"MIT","https:\u002F\u002Fgithub.com\u002F0xRayAI\u002Fxray\u002Fblob\u002Fmain\u002Fdocs\u002Farchive\u002Fintegrations-costume\u002Fclaude-seo\u002Fseo-technical\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: seo-technical\nsource: claude-seo\nattribution: |\n  Originally from https:\u002F\u002Fgithub.com\u002FAgriciDaniel\u002Fclaude-seo\n  License: MIT (see LICENSE.claude-seo)\nconverted: 2026-03-09T07:40:29.997Z\nframework: 0xRay v1.7.5\n---\n\n---\nname: seo-technical\ndescription: >\n  Technical SEO audit across 8 categories: crawlability, indexability, security,\n  URL structure, mobile, Core Web Vitals, structured data, and JavaScript\n  rendering. Use when user says \"technical SEO\", \"crawl issues\", \"robots.txt\",\n  \"Core Web Vitals\", \"site speed\", or \"security headers\".\n---\n\n# Technical SEO Audit\n\n## Categories\n\n### 1. Crawlability\n- robots.txt: exists, valid, not blocking important resources\n- XML sitemap: exists, referenced in robots.txt, valid format\n- Noindex tags: intentional vs accidental\n- Crawl depth: important pages within 3 clicks of homepage\n- JavaScript rendering: check if critical content requires JS execution\n- Crawl budget: for large sites (>10k pages), efficiency matters\n\n#### AI Crawler Management\n\nAs of 2025-2026, AI companies actively crawl the web to train models and power AI search. Managing these crawlers via robots.txt is a critical technical SEO consideration.\n\n**Known AI crawlers:**\n\n| Crawler | Company | robots.txt token | Purpose |\n|---------|---------|-----------------|---------|\n| GPTBot | OpenAI | `GPTBot` | Model training |\n| ChatGPT-User | OpenAI | `ChatGPT-User` | Real-time browsing |\n| ClaudeBot | Anthropic | `ClaudeBot` | Model training |\n| PerplexityBot | Perplexity | `PerplexityBot` | Search index + training |\n| Bytespider | ByteDance | `Bytespider` | Model training |\n| Google-Extended | Google | `Google-Extended` | Gemini training (NOT search) |\n| CCBot | Common Crawl | `CCBot` | Open dataset |\n\n**Key distinctions:**\n- Blocking `Google-Extended` prevents Gemini training use but does NOT affect Google Search indexing or AI Overviews (those use `Googlebot`)\n- Blocking `GPTBot` prevents OpenAI training but does NOT prevent ChatGPT from citing your content via browsing (`ChatGPT-User`)\n- ~3-5% of websites now use AI-specific robots.txt rules\n\n**Example — selective AI crawler blocking:**\n```\n# Allow search indexing, block AI training crawlers\nUser-agent: GPTBot\nDisallow: \u002F\n\nUser-agent: Google-Extended\nDisallow: \u002F\n\nUser-agent: Bytespider\nDisallow: \u002F\n\n# Allow all other crawlers (including Googlebot for search)\nUser-agent: *\nAllow: \u002F\n```\n\n**Recommendation:** Consider your AI visibility strategy before blocking. Being cited by AI systems drives brand awareness and referral traffic. Cross-reference the `seo-geo` skill for full AI visibility optimization.\n\n### 2. Indexability\n- Canonical tags: self-referencing, no conflicts with noindex\n- Duplicate content: near-duplicates, parameter URLs, www vs non-www\n- Thin content: pages below minimum word counts per type\n- Pagination: rel=next\u002Fprev or load-more pattern\n- Hreflang: correct for multi-language\u002Fmulti-region sites\n- Index bloat: unnecessary pages consuming crawl budget\n\n### 3. Security\n- HTTPS: enforced, valid SSL certificate, no mixed content\n- Security headers:\n  - Content-Security-Policy (CSP)\n  - Strict-Transport-Security (HSTS)\n  - X-Frame-Options\n  - X-Content-Type-Options\n  - Referrer-Policy\n- HSTS preload: check preload list inclusion for high-security sites\n\n### 4. URL Structure\n- Clean URLs: descriptive, hyphenated, no query parameters for content\n- Hierarchy: logical folder structure reflecting site architecture\n- Redirects: no chains (max 1 hop), 301 for permanent moves\n- URL length: flag >100 characters\n- Trailing slashes: consistent usage\n\n### 5. Mobile Optimization\n- Responsive design: viewport meta tag, responsive CSS\n- Touch targets: minimum 48x48px with 8px spacing\n- Font size: minimum 16px base\n- No horizontal scroll\n- Mobile-first indexing: Google indexes mobile version. **Mobile-first indexing is 100% complete as of July 5, 2024.** Google now crawls and indexes ALL websites exclusively with the mobile Googlebot user-agent.\n\n### 6. Core Web Vitals\n- **LCP** (Largest Contentful Paint): target \u003C2.5s\n- **INP** (Interaction to Next Paint): target \u003C200ms\n  - INP replaced FID on March 12, 2024. FID was fully removed from all Chrome tools (CrUX API, PageSpeed Insights, Lighthouse) on September 9, 2024. Do NOT reference FID anywhere.\n- **CLS** (Cumulative Layout Shift): target \u003C0.1\n- Evaluation uses 75th percentile of real user data\n- Use PageSpeed Insights API or CrUX data if MCP available\n\n### 7. Structured Data\n- Detection: JSON-LD (preferred), Microdata, RDFa\n- Validation against Google's supported types\n- See seo-schema skill for full analysis\n\n### 8. JavaScript Rendering\n- Check if content visible in initial HTML vs requires JS\n- Identify client-side rendered (CSR) vs server-side rendered (SSR)\n- Flag SPA frameworks (React, Vue, Angular) that may cause indexing issues\n- Verify dynamic rendering setup if applicable\n\n#### JavaScript SEO — Canonical & Indexing Guidance (December 2025)\n\nGoogle updated its JavaScript SEO documentation in December 2025 with critical clarifications:\n\n1. **Canonical conflicts:** If a canonical tag in raw HTML differs from one injected by JavaScript, Google may use EITHER one. Ensure canonical tags are identical between server-rendered HTML and JS-rendered output.\n2. **noindex with JavaScript:** If raw HTML contains `\u003Cmeta name=\"robots\" content=\"noindex\">` but JavaScript removes it, Google MAY still honor the noindex from raw HTML. Serve correct robots directives in the initial HTML response.\n3. **Non-200 status codes:** Google does NOT render JavaScript on pages returning non-200 HTTP status codes. Any content or meta tags injected via JS on error pages will be invisible to Googlebot.\n4. **Structured data in JavaScript:** Product, Article, and other structured data injected via JS may face delayed processing. For time-sensitive structured data (especially e-commerce Product markup), include it in the initial server-rendered HTML.\n\n**Best practice:** Serve critical SEO elements (canonical, meta robots, structured data, title, meta description) in the initial server-rendered HTML rather than relying on JavaScript injection.\n\n### 9. IndexNow Protocol\n- Check if site supports IndexNow for Bing, Yandex, Naver\n- Supported by search engines other than Google\n- Recommend implementation for faster indexing on non-Google engines\n\n## Output\n\n### Technical Score: XX\u002F100\n\n### Category Breakdown\n| Category | Status | Score |\n|----------|--------|-------|\n| Crawlability | ✅\u002F⚠️\u002F❌ | XX\u002F100 |\n| Indexability | ✅\u002F⚠️\u002F❌ | XX\u002F100 |\n| Security | ✅\u002F⚠️\u002F❌ | XX\u002F100 |\n| URL Structure | ✅\u002F⚠️\u002F❌ | XX\u002F100 |\n| Mobile | ✅\u002F⚠️\u002F❌ | XX\u002F100 |\n| Core Web Vitals | ✅\u002F⚠️\u002F❌ | XX\u002F100 |\n| Structured Data | ✅\u002F⚠️\u002F❌ | XX\u002F100 |\n| JS Rendering | ✅\u002F⚠️\u002F❌ | XX\u002F100 |\n\n### Critical Issues (fix immediately)\n### High Priority (fix within 1 week)\n### Medium Priority (fix within 1 month)\n### Low Priority (backlog)\n\n## DataForSEO Integration (Optional)\n\nIf DataForSEO MCP tools are available, use `on_page_instant_pages` for real page analysis (status codes, page timing, broken links, on-page checks), `on_page_lighthouse` for Lighthouse audits (performance, accessibility, SEO scores), and `domain_analytics_technologies_domain_technologies` for technology stack detection.\n\n\n---\n\n*This skill was integrated into 0xRay via the claude-seo integration script.*\n*Original source: https:\u002F\u002Fgithub.com\u002FAgriciDaniel\u002Fclaude-seo*\n","---\nname: seo-technical\ndescription: >\n  Technical SEO audit across 8 categories: crawlability, indexability, security,\n  URL structure, mobile, Core Web Vitals, structured data, and JavaScript\n  rendering. Use when user says \"technical SEO\", \"crawl issues\", \"robots.txt\",\n  \"Core Web Vitals\", \"site speed\", or \"security headers\".\n---\n\n# Technical SEO Audit\n\n## Categories\n\n### 1. Crawlability\n- robots.txt: exists, valid, not blocking important resources\n- XML sitemap: exists, referenced in robots.txt, valid format\n- Noindex tags: intentional vs accidental\n- Crawl depth: important pages within 3 clicks of homepage\n- JavaScript rendering: check if critical content requires JS execution\n- Crawl budget: for large sites (>10k pages), efficiency matters\n\n#### AI Crawler Management\n\nAs of 2025-2026, AI companies actively crawl the web to train models and power AI search. Managing these crawlers via robots.txt is a critical technical SEO consideration.\n\n**Known AI crawlers:**\n\n| Crawler | Company | robots.txt token | Purpose |\n|---------|---------|-----------------|---------|\n| GPTBot | OpenAI | `GPTBot` | Model training |\n| ChatGPT-User | OpenAI | `ChatGPT-User` | Real-time browsing |\n| ClaudeBot | Anthropic | `ClaudeBot` | Model training |\n| PerplexityBot | Perplexity | `PerplexityBot` | Search index + training |\n| Bytespider | ByteDance | `Bytespider` | Model training |\n| Google-Extended | Google | `Google-Extended` | Gemini training (NOT search) |\n| CCBot | Common Crawl | `CCBot` | Open dataset |\n\n**Key distinctions:**\n- Blocking `Google-Extended` prevents Gemini training use but does NOT affect Google Search indexing or AI Overviews (those use `Googlebot`)\n- Blocking `GPTBot` prevents OpenAI training but does NOT prevent ChatGPT from citing your content via browsing (`ChatGPT-User`)\n- ~3-5% of websites now use AI-specific robots.txt rules\n\n**Example — selective AI crawler blocking:**\n```\n# Allow search indexing, block AI training crawlers\nUser-agent: GPTBot\nDisallow: \u002F\n\nUser-agent: Google-Extended\nDisallow: \u002F\n\nUser-agent: Bytespider\nDisallow: \u002F\n\n# Allow all other crawlers (including Googlebot for search)\nUser-agent: *\nAllow: \u002F\n```\n\n**Recommendation:** Consider your AI visibility strategy before blocking. Being cited by AI systems drives brand awareness and referral traffic. Cross-reference the `seo-geo` skill for full AI visibility optimization.\n\n### 2. Indexability\n- Canonical tags: self-referencing, no conflicts with noindex\n- Duplicate content: near-duplicates, parameter URLs, www vs non-www\n- Thin content: pages below minimum word counts per type\n- Pagination: rel=next\u002Fprev or load-more pattern\n- Hreflang: correct for multi-language\u002Fmulti-region sites\n- Index bloat: unnecessary pages consuming crawl budget\n\n### 3. Security\n- HTTPS: enforced, valid SSL certificate, no mixed content\n- Security headers:\n  - Content-Security-Policy (CSP)\n  - Strict-Transport-Security (HSTS)\n  - X-Frame-Options\n  - X-Content-Type-Options\n  - Referrer-Policy\n- HSTS preload: check preload list inclusion for high-security sites\n\n### 4. URL Structure\n- Clean URLs: descriptive, hyphenated, no query parameters for content\n- Hierarchy: logical folder structure reflecting site architecture\n- Redirects: no chains (max 1 hop), 301 for permanent moves\n- URL length: flag >100 characters\n- Trailing slashes: consistent usage\n\n### 5. Mobile Optimization\n- Responsive design: viewport meta tag, responsive CSS\n- Touch targets: minimum 48x48px with 8px spacing\n- Font size: minimum 16px base\n- No horizontal scroll\n- Mobile-first indexing: Google indexes mobile version. **Mobile-first indexing is 100% complete as of July 5, 2024.** Google now crawls and indexes ALL websites exclusively with the mobile Googlebot user-agent.\n\n### 6. Core Web Vitals\n- **LCP** (Largest Contentful Paint): target \u003C2.5s\n- **INP** (Interaction to Next Paint): target \u003C200ms\n  - INP replaced FID on March 12, 2024. FID was fully removed from all Chrome tools (CrUX API, PageSpeed Insights, Lighthouse) on September 9, 2024. Do NOT reference FID anywhere.\n- **CLS** (Cumulative Layout Shift): target \u003C0.1\n- Evaluation uses 75th percentile of real user data\n- Use PageSpeed Insights API or CrUX data if MCP available\n\n### 7. Structured Data\n- Detection: JSON-LD (preferred), Microdata, RDFa\n- Validation against Google's supported types\n- See seo-schema skill for full analysis\n\n### 8. JavaScript Rendering\n- Check if content visible in initial HTML vs requires JS\n- Identify client-side rendered (CSR) vs server-side rendered (SSR)\n- Flag SPA frameworks (React, Vue, Angular) that may cause indexing issues\n- Verify dynamic rendering setup if applicable\n\n#### JavaScript SEO — Canonical & Indexing Guidance (December 2025)\n\nGoogle updated its JavaScript SEO documentation in December 2025 with critical clarifications:\n\n1. **Canonical conflicts:** If a canonical tag in raw HTML differs from one injected by JavaScript, Google may use EITHER one. Ensure canonical tags are identical between server-rendered HTML and JS-rendered output.\n2. **noindex with JavaScript:** If raw HTML contains `\u003Cmeta name=\"robots\" content=\"noindex\">` but JavaScript removes it, Google MAY still honor the noindex from raw HTML. Serve correct robots directives in the initial HTML response.\n3. **Non-200 status codes:** Google does NOT render JavaScript on pages returning non-200 HTTP status codes. Any content or meta tags injected via JS on error pages will be invisible to Googlebot.\n4. **Structured data in JavaScript:** Product, Article, and other structured data injected via JS may face delayed processing. For time-sensitive structured data (especially e-commerce Product markup), include it in the initial server-rendered HTML.\n\n**Best practice:** Serve critical SEO elements (canonical, meta robots, structured data, title, meta description) in the initial server-rendered HTML rather than relying on JavaScript injection.\n\n### 9. IndexNow Protocol\n- Check if site supports IndexNow for Bing, Yandex, Naver\n- Supported by search engines other than Google\n- Recommend implementation for faster indexing on non-Google engines\n\n## Output\n\n### Technical Score: XX\u002F100\n\n### Category Breakdown\n| Category | Status | Score |\n|----------|--------|-------|\n| Crawlability | ✅\u002F⚠️\u002F❌ | XX\u002F100 |\n| Indexability | ✅\u002F⚠️\u002F❌ | XX\u002F100 |\n| Security | ✅\u002F⚠️\u002F❌ | XX\u002F100 |\n| URL Structure | ✅\u002F⚠️\u002F❌ | XX\u002F100 |\n| Mobile | ✅\u002F⚠️\u002F❌ | XX\u002F100 |\n| Core Web Vitals | ✅\u002F⚠️\u002F❌ | XX\u002F100 |\n| Structured Data | ✅\u002F⚠️\u002F❌ | XX\u002F100 |\n| JS Rendering | ✅\u002F⚠️\u002F❌ | XX\u002F100 |\n\n### Critical Issues (fix immediately)\n### High Priority (fix within 1 week)\n### Medium Priority (fix within 1 month)\n### Low Priority (backlog)\n\n## DataForSEO Integration (Optional)\n\nIf DataForSEO MCP tools are available, use `on_page_instant_pages` for real page analysis (status codes, page timing, broken links, on-page checks), `on_page_lighthouse` for Lighthouse audits (performance, accessibility, SEO scores), and `domain_analytics_technologies_domain_technologies` for technology stack detection.\n\n\n---\n\n*This skill was integrated into 0xRay via the claude-seo integration script.*\n*Original source: https:\u002F\u002Fgithub.com\u002FAgriciDaniel\u002Fclaude-seo*\n",{"name":5,"source":22,"converted":23,"framework":24,"attribution":25},"claude-seo",1773042029997,"0xRay v1.7.5","Originally from https:\u002F\u002Fgithub.com\u002FAgriciDaniel\u002Fclaude-seo\nLicense: MIT (see LICENSE.claude-seo)\n","main","232f39ec089591afb70f9327b481e7428162a97e","docs\u002Farchive\u002Fintegrations-costume\u002Fclaude-seo\u002Fseo-technical",3,"https:\u002F\u002Fgithub.com\u002F0xRayAI\u002Fxray","https:\u002F\u002Fgithub.com\u002F0xRayAI","2026-11-13 22:20:55",{"source":7,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add 0xRayAI\u002Fxray --skill seo-technical",{"tool":39,"command":40},"bunx","bunx skills add 0xRayAI\u002Fxray --skill seo-technical",{"tool":42,"command":43},"pnpm","pnpm dlx skills add 0xRayAI\u002Fxray --skill seo-technical","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002F0xRayAI\u002Fxray\u002Fblob\u002Fmain\u002Fdocs\u002Farchive\u002Fintegrations-costume\u002Fclaude-seo\u002Fseo-technical\u002FSKILL.md",true,[],[48,55,62,69,76,83],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":6,"repositoryNo":11,"starsCount":12,"licenseSpdxId":13,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":17},"01M75AXZY4TX8Z6WF2G4EKYMAA","xray-orchestrator","Main orchestration skill for xray agents.\nProvides commands to coordinate agent work and invoke xray APIs\nthrough the local HTTP API server.","https:\u002F\u002Fgithub.com\u002F0xRayAI\u002Fxray\u002Fblob\u002Fmain\u002Fsrc\u002Fskills\u002Fxray-orchestrator\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":6,"repositoryNo":11,"starsCount":12,"licenseSpdxId":13,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":17},"01M75AXT1TB9SX9JVSP16C85BP","ui-ux-design","User interface and user experience design with mobile-first approach, cognitive simplicity, and accessibility-first principles","https:\u002F\u002Fgithub.com\u002F0xRayAI\u002Fxray\u002Fblob\u002Fmain\u002Fsrc\u002Fskills\u002Fui-ux-design\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":6,"repositoryNo":11,"starsCount":12,"licenseSpdxId":13,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":17},"01M75AXQERT17BTCCY7Y1HPXTA","testing-strategy","Design comprehensive testing strategies and optimize test coverage","https:\u002F\u002Fgithub.com\u002F0xRayAI\u002Fxray\u002Fblob\u002Fmain\u002Fsrc\u002Fskills\u002Ftesting-strategy\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":6,"repositoryNo":11,"starsCount":12,"licenseSpdxId":13,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":17},"01M75AXM7TRVQXXKT0C287VWN7","testing-best-practices","Testing best practices and quality assurance","https:\u002F\u002Fgithub.com\u002F0xRayAI\u002Fxray\u002Fblob\u002Fmain\u002Fsrc\u002Fskills\u002Ftesting-best-practices\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":6,"repositoryNo":11,"starsCount":12,"licenseSpdxId":13,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":17},"01M75AXHAJZK2JBVG638K3RZ5F","tech-writer","Documentation writer for API docs, READMEs, ADRs, changelogs, and developer experience","https:\u002F\u002Fgithub.com\u002F0xRayAI\u002Fxray\u002Fblob\u002Fmain\u002Fsrc\u002Fskills\u002Ftech-writer\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":6,"repositoryNo":11,"starsCount":12,"licenseSpdxId":13,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":17},"01M75AXE7P5MX15WA16TGFKJQG","strategist","Strategic guidance and complex problem-solving with architectural decision-making and risk analysis","https:\u002F\u002Fgithub.com\u002F0xRayAI\u002Fxray\u002Fblob\u002Fmain\u002Fsrc\u002Fskills\u002Fstrategist\u002FSKILL.md",[],[]]