Orphan pages: what they are, how to find them and how to fix them to improve your SEO
Translated from the Spanish original. Leer en español
AI-generated voices. This episode is in Spanish. Duration: 6:02.
A page can be published, work correctly and still sit outside the routes through a website. The server knows where it is. Someone starting at the homepage may have no way to reach it.
An orphan page is a page that cannot be reached by following internal links from a crawl's starting point, usually the homepage. Finding it means comparing the URLs discovered by that crawl with other sources, such as a sitemap, a content management system or Search Console. Then you need to decide whether it belongs in the website or has already served its purpose.
Adding links to every URL in a spreadsheet is not the answer. First, check what exists and what it is for.
What orphan pages are and how they differ from other issues
The defining issue is the missing internal route, rather than a complete absence of traffic or links of any kind.
Screaming Frog defines orphan pages as pages that cannot be found by crawling internal links from the starting page. Orphan pages can even link to each other: a connected group can remain separate from the rest of the website.
Several situations look similar but need different checks:
| Situation | Meaning | What to review |
|---|---|---|
| Orphan page | Cannot be reached through the internal route being crawled | Inventory, links and the page's purpose |
| Deep page | Can be reached, but takes several steps | Whether the route makes sense for its users |
| Unindexed page | Is not in Google's index at the time of the check | Crawling, content, directives and canonical selection |
| Old URL returning 404 | Does not serve an existing page | Whether it should be gone or has a relevant replacement |
If you cannot see all the columns, scroll the table sideways.
A URL in a sitemap can still be orphaned in terms of internal links. An indexed page can be orphaned too. Discovery through another source does not create a route inside the website.
The finding depends on your review's scope. A crawl restricted to one directory, with exclusions or without correctly representing navigation, can miss links that do exist. Check how you searched before calling a page orphaned.
Why orphan pages matter even if Google already knows the URL
Discovering an address and giving it a place within a website are different things.
Google uses links to discover pages and understand their relevance. It recommends that every important page should have a link from at least one other page on the website, in useful context.
A sitemap helps with discovery but does not guarantee crawling or indexing. It does not give a visitor a route from a question to a service, category or related explanation either.
The review should therefore go beyond asking whether a page appears on Google. Can someone find it from a page where they would reasonably need it?
This does not turn every orphan page into a penalty. Google distinguishes discovery, crawling and indexing. Adding a link does not guarantee a position. The task is to improve a real connection, not trigger an automatic reward.
How to find orphan pages by comparing crawl data with other sources
Compare a map of routes with an inventory of addresses. A crawler that only follows links cannot discover content disconnected from those links through that same route.
Start with these sources:
- A crawl from the homepage, with suitable scope and settings.
- The current XML sitemap.
- Published pages in the content management system.
- URLs with data in Search Console or analytics, where available.
The comparison produces candidates, not a verdict. Historical URLs, redirects and malformed addresses may appear in an inventory without being pages worth recovering.
How to find orphan pages with Screaming Frog
The orphan-page tutorial combines sitemaps, Google Analytics and Search Console. The complete workflow described by the tool requires a licence; it should not be presented as entirely free.
Prepare the sources before crawling:
- Configure linked XML sitemap crawling or specify the relevant sitemap.
- Connect the Analytics and Search Console sources you intend to use.
- Where appropriate, enable crawling of newly discovered URLs from those integrations.
- Finish the crawl and run Crawl Analysis.
- Review the Orphan URLs filters and Reports > Orphan Pages.
These names follow the tool's documentation. Settings matter: finding a URL in an integration does not necessarily mean it was added to the crawl queue.
For a manual file comparison, keep the internally discovered URL list separate from URLs supplied by the sitemap or the CMS. Record the source and the current response for each candidate. Retain the original URL strings while normalising variants for comparison.
My Screaming Frog guide covers the broader audit workflow. Here the goal is narrower: find what the internal route did not reach.
Is a Search Console export enough to find orphan pages?
No. It is an additional source, not a complete website inventory.
A page may exist without recording impressions during your chosen period. Google also documents performance-data and export limits. A URL missing from that file does not prove that the page does not exist, or tell you whether it has internal links.
The clue works in the other direction: a URL with activity that is absent from the crawl deserves a check. Open it and review its current state. Historical data is not proof of what happens today.
What to check before fixing a possible orphan page
Before adding links, confirm that the page exists, that the diagnosis is correct and that its purpose is still relevant.
- HTTP status: does it serve content, redirect or return an error?
- Final address: is this the intended URL or an old variant?
- Indexability: is there a noindex directive, a block or a canonical pointing elsewhere?
- Content: does it meet a current need or duplicate another page?
- Route: is the link missing, or did the crawler fail to interpret it?
- Use: who should reach the page, and from which content?
For the technical link check, Google recommends an HTML a element with an href attribute. An interaction responding to a click is not always a link that Google can reliably extract.
When rendering is uncertain, inspect how the link is delivered and displayed. Do not declare a page orphaned solely because it was absent from a misconfigured crawl.
How to decide which orphan pages to link, update, redirect or remove
Choose according to the page's purpose, rather than trying to make an alert count reach zero.
| Finding | Action to consider | Follow-up check |
|---|---|---|
| Useful, current but disconnected content | Add links from related pages | Check the route and destination |
| Useful page with outdated information | Update it, then integrate it | Check that it meets the current need |
| Content moved or consolidated elsewhere | Redirect to a relevant replacement | Check that the replacement answers the same need |
| Retired page without an equivalent | Return a proper 404 or 410 | Stop promoting it as current content |
| Resource that should stay accessible but not appear in search | Consider noindex for its purpose | Allow Google to crawl and read the directive |
If you cannot see all the columns, scroll the table sideways.
Google advises against redirecting many old URLs to irrelevant destinations, such as the homepage, to hide errors. For removed content with no replacement, a 404 or 410 can be the correct response.
Do not use noindex as a synonym for deletion or a solution to internal linking. The directive controls indexing; Google needs access to the page to read it. It does not replace a review of the page's purpose and navigation.
My article about improving, merging or removing thin content separates that editorial decision from the technical repair. An orphan page can contain good content; a well-linked page may still need substantial revision.
How to connect orphan pages through internal links
On a page where the destination helps someone continue their task. Not everything belongs in the main menu or footer.
A related guide can introduce a supporting explanation. A category can provide access to a relevant resource. A service page can answer a question before someone contacts the business.
My Spanish guide to internal links and their purpose covers those format choices. The aim here is to restore a useful route, not add a decorative link that nobody understands.
The text should explain the destination too. As I discuss in the article on anchor text, the phrase and link need to fit together. Repeating an exact keyword everywhere or adding unrelated recommendations is unnecessary.
After the change, crawl again from the same starting point and check the route. If the crawler now finds the page through internal links, that isolation has been corrected within the scope reviewed. It does not prove that Google has indexed it or that rankings will improve.
Frequently asked questions about orphan pages
Can an orphan page be indexed?
Yes. Google may know it from a sitemap, an external link or a previous crawl. A missing internal route does not automatically erase that knowledge.
Should every orphan page be recovered?
No. Some are retired content, variants or resources with a specific purpose. First establish what they are and whether they should remain available.
Does a link from another orphan page solve the problem?
Not necessarily. If both remain outside the route starting at the homepage, the group is still disconnected from that route.
How many links does a page need to stop being orphaned?
It needs an actual internal route from the starting point being analysed. There is no universal number that guarantees rankings. Google's guidance does not set an ideal number of links per page either.
Does a lack of traffic prove that a page is orphaned?
No. Traffic and internal linking measure different things. A page with no visits may be linked, and an orphan page may receive traffic through other routes.
How to document an orphan-page review and its changes
A list of checkable decisions, rather than an export of alerts alone.
- URL and the source that revealed it.
- Current response, final destination and content purpose.
- Reason to keep, update, merge or remove it.
- Linking page, where a new link is appropriate.
- Change made and date checked.
- New crawl result, kept separate from indexing status.
This review can form part of an SEO audit: locate the problem, assess its importance and agree the repair. The linked service description is in Spanish. An overlooked useful guide and a campaign that ended long ago do not need the same action.
To finish the coffee
A page does not need a link simply to reassure a tool. It needs a place in the website if it still has something useful to offer.
Finding orphan pages is an opportunity to make that decision again: keep, update, merge or remove. Then check that the website's routes reflect the decision.
Sources last checked: 13 November 2026.
Alejandro Castillo Cantón
