Find important pages that receive no links from elsewhere on the site. Compare crawl results with sitemaps and indexed pages, then suggest relevant existing pages where descriptive internal links could help connect the content.
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.
Review the instructions the agent will receive before you install.
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
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
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.
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.
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 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.
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.
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.