An orphan page is a page on your site that nothing links to. Search engines struggle to find it, no authority reaches it, and you probably do not know how many you have. Here is how to find them, decide which are worth rescuing, and fix them properly.
Most site owners can name their best pages and their worst pages. Almost nobody can name their invisible ones. Orphan pages accumulate silently on every site that has been running for more than a year or two, and they are usually discovered by accident — during a migration, or when someone finally runs a proper crawl. On a 200-page site, finding twenty of them is not unusual.
What an orphan page actually is
An orphan page is a page with no internal links pointing to it from anywhere else on your site. It may still exist, still be published, still be in your sitemap, and still be reachable if you know the URL. What it lacks is any route in from the rest of the site. Worth distinguishing from two things it gets confused with:
A dead-end page has incoming links but no outgoing ones. Different problem, much less serious.
A deep page requires many clicks to reach but is still linked. Not orphaned — just badly positioned. Anything more than three or four clicks from the homepage is worth reviewing, but it is a different fix.
Why orphan pages are a real problem
Crawl discovery suffers. Search engines find pages primarily by following links. A page in your XML sitemap may get crawled, but sitemap-only discovery is weaker and slower than link discovery, and recrawl frequency drops accordingly. A page crawled twice a year is re-evaluated twice a year.
No authority reaches them. Internal links are the pipes that move earned authority around a site. An orphan has no pipes. Whatever external links your site has accumulated, none of that value arrives here.
No topical context. Search engines partly understand a page by what links to it and with what anchor text. An orphan has none of that supporting signal — it has to stand entirely on its own content. The link building for beginners guide covers how links and anchors build that context.
Users cannot find them. The obvious one, frequently forgotten. If nothing links to the page, the only visitors are people arriving from search or from an external link. Every internal path to a conversion is closed.
Where orphan pages come from
They are rarely created deliberately. Six common origins:
- Site redesigns. A new template drops a navigation section or a hub page, and everything that was linked from it becomes stranded
- Deleted category or hub pages. Removing an index page orphans everything it linked to at once — this is the single most common cause of orphaning in bulk
- Old campaign landing pages. Built for a specific promotion, linked from ads only, never integrated into the site
- Pagination decay. On blogs, older posts fall off page one, then off page five, and eventually the only route is a paginated archive that crawlers traverse reluctantly
- Migrations. URLs change, internal links are updated inconsistently, and some pages lose all inbound routes
- CMS quirks. Pages published outside the normal template flow, or product variants generated programmatically without being linked from anywhere
How to find them
Orphan detection is harder than it sounds, and the reason is structural. A crawler starting at your homepage and following links will never reach an orphan — that is what makes it an orphan. Any method that works has to compare two lists: pages that exist, and pages that can be reached.
The manual route. Export every URL from your XML sitemap into a spreadsheet. Export every URL Google has indexed from Search Console. Export every page receiving sessions from Analytics. Then export your internal links report and match the lists against each other. Anything appearing in the first three and missing from the fourth is a candidate. That works. It is also three exports, a match formula, and an hour of reconciling URL formats that do not quite agree — trailing slashes, parameters, protocol variants. Then you do it again next quarter, because orphans accumulate continuously. There are desktop crawlers that automate the comparison, and they are capable tools. They are also software you install, configure, connect to two APIs, and run on a schedule you have to remember. For a 200-page site that is a disproportionate amount of setup for a report you need four times a year.
The instant route. Linkexchange includes internal linking intelligence free, and orphan page discovery is one of the built-in reports. It runs against your actual WordPress install — it already knows every page you have published and every internal link between them, so there is no crawl to configure and no lists to reconcile. You open the dashboard and the number is there, alongside weak pages, dead ends, broken internal links, and authority flow. The analysis costs nothing. Working through the fixes by hand is the same job described below, just with the finding step already done; bulk apply handles them in one click on the paid tier. That difference matters more than it sounds, because the reason most sites have never run this check is not that it is difficult. It is that it is set-up work, and set-up work does not get repeated. The website traffic
Not every orphan deserves rescuing
This is the step people skip, and it turns a useful audit into a month of pointless work. Sort what you find into four buckets.
Rescue. Genuinely useful pages that lost their route in. Old guides that still hold up, service pages that got dropped from navigation, anything with existing external links or measurable traffic. These get internal links added.
Consolidate. Thin pages covering subjects you have written about better elsewhere. Merge the worthwhile content into the stronger page and 301 the old URL. This is usually the largest bucket on an older blog.
Delete and redirect. Expired campaign pages, obsolete announcements, duplicate content. 301 to the closest relevant page — never to the homepage as a default, which tells search engines nothing and frustrates users.
Leave alone. Some pages are supposed to be unlinked. Thank-you pages, checkout confirmations, gated content landing pages, internal utility pages. These should typically be noindexed rather than linked. A useful filter: if the page has existing external links, always rescue rather than delete. Deleting a page with inbound links throws away authority you already earned — and earning replacements is considerably harder than routing what you have, as the how to get backlinks guide makes clear.
Fixing them properly
Adding one link from a sitemap page is not a fix. Route them the way you would route any page.
- Link from topically related content, in body text, using descriptive anchors. Two or three contextual links from relevant articles beats a dozen from an archive listing
- Link from pages that carry authority. Check Search Console’s Top linked pages, and prefer routing from there — an orphan linked only from other weak pages is barely improved
- Add outbound links from the rescued page too. Integration is bidirectional; a page that receives links but gives none is a dead end
- Update the sitemap if the page was missing from it
- Request indexing in Search Console for high-value rescues, to shortcut the recrawl wait
Expect movement within a few weeks on pages that were already close to ranking. A rescued page with existing external links can move quickly, because the authority was always there and simply had no route to reach it.
On the volume problem. Two or three orphans is an afternoon. Forty is a project, and it is where most audits stall — the finding was quick and the fixing is not. This is where the free analysis stops being the whole answer. Linkexchange suggests which specific pages should link to each orphan, based on topical relationship and which of your pages actually carry authority, so you are approving suggestions rather than working out every route yourself. Bulk apply commits them in one click on the paid tier. Whether you do that or place the links by hand, the standard is the same: contextual, in body text, from pages that have something to pass.
A worked example
A 180-page B2B site, five years old, two redesigns behind it.
The audit finds 23 orphan pages. Sorted, they break down like this:
- 9 old blog posts stranded when the category structure was simplified in the last redesign. Six are thin and outdated — consolidate into two stronger pieces. Three still hold up — rescue
- 5 campaign landing pages from webinars in 2023 and 2024. No traffic, no external links, no ongoing relevance — delete and 301 to the closest evergreen page
- 4 service sub-pages dropped from the navigation when the menu was condensed. All four have commercial value — rescue, urgently
- 3 thank-you and confirmation pages — correctly unlinked. Noindex them and move on
- 2 old case studies that between them hold 14 referring domains. These are the most valuable find in the audit — rescue immediately and route links from them to current service pages, because they have earned authority sitting idle
The work: 9 pages rescued with two or three contextual links each, 6 consolidated, 5 deleted with redirects, 3 noindexed. Roughly three hours.
The most valuable finding was not the orphan count. It was the two case studies holding 14 referring domains and passing that authority nowhere. Those had been earning links for years into a closed room. That pattern is common enough to be worth checking for specifically: sort your orphan list by external links before you sort it by anything else.
Preventing the next batch
Audit quarterly. Orphans accumulate continuously, and a quarterly check keeps the list at a manageable size rather than producing a hundred-page project every two years. This is the habit that fails first when the audit is an afternoon of exports, and holds when it is a dashboard you open — which is the practical case for having the report sit inside WordPress rather than in a tool you have to remember to run.
Audit immediately after any redesign or migration. These are the two events that create orphans in bulk, and the damage is cheapest to fix while the changes are fresh.
Add an internal linking step to your publishing checklist. When a new article goes live, link to it from at least two existing pages. This single habit prevents most future orphaning, and it takes two minutes per post.
Be careful when deleting hub pages. Before removing any index, category, or resource page, check what it links to and rehome those links first.
The sequence, whichever route you take
Find them. Sort them into rescue, consolidate, delete, or leave. Route the survivors properly, from topically related pages that carry authority. Then check again next quarter, because the next batch is already forming. The finding step is the one that stops people, and it is the one worth removing friction from — an audit you can run in a minute gets run, and one that takes an afternoon of exports does not. That is what the free internal linking tools in Linkexchange cover: orphans, weak pages, dead ends, broken internal links, and authority flow, reported against your live site rather than assembled from exports. The authority to fix most of this is already on your site. It is just not reaching the pages that need it.
