To find orphan pages, compare CMS and sitemap URLs with addresses reached by following internal links. Verify that each candidate actually lacks incoming internal links, since crawler scope or JavaScript limitations can create false positives. Connect useful current pages from relevant service hubs, categories or articles.

Do not treat one crawl as the whole inventory

Build inventories of published CMS URLs, sitemap URLs and pages discovered by following links from the homepage. Check redirect destinations, HTTPS and hostname variants, and parameters before comparison. Different URL spellings for the same destination should not create a false orphan classification.

Open candidates present in an inventory but absent from the crawl. Check whether the crawler excludes a subdomain, directory or JavaScript navigation, or links require login. Search for actual incoming href links. Sitemap inclusion alone does not establish a route through internal navigation.

Assess why the page should remain

A service, old campaign, event record and current guide call for different decisions. Is the information accurate and needed? Does the page have an independent job? Where would a visitor need it? Adding every candidate to the main menu before answering those questions can make navigation harder.

Imagine a new specialist-service page omitted from the service hub. A relevant link there makes sense. An expired campaign with outdated conditions may need another treatment. This hypothetical comparison demonstrates why content status should precede the linking decision.

Assess why the page should remain
Page stateQuestionDecision direction
Current with an independent purposeWhere should visitors discover it?Connect from relevant hubs and content.
Duplicates another page's jobIs a separate version needed?Consider editorial consolidation.
Contains outdated conditionsDoes it have historical or update value?Choose revision or archival treatment.
Belongs to a special journeyShould it appear in general navigation?Assess access and purpose.
Was generated accidentallyWhich process created it?Correct the underlying source.

Complete publication with a connection check

After the correction, follow the intended internal path to the page. Verify the actual destination and check that it does not accidentally open the wrong language version. Closing a row in the inventory does not establish that a visitor can complete the task.

Add “which existing pages will lead here?” to the new-content workflow. Review incoming links when content moves or is removed. Orphan-page review then becomes an ongoing architecture habit rather than an occasional cleanup exercise.

Sources