To find an orphan page, compare the URLs you intend to keep with the URLs you can reach through internal links. An orphan may still appear in your sitemap or show up in analytics. The gap is that readers have no ordinary path to it from elsewhere on your site.
Imagine you published a setup guide last year, then removed the only blog post that linked to it. The guide still opens if you have the address. A new customer who needs it would have to know it exists.
Which pages are actually orphaned?
Start with an inventory from your CMS and sitemap. Run a separate crawl starting at your homepage and the entry points a visitor can use. If the crawler imports the sitemap, look at its internal inlink report rather than assuming every crawled URL was found through a link.
Compare like with like. Resolve redirects and group obvious URL variants before comparing counts. Check candidate URLs individually. A zero inlink count can also reflect a limited crawl, an authentication boundary or a link your tool failed to render.
Google's link guidance recommends linking to important pages from elsewhere on your site. For a normal link, use an anchor with an href that points to the intended address.
Where should you add the link?
Pick a page where a reader is likely to need the missing resource. In a fictional example, a feature page explains that customers can export a report. Its next useful link might be Export a scheduled report, placed beside that feature explanation. A generic sitewide footer link would give people less context.
| What you find | What to do |
|---|---|
| A current guide solves a real task | Link from the feature page, help hub or article where that task comes up. |
| Two pages explain the same task | Decide which should be the primary resource before adding links. |
| The URL is an intentionally private utility | Check its access rules and keep it out of public navigation. |
How do you verify the repair?
Open the source page while signed out, follow the link and check the final URL and heading. Then repeat the crawl and confirm it reports the source as an inlink. A working route is a useful outcome by itself. Search visibility takes a separate check.
Log the source URL, target URL and anchor so you can check them after the next redesign. If the discovery came from a larger review, add it to your visibility audit action list and assign someone to verify the change.
How do you check a large inventory without opening every page?
Use a spreadsheet with one row per intended destination. Keep the original URL, final URL after redirects, source inventory and inlink count in separate columns. Match on the final URL only after you confirm the variants represent the same resource. A spreadsheet that drops all query strings up front can hide legitimate pages if the parameters change what a visitor sees.
- Filter to pages you expect people to reach without signing in. Keep intentional exclusions in a separate view.
- Group the remaining rows by template or section. If an entire help category has zero reported inlinks, test the category landing page before editing each article.
- Start with a page that supports a customer task. Find the point in that task where a reader would need the guide and write the link in that context.
For instance, if a report page links to a general export category and that category links to the setup guide, the guide has an indirect route. It may still deserve a direct link if export setup is the most likely next task. Keep the two findings separate in your sheet: no path and path could be easier. They often call for different owners and priorities.



