seo-technical
Diagnose crawl access, HTTP responses, canonicals, sitemaps, rendering, and Core Web Vitals using observed site evidence. Use for technical indexing or performance problems; use seo-on-page for copy and seo-analytics for a traffic-loss investigation.
ronaldships · 已有静态检查记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add ronaldships/foundvia-discovery --skill seo-technical技能说明
name: seo-technical description: Diagnose crawl access, HTTP responses, canonicals, sitemaps, rendering, and Core Web Vitals using observed site evidence. Use for technical indexing or performance problems; use seo-on-page for copy and seo-analytics for a traffic-loss investigation.
Technical discovery diagnosis
Establish evidence
Inspect the supplied URL, intended public/private state, actual framework/version, and authorized Search Console history. Fetch initial HTML, robots.txt, response headers, and sitemap; use the Foundvia helper for a bounded preflight. If JavaScript changes the output, compare rendered HTML. A tool failure is not proof of a site failure.
Investigate in order
- Confirm status and redirect destination. Preserve intentional authentication and private routes.
- Distinguish a crawler prohibition from noindex. A blocked crawler cannot read a new noindex directive. Evaluate Googlebot and OAI-SearchBot independently; preserve GPTBot training policy.
- Compare declared canonical with the intended page and, where available, Google's selected canonical. Query parameters may represent distinct content. Do not canonicalize all child routes to the homepage.
- Check sitemap URLs against real public routes; include truthful lastmod only. A sitemap is a discovery hint, not proof of indexing.
- Inspect rendered content and crawlable links. Do not block framework assets such as /_next/ by default.
- For performance, use field data and a reproducible profile to locate the actual bottleneck. A laboratory score is not a real-user pass. Security headers protect users; do not present HSTS/CSP as ranking requirements.
Fix and verify
Report URL/file, evidence, consequence, priority, action, and verification. Change code only within the user's scope; check affected routes and the existing build/typecheck. Distinguish local fixes, deployment, and live verification. Do not promise recrawl timing or rank changes.
Read crawlability, performance, or security only for the relevant investigation. Source: Google robots specification.