An orphan page is not connected by any internal link identified in the perimeter of your exploration. However, it can exist in a sitemap or receive visits. Compare multiple inventories before concluding, then decide whether the page should be bound, merged, otherwise retained or removed.
Compare available inventories
Compare sitemap URLs, known website pages, useful logs and a crawl starting from the home page. Check that the tool follows the intended languages and domain. A protected page or misinterpreted navigation can produce a false diagnosis. Record where each URL came from to distinguish an isolated page from a limitation of the collection method.
Compare URL sets rather than totals
The number of pages in a sitemap and the number of pages found by an exploration may differ for good reasons. Compare addresses, not just accounts. Harmonize domain variants, settings and redirects according to site policy, without arbitrarily deleting a difference that identifies separate content. Keep the original value so you can revert to a standardization rule.
| Observed presence | working hypothesis | Useful verification |
|---|---|---|
| In the sitemap, absent from exploration | Isolated page or tool limit | Open URL and search internal links |
| In the exploration, absent from the sitemap | Page discovered by navigation | Confirm if it should appear in the perimeter of the sitemap |
| Found in logs but missing from the other inventories | Old address or private access | Review Answer, Origin and Current Utility |
| Accessible only after an action | Dynamic navigation to examine | Check the existence of a shareable destination |
| Old link to a redirect | Indirect inherited course | Update the link to the right destination |
The Role of the sitemap described by Google is to help discover URLs, without guaranteeing their indexing. A complete file therefore does not prove that your library offers a good course. For an agency, a method article can be technically published while remaining almost invisible to the visitor who consults the services.
Understand the role of each page
Open the isolated pages and classify them: old content useful, completed campaign, duplicate, technical page or error. Some pages are not intended to be promoted in public navigation. The right decision depends on their current function. Do not link them all from the footer only to make a tool warning disappear: this link should also help visitors.
Add links in the right context
Look for a page that the reader is viewing just before needing this answer. Add an HTML link to the actual destination, with a descriptive label. Google recommends exploreable links and anchor texts that explain their destination. Also check the category page and nearby items. A sitemap helps to report URLs, but does not replace an understandable reading path.
Fictional example: a migration guide
A useful guide remains after a redesign, but no more pages present it. The team rereads it, corrects its information and links it from the file devoted to the change of CMS. It adds a link to the service concerned when it helps to continue the project. The decision is justified by the usefulness of the guide, and not only by its old traffic.
Choose an entry page that makes the link useful
Take an isolated page and look for when its answer becomes necessary. An article on URL retention can be presented from a CMS change guide. A price and stock check can be linked from a catalog preparation page. This link has an editorial justification; It is not only used to modify an exploration indicator.
- Describe in one sentence the need to which the isolated page still responds. If this need no longer exists, examine its withdrawal rather than an artificial link.
- Choose an entry page and a label that announces what the reader will find. Avoid a series of generic links without context.
- Control the destination and useful return links. A bound page can always lead to a dead end if it does not offer any suitable suite.
- Restart the inventory from the selected public entries and open the route on mobile. Keep the tool boundaries if some links are not interpreted.
For the series of articles on this site, the same principle consists in linking the subjects on the course: audit, measurement and improvement of an offer, or documentary base, evaluation and human relay. This choice can be checked in local navigation; It does not show a gain in ranking. The Selection of long tail questions Then helps to decide if a response is missing or only better access to existing content.
A connected and properly served URL may remain missing from an external index. Then examine the Diagnosing unindexed pages explored Instead of adding endless links. Access, utility and selection by the engine remain distinct findings.
Check the complete user journey
Restart the exploration and open the links on mobile. Check the destination, the absence of a redirection string and the consistency of the anchor text. Keep the removed URLs and their treatment decision. A page that has become accessible again may still require editorial work. Integrate this control into your Organization of the network around the services to prevent new content from remaining isolated.