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

external-links

Review external links in articles to identify unsupported factual claims and suggest authoritative sources. Check link attributes used for security and for identifying paid, affiliate, or untrusted links, then guide corrections to citations and markup.

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

원문원문 설명 보기

Use when auditing content pages for citation quality, suggesting authoritative sources to link for factual claims, or reviewing whether a page's external link attributes (nofollow, noopener) are correctly set.

설치 방법 보기

이럴 때 유용합니다

  • Find factual claims that lack source links
  • Add citations to official or research sources
  • Review external link security attributes
  • Check paid and affiliate link attributes

포함된 파일(2)

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

SKILL.md(원문)

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

Add relevant external links

Outbound links to authoritative sources strengthen the credibility of your content and are considered a positive trust signal by Google. Pages that cite their sources rank better for informational queries than those that make unsupported claims.

Quick Reference

  • Link out to authoritative sources that support your claims — this demonstrates E-E-A-T and improves credibility
  • External links to reputable sites do not hurt your SEO; Google treats them as a trust signal
  • Use rel="noopener noreferrer" on external links; add rel="nofollow" only for untrusted or paid links

Check

For each content page, count the number of external <a href> links pointing to domains other than the current site. Check: (1) Are factual claims backed by links to authoritative sources (government sites, peer-reviewed research, official documentation)? (2) Do all external links have rel="noopener noreferrer" for security? (3) Are paid or sponsored links marked with rel="sponsored" or rel="nofollow"?

Fix

  1. Identify factual claims in the content that cite statistics, research, or expert consensus without a source link.
  2. Find the authoritative source (study, official documentation, government data) and add an inline link.
  3. Add rel="noopener noreferrer" to all external links for security.
  4. Add rel="sponsored" to paid or affiliate links; rel="nofollow" to links you cannot vouch for.
  5. Avoid linking to competitor sites for their main commercial pages; prefer linking to neutral third parties. Example: Replace "Studies show 60% of users abandon slow pages" with: "According to <a href="https://web.dev/performance/" rel="noopener noreferrer">Google's web.dev research</a>, 60% of users abandon pages that take over 3 seconds to load."

Explain

Google uses the context of your outbound links as a signal of content quality. Pages that cite reputable external sources are treated as more trustworthy than those making unsupported assertions. Properly attributed external links also demonstrate E-E-A-T by showing you have researched the topic from primary sources.

Code Review

Parse all <a href> elements with external URLs (different domain than the site). Verify each external link has rel="noopener noreferrer". Flag paid/affiliate links missing rel="sponsored". Count external links per page — flag pages with zero external links in long-form content (>500 words) that contains factual claims.


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

Rule page: https://frontendchecklist.io/rules/seo/external-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의 스킬 모두 보기

이 스킬의 문제 신고