Use when auditing internal link structure or reviewing link attributes. Applies to any site using rel=nofollow on links pointing to pages within the same domain.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
Adding rel=nofollow to internal links prevents PageRank from flowing to those pages—reducing their ability to rank—while providing no benefit over simply omitting the attribute.
Scan all internal links (<a href> tags pointing to the same domain) for the presence of rel='nofollow' or rel containing 'nofollow'. List each instance with its source page, anchor text, and target URL.
Remove rel='nofollow' from internal links. If the goal was to prevent indexing of the target page, add <meta name='robots' content='noindex'> to the target page instead. If the goal was to prevent crawling, use robots.txt Disallow for that path.
The rel=nofollow attribute was originally designed for untrusted external links. When applied to internal links, it blocks PageRank from flowing to your own pages without any benefit. Google has stated that PageRank sculpting via nofollow does not work—the PageRank that would have passed is simply lost, not redistributed.
Query all <a href='...'> elements. For each link, check if rel contains 'nofollow'. Determine if the link is internal (same domain) or external. Flag every internal link with rel='nofollow'. Check if the flagged links are in navigation, header, footer, or body content. Look for rel='nofollow new-tab' patterns that may have been applied blanket to all links.
For full implementation details, code examples, and framework-specific guidance,
see references/rule.md.
Rule page: https://frontendchecklist.io/rules/seo/nofollow-internal
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
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.
日本語の概要は準備中です。原文の説明を表示しています。