Use when auditing site architecture or investigating why specific pages have low organic traffic despite good content. Applies to any site with more than ~20 pages.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
Orphan pages receive no PageRank from internal links and are rarely recrawled by Googlebot, which limits their ability to rank even when their content is excellent.
Using a site crawl (Screaming Frog or similar), identify pages that appear in the sitemap or have been indexed but receive zero inbound internal links. List the URL, page title, and any existing content that could logically link to the orphan page.
For each orphan page, identify 2–5 relevant existing pages that should link to it. Add contextual <a href='...'>anchor text</a> links in body content, related articles sections, or navigation. Ensure anchor text is descriptive and matches the target page's primary keyword.
Search engines discover pages primarily by following links. A page with no internal links may be found via the sitemap but receives no PageRank from the site's link graph. Without PageRank, the page has limited ranking potential even if the content is excellent. Regular crawling also depends on internal links — orphan pages are recrawled less frequently.
Crawl the site and build an inbound link count for each URL. Cross-reference against the sitemap and indexed pages. Identify URLs with zero inbound internal links. For each orphan, report: URL, page title, word count, and potential linking pages (pages with semantically related content). Exclude intentional no-link pages (thank-you pages, admin pages).
For full implementation details, code examples, and framework-specific guidance,
see references/rule.md.
Rule page: https://frontendchecklist.io/rules/seo/orphan-pages
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
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.
日本語の概要は準備中です。原文の説明を表示しています。