Orphan Pages: How to Find and Fix Them
An orphan page has no internal links pointing to it. People and crawlers following links cannot reach it. Google says every page you care about should have a link from at least one other page on your site. This guide shows how to find orphans, decide which to link, merge or remove, and prevent new ones.
- What orphans are
- 3 ways to find them
- Fix or remove
- Prevent new ones
Home -> Guides -> Post A
Home -> Guides -> Post B
(no links) Post CAn orphan page is one with no internal links to it. Google says every page you care about should have a link from at least one other page, using crawlable a href links and descriptive anchor text. Find orphans by comparing your sitemap or WordPress page list against a crawl and the Search Console Links report. Then link, merge or remove each one.
What an orphan page is
A page that no other page on your site links to. It may exist in your sitemap or CMS, but nothing in your navigation, content or footer points to it. Google’s page does not use the term orphan; this definition is a common one, and Google’s linking guidance applies to it.
What Google says about links
| Topic | Guidance |
|---|---|
| Internal links | Every page you care about should have a link from at least one other page on your site; no ideal number of links per page |
| Markup | Google generally follows only a elements with href; it cannot reliably extract URLs from anchors without href |
| Discovery | Links help Google judge relevance and find new pages to crawl |
| JavaScript links | Crawlable if they use the same anchor markup; check rendered HTML in URL Inspection |
| Anchor text | Descriptive text helps people and Google; empty links are a problem, though title or image alt can be a fallback |
Three ways to find orphans
Sitemap vs crawl
Crawl your site by following links, then compare with your sitemap URLs. Pages in the sitemap but not found by the crawl are orphan candidates (my own method).
Page list vs links
Export your WordPress page and post list, and check each for at least one inbound internal link.
Links report
In the Links report, check internal top linked pages; pages missing there deserve review. It is a sample, so confirm manually.
Decide what to do with each orphan
| Orphan is… | Action (my own framework) |
|---|---|
| Valuable and current | Add internal links from related pages |
| Overlaps another page | Merge into the stronger page and redirect. See keyword cannibalization |
| Outdated | Update it, then link. See update old posts |
| Worthless | Remove, returning 404 or 410, or redirect if a close match exists |
| Should stay private | Leave unlinked, add noindex or protect it |
How to add the links
- Link from topically related pages with descriptive anchors.
- Use real a href links, not scripted spans.
- Add the page to a hub or category page where it belongs.
- Consider adding it to relevant navigation or a related-posts block.
See internal linking and anchor text.
Fix orphans step by step
Export all indexable URLs
From the sitemap and CMS.
Crawl by following links
Record which URLs are reached.
Find the difference
URLs not reached are candidates.
Classify each page
Link, merge, update or remove.
Add internal links
From related pages and hubs.
Prevent new orphans
- Add at least one internal link before or as you publish.
- Link new posts from an existing hub.
- Review internal links when you retire or merge content.
- Run the orphan check regularly, such as quarterly (my own cadence).
Notes for WordPress sites
- Category pages and blog archives link posts automatically, but only a limited number show per page (my own note). See pagination SEO.
- Noindexed archives may stop passing visibility; verify posts have contextual links. See archives.
- Internal link plugins can automate related links.
Troubleshooting
| Symptom | Likely cause (my own diagnosis) | Fix |
|---|---|---|
| Page not indexed, only in sitemap | No internal links | Add links |
| Link added but not crawled | Link not a real a href | Use proper anchors |
| Crawl shows orphan but page is in menu | Menu built with script | Check rendered HTML |
| Found a page with only external links | Still orphan internally | Add internal links |
Checklist
Find
- Sitemap list
- CMS list
- Crawl results
- Links report check
Decide
- Valuable: link
- Duplicate: merge
- Outdated: update
- Worthless: remove
Link
- a href markup
- Descriptive anchors
- From related pages
- From a hub
Maintain
- Link at publish
- Quarterly check
- Review after merges
- Inspect key pages
What Google’s page does not say
It does not define orphan pages or say how Google treats them, whether sitemaps help discovery (the body does not mention them), how pages linked only from other sites are handled, or any minimum number of internal links.
Key terms
- Orphan page
- A page with no internal links to it.
- Internal link
- A link from one page of your site to another.
- Anchor text
- The clickable words of a link.
- Hub page
- A page that links to related content.
Common mistakes
Relying on sitemap alone
No link signals.
Scripted links
Not reliably parsed.
Linking everything to everything
Dilutes context.
Generic anchors
Click here.
Keeping junk orphans
Dead weight.
One-time check
New orphans appear.
Related guides
Orphan page questions
What is an orphan page?
A page with no internal links pointing to it.
Why does it matter?
Google uses links to find pages, and says every page you care about should be linked from at least one other page.
How many links do I need?
Google gives no ideal number; at least one internal link for pages you care about.
Does a sitemap fix it?
Google’s linking page does not say; links remain the recommended approach.
How do I find orphans?
Compare sitemap or CMS lists against a crawl.
Should I delete orphans?
Only low-value ones. Link, merge or update valuable pages.
Do JavaScript links count?
Yes if they use proper anchor markup; verify rendered HTML.
Can anchor text be empty?
Avoid it; title or image alt can be a fallback.
Google’s link guidance comes from the sources. The orphan definition, detection methods, decision framework, WordPress notes, troubleshooting and checklists are my own.