[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MEEGY3KB8PBH194MD1NSDQ":3,"skill-same:01M6MEEGY3KB8PBH194MD1NSDQ":96},{"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":29,"publishedAt":51,"linkOnly":52,"markdownContent":53,"markdownBody":54,"frontMatter":55,"refName":62,"commitSha":63,"skillDirectory":64,"forksCount":65,"repositoryHtmlUrl":66,"repositoryHomepageUrl":67,"ownerHtmlUrl":68,"ownerBlogUrl":69,"ownerDescription":70,"updatedAt":71,"install":72,"resources":84},"01M6MEEGY3KB8PBH194MD1NSDQ","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\".","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1575,"MIT","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Favalonreset\u002Fseo-dungeon\u002Fskills\u002Fseo-technical\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Favalonreset\u002Fseo-dungeon\u002Fskills\u002Fseo-technical\u002FSKILL.md",[19,24],{"categoryNo":20,"categoryName":21,"taxonomyType":22,"taxonomyTypeDesc":23},"01JBSEEDCAT000000000000019","营销推广","SCENARIO","使用场景",{"categoryNo":25,"categoryName":26,"taxonomyType":27,"taxonomyTypeDesc":28},"01JBSEEDCAT000000000000035","市场营销","PROFESSION","适用职业",[30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50],"seo","technical","seo technical","when","core","seo audit","security","data","headers","mobile","rendering","audit","structure","across","technical seo audit","URL","crawlability","issues","vitals","crawl","categories","2026-11-10 10:12:30",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.7\"\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 `claude-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- AMP has no separate ranking advantage. Since 2026-07-01, Google Search sends\n  users directly to publisher-hosted AMP URLs, so do not recommend AMP Cache,\n  AMP Viewer, or signed exchange maintenance. Audit AMP against the same content,\n  action-parity, and quality requirements as other pages.\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- Canonicalization fixes can take time: Google may retain corrected pages in a\n  duplicate cluster for **up to two weeks** while re-evaluating them. Do not\n  interpret an unchanged canonical immediately after a fix as proof that the\n  fix failed.\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. Lighthouse 13.4.1 re-enabled the category through the PSI API.\nIt is also available through Lighthouse CLI with\n`--only-categories=agentic-browsing`, DevTools, and 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\nclaude-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 Chromium's\n`Accessibility.getFullAXTree` CDP command through Playwright. To capture the\ntree without scoring, use\n`claude-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 credentials or optional tools are available, use direct DataForSEO calls for real page analysis (status codes, page timing, broken links, on-page checks), Lighthouse audits, and technology stack detection.\n\n## Google API Integration (Optional)\n\nIf Google API credentials are configured, use `claude-seo run pagespeed_check.py \u003Curl> --json` for real PSI + CrUX field data (replaces lab-only CWV estimates), `claude-seo run crux_history.py \u003Curl> --json` for 25-week CWV trends, and `claude-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 `claude-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- AMP has no separate ranking advantage. Since 2026-07-01, Google Search sends\n  users directly to publisher-hosted AMP URLs, so do not recommend AMP Cache,\n  AMP Viewer, or signed exchange maintenance. Audit AMP against the same content,\n  action-parity, and quality requirements as other pages.\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- Canonicalization fixes can take time: Google may retain corrected pages in a\n  duplicate cluster for **up to two weeks** while re-evaluating them. Do not\n  interpret an unchanged canonical immediately after a fix as proof that the\n  fix failed.\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. Lighthouse 13.4.1 re-enabled the category through the PSI API.\nIt is also available through Lighthouse CLI with\n`--only-categories=agentic-browsing`, DevTools, and 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\nclaude-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 Chromium's\n`Accessibility.getFullAXTree` CDP command through Playwright. To capture the\ntree without scoring, use\n`claude-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 credentials or optional tools are available, use direct DataForSEO calls for real page analysis (status codes, page timing, broken links, on-page checks), Lighthouse audits, and technology stack detection.\n\n## Google API Integration (Optional)\n\nIf Google API credentials are configured, use `claude-seo run pagespeed_check.py \u003Curl> --json` for real PSI + CrUX field data (replaces lab-only CWV estimates), `claude-seo run crux_history.py \u003Curl> --json` for 25-week CWV trends, and `claude-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":56,"description":59,"argument-hint":60,"user-invocable":61},{"author":57,"version":58,"category":30},"AgriciDaniel","2.2.7","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","40706766fd37c03ca624f5206741fef55dd2a684","plugins\u002Favalonreset\u002Fseo-dungeon\u002Fskills\u002Fseo-technical",491,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins","https:\u002F\u002Fhol.org\u002Fplugins\u002Fbest-codex-plugins","https:\u002F\u002Fgithub.com\u002Fhashgraph-online","https:\u002F\u002Fhol.org","Open-source standards and developer tools for interoperable AI agents: discovery, identity, communication, payments, privacy and security.","2026-11-14 14:06:13",{"source":8,"skillName":5,"commands":73,"prompt":83,"zipAvailable":61},[74,77,80],{"tool":75,"command":76},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill seo-technical",{"tool":78,"command":79},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill seo-technical",{"tool":81,"command":82},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill seo-technical","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Favalonreset\u002Fseo-dungeon\u002Fskills\u002Fseo-technical\u002FSKILL.md",[85,90],{"path":86,"resourceType":87,"resourceTypeDesc":88,"sizeBytes":89,"sourceHtmlUrl":16},"LICENSE.txt","LICENSE","许可证",143,{"path":91,"resourceType":92,"resourceTypeDesc":93,"sizeBytes":94,"sourceHtmlUrl":95},"references\u002Fagent-friendly-pages.md","REFERENCE","参考文档",8095,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Favalonreset\u002Fseo-dungeon\u002Fskills\u002Fseo-technical\u002Freferences\u002Fagent-friendly-pages.md",[97,106,114,122,130,138],{"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":15,"licenseFileUrl":101,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":105},"01M7DV332YQMGD8WTRJ9DZQXTB","worktable-review-with-annotations","Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":110,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":105},"01M7DV2YGHCZVBEB1AHYB6CGHE","worktable-find-and-synthesize-context","Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FSKILL.md",[],[],{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":118,"sourceHtmlUrl":119,"categories":120,"keywords":121,"publishedAt":105},"01M7DV2TQN1H11ME2SAF9MXN7V","worktable-create-or-update-docs","Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FSKILL.md",[],[],{"skillNo":123,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":126,"sourceHtmlUrl":127,"categories":128,"keywords":129,"publishedAt":105},"01M7DV2NE452NEA8TXATKSNAJH","worktable-create-or-manage-records","Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FSKILL.md",[],[],{"skillNo":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":134,"sourceHtmlUrl":135,"categories":136,"keywords":137,"publishedAt":105},"01M7DV2HENRBR2KSCVM064WH0Y","worktable-create-or-manage-interactive-html","Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FSKILL.md",[],[],{"skillNo":139,"name":140,"nameZh":6,"description":141,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":142,"sourceHtmlUrl":143,"categories":144,"keywords":145,"publishedAt":105},"01M7DV2CADR5R7RQFFYPNAGR9Y","worktable-collaborate-threads","Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FSKILL.md",[],[]]