[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CM8938RF9V9RH59Q4HCXYH":3,"skill-same:01M7CM8938RF9V9RH59Q4HCXYH":64},{"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":16,"sourceHtmlUrl":17,"categories":18,"keywords":19,"publishedAt":20,"linkOnly":21,"markdownContent":22,"markdownBody":23,"frontMatter":24,"refName":32,"commitSha":33,"skillDirectory":34,"forksCount":35,"repositoryHtmlUrl":36,"repositoryHomepageUrl":6,"ownerHtmlUrl":37,"ownerBlogUrl":6,"ownerDescription":38,"updatedAt":39,"install":40,"resources":52},"01M7CM8938RF9V9RH59Q4HCXYH","seo-technical",null,"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\".","peterish8\u002Fprats-skill-atlas","peterish8","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F181628466?v=4","01M7CHQAPN6X8D29E2Q8DW4BYF","Prathick Dhanes R","01M7CHQAQ7T42E6D8HH3CZH342",1,"MIT","https:\u002F\u002Fgithub.com\u002Fpeterish8\u002Fprats-skill-atlas\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fresearch-data\u002Fresearch-seo-and-content\u002Fseo-technical\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fpeterish8\u002Fprats-skill-atlas\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fresearch-data\u002Fresearch-seo-and-content\u002Fseo-technical\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: seo-technical\ndescription: >\n  Technical SEO audit across 9 categories: crawlability, indexability, security,\n  URL structure, mobile, Core Web Vitals, structured data, JavaScript rendering,\n  and IndexNow protocol. Use when user says \"technical SEO\", \"crawl issues\",\n  \"robots.txt\", \"Core Web Vitals\", \"site speed\", or \"security headers\".\nuser-invocable: true\nargument-hint: \"[url]\"\nlicense: MIT\nmetadata:\n  author: AgriciDaniel\n  version: \"2.2.4\"\n  category: seo\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: run `\"$HOME\u002F.Codex\u002Fskills\u002Fseo\u002Fbin\u002FCodex-seo\" run sitemap_discovery.py \u003Curl> --json`; require a\n  valid entry in `found`, and report stale or unsafe robots.txt declarations\n  separately from working fallback locations\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- Googlebot **fetch limits**: Googlebot fetches the first **2MB of HTML** and first **64MB of a PDF** (uncompressed; 15MB is the broader crawler-infra default). Long-standing, not a 2026 change, but inline base64 images, oversized inline CSS\u002FJS, or bloated nav can push critical content\u002FJSON-LD past the cap and out of the index. Keep key content + structured data within the first 2MB.\n- Crawl rate **auto-adjusts** (backs off on 5xx\u002Fslow responses); there is **no manual crawl-rate control** (the legacy Search Console setting was removed Jan 2024). Influence crawling via sitemaps, server responsiveness, and robots controls.\n- Google's canonical crawling\u002Frobots reference moved to **developers.google.com\u002Fcrawling** (migrated 2025-11-20); IP-range files relocated to `\u002Fcrawling\u002Fipranges\u002F` and `googlebot.json` was renamed `common-crawlers.json`.\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 the full AI crawler\u002Ffetcher taxonomy.\n\n> **User-triggered fetchers ignore robots.txt by design.** Google now documents **Google-Agent** (Project Mariner, agentic browsing) plus **Google-NotebookLM** and **Google Messages** as *user-triggered* fetchers that **cannot be blocked via robots.txt**. Use server-side access controls instead. By contrast, `Google-Extended` and `Google-CloudVertexBot` obey robots.txt. Emerging: **Web Bot Auth** (RFC 9421) lets bots authenticate cryptographically via a `Signature-Agent` header + key directory at `agent.bot.goog` (used by Google-Agent); reverse-DNS verification remains the fallback.\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- **Back-button hijacking** (spam-policy violation, malicious practices): flag pages that defeat the Back button via `history.pushState`\u002F`replaceState` (including scripts injected by third-party ad\u002Flibrary platforms). Added to Google's spam policies 2026-04-13; **enforcement live since 2026-06-15** (manual actions + automated demotions): treat as Critical.\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 & Page Experience\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: Googlebot Smartphone is the primary crawler (rollout completed 2024). A mobile version is **not strictly required** (Google says \"very strongly recommended\"), sites that don't work on mobile can still be indexed, but the real risk is **content\u002Fparity loss**, not hard exclusion.\n- **Mobile\u002Fdesktop content parity** (highest-value mobile check): equivalent primary content, matching robots meta tags, matching titles\u002Fdescriptions, equivalent structured data, crawlable resources; avoid lazy-loading primary content that requires user interaction.\n- **Intrusive interstitials \u002F ad density**: flag full-page interstitials, standalone consent-redirect pages, persistent blocking dialogs, and excessive\u002Fdistracting ad density (a named page-experience aspect). Acceptable: small banners, standard CMS\u002Flegal dialogs.\n- **\"Read more\" deep links**: keep key content **immediately visible on load** (not behind tabs\u002Faccordions), don't hijack scroll on load, and preserve URL hash fragments, content hidden behind expandable sections is less likely to qualify.\n\n> **Page experience is guidance, not a single ranking system.** Only **Core Web Vitals** feeds ranking directly; **HTTPS** is a confirmed but lightweight signal (affects \u003C~1% of queries). Relevance can still win even when page experience is sub-par, so don't over-weight security headers. Note: the standalone **Page Experience report was removed** from Search Console (monitor via the Core Web Vitals + HTTPS reports).\n\n### 6. Core Web Vitals\n- **LCP** (Largest Contentful Paint): target \u003C=2.5s\n- **INP** (Interaction to Next Paint): target \u003C=200ms\n  - INP replaced FID on March 12, 2024. FID was removed from Chrome's field-data tools (CrUX API, PageSpeed Insights) on September 9, 2024 (Lighthouse is a lab tool that never reported FID). Do NOT reference FID anywhere.\n- **CLS** (Cumulative Layout Shift): target \u003C=0.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## Agent-Friendly Pages & Agentic Browsing\n\nAI agents (not just AI summarizers) increasingly read sites through three\nchannels: vision models on screenshots, raw HTML\u002FDOM, and the **accessibility\ntree** (the cleanest signal). Audit criteria: semantic HTML (real `\u003Cbutton>`\nand `\u003Ca>`, not `\u003Cdiv onclick>`), label associations, interactive target sizing,\nlayout stability across templates, `cursor: pointer` correctness, live in\n`references\u002Fagent-friendly-pages.md`.\n\nGoogle now ships a Lighthouse **Agentic Browsing** category (default-on since\nLighthouse 13.3.0, Chrome 150+; buckets: agent-centric accessibility, CLS +\nllms.txt, three WebMCP audits). It reports a **fractional pass-ratio (X of N),\nnot a 0-100 score**, keep that distinct from this skill's own Agent-UX 0-100\nheuristic below. The PSI REST API does not expose it; run via Lighthouse CLI\n`--only-categories=agentic-browsing`, DevTools, or the PSI web UI. See\n`references\u002Fagent-friendly-pages.md`.\n\n### Audit command\n\n```bash\n# Render with Playwright + capture accessibility tree, then score\n\"$HOME\u002F.Codex\u002Fskills\u002Fseo\u002Fbin\u002FCodex-seo\" run agent_ux_check.py https:\u002F\u002Fexample.com --json\n```\n\nThe scanner outputs an Agent-UX score (0-100) plus itemized issues:\n- HTML findings: real buttons \u002F anchors, `\u003Cdiv onclick>` widgets, semantic\n  landmarks, inputs without `\u003Clabel for>`, inputs without ARIA labels\n- Accessibility tree findings: total nodes, interactive nodes, unnamed\n  interactive elements, `role=\"generic\"` ratio\n\nThe accessibility-tree snapshot uses Playwright's\n`page.accessibility.snapshot(interesting_only=False)`. To capture the tree\nwithout scoring, use `\"$HOME\u002F.Codex\u002Fskills\u002Fseo\u002Fbin\u002FCodex-seo\" run render_page.py \u003Curl> --a11y-tree --json`.\n\nSurface findings as **opportunities**, not failures; don't gate audits on a\nsub-100 Agent-UX score. WebMCP origin-trial\u002Fsign-up status needs verification,\nand absence of WebMCP support is still an opportunity, not a defect.\n\n## Output\n\n### Technical Score: XX\u002F100\n\n### Category Breakdown\n| Category | Status | Score |\n|----------|--------|-------|\n| Crawlability | pass\u002Fwarn\u002Ffail | XX\u002F100 |\n| Indexability | pass\u002Fwarn\u002Ffail | XX\u002F100 |\n| Security | pass\u002Fwarn\u002Ffail | XX\u002F100 |\n| URL Structure | pass\u002Fwarn\u002Ffail | XX\u002F100 |\n| Mobile | pass\u002Fwarn\u002Ffail | XX\u002F100 |\n| Core Web Vitals | pass\u002Fwarn\u002Ffail | XX\u002F100 |\n| Structured Data | pass\u002Fwarn\u002Ffail | XX\u002F100 |\n| JS Rendering | pass\u002Fwarn\u002Ffail | XX\u002F100 |\n| IndexNow | pass\u002Fwarn\u002Ffail | 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## Google API Integration (Optional)\n\nIf Google API credentials are configured, use `\"$HOME\u002F.Codex\u002Fskills\u002Fseo\u002Fbin\u002FCodex-seo\" run pagespeed_check.py \u003Curl> --json` for real PSI + CrUX field data (replaces lab-only CWV estimates), `\"$HOME\u002F.Codex\u002Fskills\u002Fseo\u002Fbin\u002FCodex-seo\" run crux_history.py \u003Curl> --json` for 25-week CWV trends, and `\"$HOME\u002F.Codex\u002Fskills\u002Fseo\u002Fbin\u002FCodex-seo\" run gsc_inspect.py \u003Curl> --json` for real indexation status per URL.\n\n## Error Handling\n\n| Scenario | Action |\n|----------|--------|\n| URL unreachable | Report connection error with status code. Suggest verifying URL, checking DNS resolution, and confirming the site is publicly accessible. |\n| robots.txt not found | Note that no robots.txt was detected at the root domain. Recommend creating one with appropriate directives. Continue audit on remaining categories. |\n| HTTPS not configured | Flag as a critical issue. Report whether HTTP is served without redirect, mixed content exists, or SSL certificate is missing\u002Fexpired. |\n| Core Web Vitals data unavailable | Note that CrUX data is not available (common for low-traffic sites). Suggest using Lighthouse lab data as a proxy and recommend increasing traffic before re-testing. |\n","# Technical SEO Audit\n\n## Categories\n\n### 1. Crawlability\n- robots.txt: exists, valid, not blocking important resources\n- XML sitemap: run `\"$HOME\u002F.Codex\u002Fskills\u002Fseo\u002Fbin\u002FCodex-seo\" run sitemap_discovery.py \u003Curl> --json`; require a\n  valid entry in `found`, and report stale or unsafe robots.txt declarations\n  separately from working fallback locations\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- Googlebot **fetch limits**: Googlebot fetches the first **2MB of HTML** and first **64MB of a PDF** (uncompressed; 15MB is the broader crawler-infra default). Long-standing, not a 2026 change, but inline base64 images, oversized inline CSS\u002FJS, or bloated nav can push critical content\u002FJSON-LD past the cap and out of the index. Keep key content + structured data within the first 2MB.\n- Crawl rate **auto-adjusts** (backs off on 5xx\u002Fslow responses); there is **no manual crawl-rate control** (the legacy Search Console setting was removed Jan 2024). Influence crawling via sitemaps, server responsiveness, and robots controls.\n- Google's canonical crawling\u002Frobots reference moved to **developers.google.com\u002Fcrawling** (migrated 2025-11-20); IP-range files relocated to `\u002Fcrawling\u002Fipranges\u002F` and `googlebot.json` was renamed `common-crawlers.json`.\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 the full AI crawler\u002Ffetcher taxonomy.\n\n> **User-triggered fetchers ignore robots.txt by design.** Google now documents **Google-Agent** (Project Mariner, agentic browsing) plus **Google-NotebookLM** and **Google Messages** as *user-triggered* fetchers that **cannot be blocked via robots.txt**. Use server-side access controls instead. By contrast, `Google-Extended` and `Google-CloudVertexBot` obey robots.txt. Emerging: **Web Bot Auth** (RFC 9421) lets bots authenticate cryptographically via a `Signature-Agent` header + key directory at `agent.bot.goog` (used by Google-Agent); reverse-DNS verification remains the fallback.\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- **Back-button hijacking** (spam-policy violation, malicious practices): flag pages that defeat the Back button via `history.pushState`\u002F`replaceState` (including scripts injected by third-party ad\u002Flibrary platforms). Added to Google's spam policies 2026-04-13; **enforcement live since 2026-06-15** (manual actions + automated demotions): treat as Critical.\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 & Page Experience\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: Googlebot Smartphone is the primary crawler (rollout completed 2024). A mobile version is **not strictly required** (Google says \"very strongly recommended\"), sites that don't work on mobile can still be indexed, but the real risk is **content\u002Fparity loss**, not hard exclusion.\n- **Mobile\u002Fdesktop content parity** (highest-value mobile check): equivalent primary content, matching robots meta tags, matching titles\u002Fdescriptions, equivalent structured data, crawlable resources; avoid lazy-loading primary content that requires user interaction.\n- **Intrusive interstitials \u002F ad density**: flag full-page interstitials, standalone consent-redirect pages, persistent blocking dialogs, and excessive\u002Fdistracting ad density (a named page-experience aspect). Acceptable: small banners, standard CMS\u002Flegal dialogs.\n- **\"Read more\" deep links**: keep key content **immediately visible on load** (not behind tabs\u002Faccordions), don't hijack scroll on load, and preserve URL hash fragments, content hidden behind expandable sections is less likely to qualify.\n\n> **Page experience is guidance, not a single ranking system.** Only **Core Web Vitals** feeds ranking directly; **HTTPS** is a confirmed but lightweight signal (affects \u003C~1% of queries). Relevance can still win even when page experience is sub-par, so don't over-weight security headers. Note: the standalone **Page Experience report was removed** from Search Console (monitor via the Core Web Vitals + HTTPS reports).\n\n### 6. Core Web Vitals\n- **LCP** (Largest Contentful Paint): target \u003C=2.5s\n- **INP** (Interaction to Next Paint): target \u003C=200ms\n  - INP replaced FID on March 12, 2024. FID was removed from Chrome's field-data tools (CrUX API, PageSpeed Insights) on September 9, 2024 (Lighthouse is a lab tool that never reported FID). Do NOT reference FID anywhere.\n- **CLS** (Cumulative Layout Shift): target \u003C=0.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## Agent-Friendly Pages & Agentic Browsing\n\nAI agents (not just AI summarizers) increasingly read sites through three\nchannels: vision models on screenshots, raw HTML\u002FDOM, and the **accessibility\ntree** (the cleanest signal). Audit criteria: semantic HTML (real `\u003Cbutton>`\nand `\u003Ca>`, not `\u003Cdiv onclick>`), label associations, interactive target sizing,\nlayout stability across templates, `cursor: pointer` correctness, live in\n`references\u002Fagent-friendly-pages.md`.\n\nGoogle now ships a Lighthouse **Agentic Browsing** category (default-on since\nLighthouse 13.3.0, Chrome 150+; buckets: agent-centric accessibility, CLS +\nllms.txt, three WebMCP audits). It reports a **fractional pass-ratio (X of N),\nnot a 0-100 score**, keep that distinct from this skill's own Agent-UX 0-100\nheuristic below. The PSI REST API does not expose it; run via Lighthouse CLI\n`--only-categories=agentic-browsing`, DevTools, or the PSI web UI. See\n`references\u002Fagent-friendly-pages.md`.\n\n### Audit command\n\n```bash\n# Render with Playwright + capture accessibility tree, then score\n\"$HOME\u002F.Codex\u002Fskills\u002Fseo\u002Fbin\u002FCodex-seo\" run agent_ux_check.py https:\u002F\u002Fexample.com --json\n```\n\nThe scanner outputs an Agent-UX score (0-100) plus itemized issues:\n- HTML findings: real buttons \u002F anchors, `\u003Cdiv onclick>` widgets, semantic\n  landmarks, inputs without `\u003Clabel for>`, inputs without ARIA labels\n- Accessibility tree findings: total nodes, interactive nodes, unnamed\n  interactive elements, `role=\"generic\"` ratio\n\nThe accessibility-tree snapshot uses Playwright's\n`page.accessibility.snapshot(interesting_only=False)`. To capture the tree\nwithout scoring, use `\"$HOME\u002F.Codex\u002Fskills\u002Fseo\u002Fbin\u002FCodex-seo\" run render_page.py \u003Curl> --a11y-tree --json`.\n\nSurface findings as **opportunities**, not failures; don't gate audits on a\nsub-100 Agent-UX score. WebMCP origin-trial\u002Fsign-up status needs verification,\nand absence of WebMCP support is still an opportunity, not a defect.\n\n## Output\n\n### Technical Score: XX\u002F100\n\n### Category Breakdown\n| Category | Status | Score |\n|----------|--------|-------|\n| Crawlability | pass\u002Fwarn\u002Ffail | XX\u002F100 |\n| Indexability | pass\u002Fwarn\u002Ffail | XX\u002F100 |\n| Security | pass\u002Fwarn\u002Ffail | XX\u002F100 |\n| URL Structure | pass\u002Fwarn\u002Ffail | XX\u002F100 |\n| Mobile | pass\u002Fwarn\u002Ffail | XX\u002F100 |\n| Core Web Vitals | pass\u002Fwarn\u002Ffail | XX\u002F100 |\n| Structured Data | pass\u002Fwarn\u002Ffail | XX\u002F100 |\n| JS Rendering | pass\u002Fwarn\u002Ffail | XX\u002F100 |\n| IndexNow | pass\u002Fwarn\u002Ffail | 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## Google API Integration (Optional)\n\nIf Google API credentials are configured, use `\"$HOME\u002F.Codex\u002Fskills\u002Fseo\u002Fbin\u002FCodex-seo\" run pagespeed_check.py \u003Curl> --json` for real PSI + CrUX field data (replaces lab-only CWV estimates), `\"$HOME\u002F.Codex\u002Fskills\u002Fseo\u002Fbin\u002FCodex-seo\" run crux_history.py \u003Curl> --json` for 25-week CWV trends, and `\"$HOME\u002F.Codex\u002Fskills\u002Fseo\u002Fbin\u002FCodex-seo\" run gsc_inspect.py \u003Curl> --json` for real indexation status per URL.\n\n## Error Handling\n\n| Scenario | Action |\n|----------|--------|\n| URL unreachable | Report connection error with status code. Suggest verifying URL, checking DNS resolution, and confirming the site is publicly accessible. |\n| robots.txt not found | Note that no robots.txt was detected at the root domain. Recommend creating one with appropriate directives. Continue audit on remaining categories. |\n| HTTPS not configured | Flag as a critical issue. Report whether HTTP is served without redirect, mixed content exists, or SSL certificate is missing\u002Fexpired. |\n| Core Web Vitals data unavailable | Note that CrUX data is not available (common for low-traffic sites). Suggest using Lighthouse lab data as a proxy and recommend increasing traffic before re-testing. |\n",{"name":5,"license":15,"metadata":25,"description":29,"argument-hint":30,"user-invocable":31},{"author":26,"version":27,"category":28},"AgriciDaniel","2.2.4","seo","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\".\n","[url]",true,"main","f1bcf88a052c2ccbb297666b33fb820cfd94ac71",".agents\u002Fskills\u002Fresearch-data\u002Fresearch-seo-and-content\u002Fseo-technical",0,"https:\u002F\u002Fgithub.com\u002Fpeterish8\u002Fprats-skill-atlas","https:\u002F\u002Fgithub.com\u002Fpeterish8","Building real-world products with clean UI, smart architecture, and privacy in mind. Frontend-focused, full-stack curious.","2026-10-15 19:02:31",{"source":8,"skillName":5,"commands":41,"prompt":51,"zipAvailable":31},[42,45,48],{"tool":43,"command":44},"npx","npx skills add peterish8\u002Fprats-skill-atlas --skill seo-technical",{"tool":46,"command":47},"bunx","bunx skills add peterish8\u002Fprats-skill-atlas --skill seo-technical",{"tool":49,"command":50},"pnpm","pnpm dlx skills add peterish8\u002Fprats-skill-atlas --skill seo-technical","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fpeterish8\u002Fprats-skill-atlas\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fresearch-data\u002Fresearch-seo-and-content\u002Fseo-technical\u002FSKILL.md",[53,58],{"path":54,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":57,"sourceHtmlUrl":16},"LICENSE.txt","LICENSE","许可证",143,{"path":59,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":62,"sourceHtmlUrl":63},"references\u002Fagent-friendly-pages.md","REFERENCE","参考文档",8100,"https:\u002F\u002Fgithub.com\u002Fpeterish8\u002Fprats-skill-atlas\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fresearch-data\u002Fresearch-seo-and-content\u002Fseo-technical\u002Freferences\u002Fagent-friendly-pages.md",[65,74,82,90,97,105],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":69,"licenseFileUrl":70,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":20},"01M7CTAZW9MHV3RWH2ZEKDQXG9","skill-creator","Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Codex's capabilities with specialized knowledge, workflows, or tool integrations.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fpeterish8\u002Fprats-skill-atlas\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Ftools-utilities\u002Fgeneral-purpose\u002Fskill-creator\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fpeterish8\u002Fprats-skill-atlas\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Ftools-utilities\u002Fgeneral-purpose\u002Fskill-creator\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":78,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":20},"01M7CT8MG7NB1JR67XYZ9EWW3B","seo-audit","Full website SEO audit with parallel subagent delegation. Crawls up to 500 pages, detects business type, delegates to up to 15 specialists (8 always + 7 conditional), generates health score. Use when user says audit, full SEO check, analyze my site, or website health check.","https:\u002F\u002Fgithub.com\u002Fpeterish8\u002Fprats-skill-atlas\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Ftesting\u002Fqa-and-verification\u002Fseo-audit\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fpeterish8\u002Fprats-skill-atlas\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Ftesting\u002Fqa-and-verification\u002Fseo-audit\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":69,"licenseFileUrl":86,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":20},"01M7CT87F6GQ0WAD393PKPAGGX","playwright","Use when the task requires automating a real browser from the terminal (navigation, form filling, snapshots, screenshots, data extraction, UI-flow debugging) via `playwright-cli` or the bundled wrapper script.","https:\u002F\u002Fgithub.com\u002Fpeterish8\u002Fprats-skill-atlas\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Ftesting\u002Fqa-and-verification\u002Fplaywright\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fpeterish8\u002Fprats-skill-atlas\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Ftesting\u002Fqa-and-verification\u002Fplaywright\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":20},"01M7CT809RF90MG98MYEA97D8Z","gsap-performance","Official GSAP skill for performance — prefer transforms, avoid layout thrashing, will-change, batching. Use when optimizing GSAP animations, reducing jank, or when the user asks about animation performance, FPS, or smooth 60fps.","https:\u002F\u002Fgithub.com\u002Fpeterish8\u002Fprats-skill-atlas\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Ftesting\u002Fqa-and-verification\u002Fgsap-performance\u002FSKILL.md",[],[],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":101,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":20},"01M7CT7Q4VD995JHZMQQFBZZV9","firecrawl-seo-audit","Audit a website's SEO with Firecrawl. Use when the user asks for an SEO audit, metadata and heading review, sitemap\u002Fsite-structure analysis, keyword opportunities, competitor SERP comparison, or prioritized search optimization recommendations.","ISC","https:\u002F\u002Fgithub.com\u002Fpeterish8\u002Fprats-skill-atlas\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Ftesting\u002Fqa-and-verification\u002Ffirecrawl-seo-audit\u002FSKILL.md",[],[],{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":101,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":20},"01M7CT7JRJFC5RAKJBAP0VS1CV","firecrawl-qa","QA test a live website with Firecrawl browser and scrape evidence. Use when the user wants exploratory QA, form testing, navigation\u002Flink checks, responsive checks, performance observations, bug reports, or a pre-launch quality review.","https:\u002F\u002Fgithub.com\u002Fpeterish8\u002Fprats-skill-atlas\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Ftesting\u002Fqa-and-verification\u002Ffirecrawl-qa\u002FSKILL.md",[],[]]