Token导航 LogoToken导航TokenDH.com
研究检索external-servicegithub未标认证来源可访问许可证需确认审计通过

fix-linking修复链接

Agent Skill

fix-linking 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

38,788

周安装

1,619

GitHub Stars

7

下载量

12,466
CodexClaudeCursorGemini CLI

安装说明

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

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

请帮我安装这个 Agent Skill:fix-linking(修复链接)
来源仓库:https://github.com/calm-north/seojuice-skills
仓库路径:skills/fix-linking
安装命令:
npx skills add https://github.com/calm-north/seojuice-skills --skill fix-linking
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/calm-north/seojuice-skills --skill fix-linking

简介

使用中心辐射型拓扑、PageRank 流和锚文本优化来设计和审核内部链接结构。

  • 支持五种架构模型(中心辐射型、筒仓型、扁平型、金字塔型、网状型),并提供适合不同网站大小和内容类型的指导
  • 包括孤立页面检测、链接深度分析和锚文本多样性评估,以识别排名障碍
  • 提供具体的链接注入计划,包括源页面、目标页面、锚文本建议和优先级排名
  • 涵盖 PageRank 流逻辑、主题相关信号以及架构更改的预期 ROI 时间表(15-50% 流量改进)

SKILL.md

Fix Linking

Design and audit internal link structures using hub-and-spoke topology, PageRank flow logic, and anchor text budgets.

Why Internal Links Matter

Internal links do two things: (1) pass PageRank between pages, and (2) signal topical relevance via anchor text. A page with zero incoming internal links is an orphan — invisible to authority flow regardless of content quality.

Architecture Model Selection

Before auditing links, choose the right architecture model for the site:

ModelBest ForSite SizeKey Characteristic
Hub-and-Spoke (Topic Cluster)Content marketing, SaaS, publishers50-500 pagesBidirectional links between pillar and cluster articles
Silo StructureE-commerce, directories, large enterprises100+ categoriesVertical-only links within topic silos
Flat ArchitectureSmall sites, portfolios, startups<100 pagesAll pages within 2-3 clicks, cross-linked freely
PyramidNews sites, large blogs, corporate500+ pagesTop-down hierarchy, authority concentrates at top
Mesh/MatrixKnowledge bases, wikis, help centersAnyFree-form linking between any related pages

Key Metrics by Architecture

MetricHub-and-SpokeSiloFlatPyramidMesh
Target click depth≤3≤4≤2≤4≤3
Internal links per page5-103-78-153-58-15
Cross-section linksManyFewN/ASomeMany
Authority distributionDistributed to hubsTop of siloEvenTop-heavyEven

Expected ROI from Architecture Changes

ChangeTypical ImpactTimeline
Fix orphan pages+15-30% traffic to those pages2-4 weeks
Build first topic cluster+10-25% traffic to cluster pages4-8 weeks
Reduce click depth by 1 level+5-15% crawl efficiency2-6 weeks
Anchor text optimization+5-10% ranking improvement4-12 weeks
Full architecture migration+20-50% overall organic traffic3-6 months

Recommended for most sites: Hub-and-Spoke as the primary model, with silo-style isolation between unrelated topic areas.

Phase 1: Map the Current Structure

Before designing links, understand what exists:

  1. Hub pages. Pages that aggregate links and distribute authority — homepage, category pages, pillar articles. List them.
  2. Orphan pages. No incoming internal links from crawlable pages. They receive zero PageRank from the internal graph.
  3. Link depth. How many clicks from the homepage does each important page require? Depth 4+ pages are effectively buried.
  4. Anchor text. Repeated identical anchors are fine. Generic anchors ("click here", "read more") waste relevance signal.

Ask the user for their page list or sitemap, or work with what they describe.

Phase 2: Hub-and-Spoke Design

Hub Pages (pillar/category)

  • Linked from homepage or main navigation
  • Link out to all supporting pages in their cluster
  • Serve as authority redistribution nodes

Spoke Pages (supporting/cluster articles)

  • Receive at least 2-3 internal links from hub and sibling spokes
  • Always link back to their hub page
  • Link to 2-4 sibling spokes where contextually relevant
  • Never link to competing pages (same keyword intent)

Cross-Cluster Links

  • Only when there is genuine topical relevance
  • Use to signal E-E-A-T connections (e.g., case study → methodology page)
  • Limit to 1-2 per page to avoid diluting cluster coherence

Phase 3: Anchor Text Budget

For internal links, each page should receive anchor text in this distribution:

Anchor TypeTarget ShareExample
Exact match20-30%"content decay detection"
Partial match30-40%"detecting when content decays"
Related/semantic20-30%"pages losing traffic"
Branded5-10%"our decay detection feature"
Generic0-5%"learn more"

Diversity improves relevance coverage for semantic search.

Phase 4: Orphan Page Resolution

For each orphan page, apply this decision tree:

  1. Worth ranking? If no (thin, superseded), redirect to the closest relevant page. Stop.
  2. Which cluster? Find the nearest hub page.
  3. Which 2-3 existing pages would readers logically arrive from? These are injection points.
  4. What anchor text fits naturally? Match the orphan page's target keyword.
  5. Does the hub page need a content update to include a contextual reference?

Phase 5: Link Injection Plan

Produce a concrete action plan:

Source PageTarget PageSuggested Anchor TextWhere on Source PagePriority
/blog/seo-guide/tools/keyword-research"keyword research tool"Under "Research Phase" headinghigh
...............

Priority = high if the target is a revenue-critical or high-intent page.

Output Format

Internal Link Audit: [domain]

Current State

  • Orphan pages: [count or list]
  • Average link depth for important pages: [value]
  • Hub pages identified: [list]
  • Anchor text diversity: [assessment]

Hub-and-Spoke Map For each cluster: Hub → [Spoke 1, Spoke 2, Spoke 3...]

Link Injection Plan [Table from Phase 5]

Anchor Text Fixes Pages where anchor text is entirely generic and needs replacement.

Recommendations

  1. Orphan pages that are revenue-critical — link them first
  2. Pages at depth 4+ that should be at depth 2 — add shortcuts via hub pages
  3. Clusters with weak internal connectivity — add sibling cross-links
  4. Pages with 0-1 incoming links that are important for conversions

Pro Tip: Try the free Internal Link Finder and Anchor Text Diversity tools at seojuice.com. SEOJuice MCP users can run /seojuice:site-health for instant orphan page detection, link depth distribution, and most-linked pages — the get_site_topology tool maps your entire internal link graph automatically.

适合场景

01

用户想查找某类 Agent Skill 时

02

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

03

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

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

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

能力 4

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

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

平台分布

Codex

36.52%
按下载量换算4,553

Claude

30.93%
按下载量换算3,856

Cursor

19.17%
按下载量换算2,390

Gemini CLI

10.05%
按下载量换算1,253

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

external-service

该 Skill 可能调用第三方服务、云服务或外部模型 API,使用前需要确认账号、额度、数据发送范围和服务条款。

安装前确认

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

来源信息

继续浏览同类 Skills