본문으로 건너뛰기
cccskills
무료GitHub에 공개

internal-links

Audit links between pages on a website to find important pages with few incoming links. Suggest relevant connections from related content and clearer link text that describes the destination page.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

원문원문 설명 보기

Use when auditing a site's internal link structure, identifying pages that need more incoming links, generating contextual linking opportunities between related content, or reviewing a CMS template's internal linking patterns.

설치 방법 보기

이럴 때 유용합니다

  • Finding important pages with too few internal links
  • Adding relevant links between related articles
  • Replacing vague link text with descriptive wording
  • Reviewing internal linking patterns in CMS templates

포함된 파일(2)

  • SKILL.md3.0 KB
  • references/rule.md5.0 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

Add internal links to key pages

Internal links are how PageRank flows through your site. A key page with few internal links receives less PageRank signal, ranking lower than its content quality would otherwise allow. Googlebot also discovers pages through internal links — a page with zero incoming links is likely an orphan page.

Quick Reference

  • Important pages should receive multiple internal links with descriptive, keyword-relevant anchor text
  • Internal links distribute PageRank; pages receiving few internal links rank lower regardless of content quality
  • Use contextual inline links in body content — these carry more weight than navigation or footer links

Check

Using a site crawl, build a map of internal links. For each important page (key landing pages, top blog posts, product pages): (1) Count the number of unique internal pages linking to it. (2) Check if the anchor text of those links includes relevant keywords for the target page. (3) Identify pages with 0–2 incoming internal links (likely orphans or under-linked). (4) Verify links are in body content, not only in global navigation or footer.

Fix

  1. List your top 10–20 most important pages by business value.
  2. For each, identify pages on the site with topically related content.
  3. Add contextual inline links to those important pages from related content.
  4. Use descriptive anchor text that includes target keywords: instead of "click here", use "our guide to CSS Grid".
  5. Add a "Related articles" or "See also" section to articles, linking to relevant high-value pages.
  6. Ensure your site's top navigation links to your 5–10 most important commercial pages.
  7. Check that pillar pages link to their supporting cluster pages and vice versa.

Explain

PageRank, Google's foundational ranking algorithm, flows from page to page through internal links. A page with many high-quality internal links pointing to it receives more PageRank signal and ranks more competitively. Anchor text of internal links also provides keyword context signals to Google about the target page's topic.

Code Review

Build an internal link graph from crawl data. Compute in-degree (number of pages linking in) for each page. Flag pages with in-degree < 2 that are in the sitemap and not excluded by robots/noindex. Check anchor text of internal links for generic text ('here', 'click', 'read more') that could be replaced with descriptive keyword-rich text.


For full implementation details, code examples, and framework-specific guidance, see references/rule.md.

Rule page: https://frontendchecklist.io/rules/seo/internal-links

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

404-page

무료

Create and review custom 404 pages that help visitors recover from broken or moved links through search and navigation. Check the rendered page and HTTP response so missing content returns a proper 404 status.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Creating a helpful custom 404 page
  • Adding search and navigation for broken links
  • Checking missing pages that return HTTP 200
thedaviddias/Front-End-Checklist7.5만2026년 10월 6일 업데이트

Audit or create a dedicated About page that explains a website’s purpose and identifies its people or organization. Review the rendered output and supporting information, including expertise and contact details, to find gaps.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Reviewing a website’s About page
  • Creating a page about the organization and its mission
  • Checking how operator information appears in rendered output
thedaviddias/Front-End-Checklist7.5만2026년 10월 6일 업데이트

Review and add automated accessibility checks for components, pages, and continuous integration workflows. Use axe-based tools to detect structural and attribute issues, while identifying checks that still need keyboard or screen reader testing.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Review accessibility coverage for shared components
  • Add accessibility checks to page flow tests
  • Run accessibility tests in CI
thedaviddias/Front-End-Checklist7.5만2026년 10월 6일 업데이트

Review sign-in, registration, multi-factor authentication, and account recovery for accessibility barriers. Find blocked paste, difficult code entry, and inaccessible backup methods, then suggest authentication paths that support password managers, autofill, or device approval.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Reviewing accessibility across the sign-in process
  • Checking verification code paste and autofill
  • Inspecting password reset and account recovery
thedaviddias/Front-End-Checklist7.5만2026년 10월 6일 업데이트

Review form errors, success messages, and live updates so screen reader users receive important notifications. Check the HTML delivered to the browser, announcement settings, display duration, and dismissal controls, then identify specific elements that need changes.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Reviewing form error announcements
  • Checking success message display duration
  • Auditing live update notifications
thedaviddias/Front-End-Checklist7.5만2026년 10월 6일 업데이트

Review HTML tables so screen reader users can understand how headers and data relate. Check header markup, table descriptions, and merged cells, then identify specific fixes and ways to verify them.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Reviewing tables for screen reader accessibility
  • Checking header relationships in tables with merged cells
  • Reviewing table patterns in a design system
thedaviddias/Front-End-Checklist7.5만2026년 10월 6일 업데이트

thedaviddias의 스킬 모두 보기

이 스킬의 문제 신고