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.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
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.
rel="noopener noreferrer" on external links; add rel="nofollow" only for untrusted or paid linksFor 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"?
rel="noopener noreferrer" to all external links for security.rel="sponsored" to paid or affiliate links; rel="nofollow" to links you cannot vouch for.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.
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
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Use when reviewing templates, rendered HTML, or shared components related to Create a custom 404 error page. Validate the final browser-facing markup, not just the source framework abstraction.
日本語の概要は準備中です。原文の説明を表示しています。
Use when auditing metadata, crawlability, structured data, or indexability related to Create a dedicated About page. Verify the rendered HTML and HTTP response rather than relying only on source files.
日本語の概要は準備中です。原文の説明を表示しています。
Use when reviewing component libraries, page flows, or CI pipelines that need repeatable accessibility checks. Automated testing is strongest at catching structural and attribute-level issues; it does not replace keyboard, screen reader, and manual UX testing.
日本語の概要は準備中です。原文の説明を表示しています。
Use when reviewing sign-in, sign-up, MFA, CAPTCHA, recovery, and re-auth flows. Evaluate the full authentication path, including error handling and backup methods, not just the primary login form.
日本語の概要は準備中です。原文の説明を表示しています。
Use when reviewing templates, rendered HTML, or shared components related to Make notifications accessible. Validate the final browser-facing markup, not just the source framework abstraction.
日本語の概要は準備中です。原文の説明を表示しています。
Use when reviewing rendered HTML, interactive components, or design-system patterns related to Use semantic table markup for screen readers. Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output where relevant.
日本語の概要は準備中です。原文の説明を表示しています。