Orphan Pages
An orphan page is a URL on your site that has no internal links pointing to it from other crawlable pages — so users and search engines can't reach it through normal navigation.
Start here
- Export your full URL list and cross-reference it with crawl data to find orphans.
- Not all orphans are bad — check intent before adding links.
- Add contextual internal links, not just sitewide nav changes.
- Set a recurring audit to catch new orphans early.
- Use Search Console's 'Pages' report to spot pages with no internal links.
Let's break down what orphan pages actually are, when they matter, and how to stop making the same mistakes I did.
What I'd do first
- Run a crawl with Screaming Frog or Sitebulb to get a full URL list.
- Cross-reference that list with your XML sitemap, Google Analytics pages, and Search Console.
- Flag any URL that appears in your sitemap or analytics but has zero internal links pointing to it.
- Check each orphan — is it intentionally hidden (thank-you page, staging, old redirect)? If not, add contextual links from relevant pages.
- Set a recurring audit (monthly or quarterly) to catch new orphans before they pile up.
Plain-English take
Think of your website like a house. Internal links are the hallways and doors. An orphan page is a room with no door — you can't walk into it from anywhere else. Even if you put a sign outside (the sitemap), people and search engines still can't get there without a door. The fix is simple: add a door (a link) from a room that people already visit.
When it actually matters
- You have a content library — blog posts, guides, or product pages that you want indexed and ranking.
- After a site migration — old URLs often get orphaned if redirects are missed.
- During a campaign launch — landing pages or promo pages that aren't linked from the main nav.
- When you use tag pages — auto-generated tag archives can become orphans if no one links to them.
- If you're doing a content audit — orphan pages are a sign that your internal linking strategy has gaps.
What I got wrong
- Assuming the sitemap was enough. I used to think if a page was in the XML sitemap, Google would find it. Nope — sitemaps are hints, not guarantees. Without internal links, discovery is unreliable.
- Treating every orphan as a problem. Some pages are meant to be hidden — like thank-you pages after a form submission. I wasted time trying to link to those.
- Fixing with sitewide nav only. I'd add a link in the footer or header, but that's not contextual. A link from a related article is way more valuable for both users and SEO.
- Ignoring migration orphans. After a redesign, I forgot to check for old URLs that weren't redirected. They sat there for months, unlinked and unindexed.
Next step
Quick answers
Can a page be in the XML sitemap and still be an orphan?
Yes. A sitemap is a hint to search engines, not a guarantee of discovery. If no internal links point to the page, it's still an orphan.
Are all orphan pages bad for SEO?
No. Some pages are intentionally orphaned — like thank-you pages, staging content, or old redirect targets. The problem is when you want a page indexed but it has no internal links.
Sources
Primary documentation is linked directly. Anything commercial is marked nofollow.
- Google Search Central — Primary Google documentation for crawl discovery, indexing, internal linking, sitemaps, and canonicalization.
- Screaming Frog — Widely used technical SEO reference for finding orphan pages via crawl, sitemap, GA, and Search Console integration.
- Conductor Academy — Clear practitioner explanation of orphan-page definition, discovery workflow, and fix workflow.
- Botify Blog — Technical SEO source covering orphan pages from a crawlability and site-discovery perspective.
Notes from Callum Bennett.