Token导航 LogoToken导航TokenDH.com
研究检索需要联网clawhub未标认证来源可访问clear审计通过

site-crawlability网站可抓取性

Agent Skill

site-crawlability 用于处理浏览器自动化、网页检查和页面信息提取,适合在 OpenClaw 中需要让 Agent 打开页面、读取网页或验证前端流程时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

6,891

周安装

296

GitHub Stars

公开资料未说明

下载量

2,415
OpenClaw

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

MIT-0

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:site-crawlability(网站可抓取性)
来源仓库:https://github.com/kostja94/site-crawlability
安装命令:
openclaw skills install site-crawlability
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 OpenClaw 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

ClawHubOpenClaw
openclaw skills install site-crawlability

简介

site-crawlability 用于处理浏览器自动化与网页检查,适合在 OpenClaw 中验证前端流程时使用。

  • 它能提升网站可抓取性,修复孤立页面并优化搜索引擎结构。
  • 通过 clawhub 安装后,可结合原始文档配置爬虫策略与访问规则。
  • 安装前需确认权限范围、维护状态,以及是否会触发页面渲染或动态内容加载。
  • 使用时建议限定于自有站点或授权测试环境,避免对第三方平台造成干扰。

SKILL.md

name
site-crawlability
description
When the user wants to improve crawlability, fix orphan pages, or optimize site structure for search engines. Also use when the user mentions "crawlability," "crawl budget," "orphan pages," "internal links," "site structure," "site crawlability," "infinite scroll," "pagination," "masonry SEO," "AI crawler optimization," "GPTBot crawlability," "ClaudeBot crawlability," or "content not indexed." For internal links, use internal-links.
metadata
version
1.2.1

SEO Technical: Crawlability

Guides crawlability improvements: robots, X-Robots-Tag, site structure, and internal linking.

When invoking: On first use, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On subsequent use or when the user asks to skip, go directly to the main output.

Scope (Technical SEO)

  • Redirect chains & loops: Fix multi-hop redirects; point directly to final URL
  • Broken links (4xx): Fix broken internal/external links; 301 or remove
  • Site architecture: Logical hierarchy; pages within 3–4 clicks from homepage
  • Orphan pages: Add internal links to pages with no incoming links
  • Pagination: Prefer pagination over infinite scroll for crawlability
  • Crawl budget: Reduce waste on duplicates, redirects, low-value URLs (see below)
  • AI crawler optimization: SSR for critical content; URL management; reduce 404/redirect waste (see below)

Initial Assessment

Check for project context first: If .claude/project-context.md or .cursor/project-context.md exists, read it for site structure.

Identify:

  1. Site structure: Flat vs. deep hierarchy
  2. Framework: Next.js, static, SPA, etc.
  3. Key paths: Sitemap, robots.txt, API, static assets

Best Practices

Redirect Chains & Loops

  • Fix multi-hop redirects; point directly to final URL
  • Loops: URLs redirecting back to themselves; break the cycle

Broken Links (4xx)

  • Fix broken internal/external links; 301 or remove
  • Audit regularly; update or remove broken links

Site Architecture

PrincipleGuideline
DepthImportant pages within 3–4 clicks from homepage
Orphan pagesAdd internal links to pages with no incoming links; see internal-links for link strategy
HierarchyLogical structure; hub pages link to content

Pagination vs Infinite Scroll

Problem: With infinite scroll, crawlers cannot emulate user behavior (scroll, click "Load more"); content loaded after initial page load is not discoverable. Same applies to masonry + infinite scroll, lazy-loaded lists, and similar patterns.

Solution: Prefer pagination for key content. If keeping infinite scroll, make it search-friendly per Google's recommendations:

RequirementPractice
Component pagesChunk content into paginated pages accessible without JavaScript
Full URLsEach page has unique URL (e.g. ?page=1, ?lastid=567); avoid #1
No overlapEach item listed once in series; no duplication across pages
Direct accessURL works in new tab; no cookie/history dependency
pushState/replaceStateUpdate URL as user scrolls; enables back/forward, shareable links
404 for out-of-bounds?page=999 returns 404 when only 998 pages exist

Reference: Infinite scroll search-friendly recommendations (Google Search Central, 2014)

Pagination (Traditional)

  • Reference links to next/previous pages; rel="prev" / rel="next" where applicable
  • Avoid dynamic-only loading; ensure links in HTML

Crawl Budget

Crawl budget is the number of URLs Googlebot will crawl on your site in a given period. Large sites (10,000+ pages) may waste up to 30% of crawl budget on duplicates, redirects, and low-value URLs.

Waste sourceFix
Duplicate URLsCanonical; consolidate; 301 to preferred
Redirect chainsPoint directly to final URL
Parameter proliferationUse rel="canonical"; consider Clean-param (Yandex)
Low-value pagesnoindex for thin/duplicate; see indexing
Crawl trapsAvoid infinite URL generation (e.g. faceted filters)

Sitemap: Include only indexable, canonical URLs. See xml-sitemap, canonical-tag.

AI Crawler Optimization

AI crawlers (GPTBot, ClaudeBot, PerplexityBot, etc.) now represent ~28% of Googlebot's crawl volume. Their behavior differs from search engines—optimizing for both improves GEO (AI search visibility). See generative-engine-optimization for GEO strategy. Vercel/MERJ study (Dec 2024):

FactorAI Crawlers (GPTBot, Claude)Googlebot
JavaScriptDo not execute JS; cannot read client-side rendered contentFull JS rendering
404 rate~34% of fetches hit 404s~8%
Redirects~14% of fetches follow redirects~1.5%
Content in initial HTMLJSON, RSC in initial response can be indexedSame

Recommendations for AI crawlability:

PracticeAction
Server-side renderingCritical content in initial HTML. Use SSR, ISR, or SSG. See rendering-strategies for full guide.
URL managementKeep sitemaps updated; use consistent URL patterns; avoid outdated /static/ assets that cause 404s. AI crawlers frequently hit outdated URLs.
RedirectsFix redirect chains; point directly to final URL. AI crawlers waste ~14% of fetches on redirects.
404 handlingFix broken links; remove or redirect outdated URLs. High 404 rates suggest AI crawlers may use stale URL lists.

Reference: The rise of the AI crawler (Vercel, 2024)

Common Issues

IssueCheck
Redirect chainsUpdate links to point directly to final URL
Broken links301 or remove; audit internal and external
Orphan pagesAdd internal links from hub or navigation; see internal-links for strategy
Infinite scrollProvide paginated component pages; or replace with pagination for key content; see above
AI crawlers missing contentEnsure critical content in initial HTML; see rendering-strategies

Output Format

  • Redirect audit: Chains and loops to fix
  • Broken link audit: 4xx links to fix
  • Site structure: Orphan pages, hierarchy
  • Pagination: Implementation for crawlable content
  • AI crawler: SSR/URL/redirect checks if GEO or AI visibility is a goal

Related Skills

  • seo-strategy: SEO workflow; crawlability is Technical phase (P0)
  • website-structure: Plan which pages to build, page priority, structure planning; use before or alongside crawlability audit
  • robots-txt: robots.txt configuration; AI crawler allow/block (GPTBot, ClaudeBot)
  • xml-sitemap: URL discovery; keep updated to reduce AI crawler 404s
  • google-search-console: Index status, Coverage report
  • indexing: Fix indexing issues
  • internal-links: Internal linking best practices
  • masonry: Masonry + infinite scroll has same crawl issue; layout skill references this for SEO
  • generative-engine-optimization: GEO strategy; AI search visibility; crawlability enables AI citation
  • canonical-tag: Canonical reduces crawl budget waste on duplicates
  • rendering-strategies: SSR, SSG, CSR; content in initial HTML; crawler visibility

适合场景

01

OpenClaw 用户查找和安装 Skill 时

02

用户想查找某类 Agent Skill 时

03

需要根据任务场景推荐可安装能力包时

04

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

补充不同宿主或平台的使用分布数据

能力 5

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

OpenClaw

84.62%
按下载量换算2,044

安全审计

VirusTotal

通过

ClawScan

通过

Static analysis

通过

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills