An orphan page is a page on your website that no other page on your website links to. It might be a landing page built for a past campaign, a product that dropped out of its category, a blog post that slipped off the paginated archive, or a page created by a plugin that nobody remembers adding. Visitors cannot click their way to it, and search engines have a harder time finding it, understanding it and deciding it matters.
Orphan pages are one of the most common issues we find in technical audits, and one of the easiest to fix once you can see them. The hard part is the finding, because by definition a normal site crawl, which follows links, will never reach a page that has no links pointing to it.
This guide explains why orphan pages hurt SEO, the data sources you need to compare to find them, a step-by-step process to decide what to do with each one, and the mistakes that cause them to come back.
Key Takeaways
- An orphan page has no internal links from any other page on the same site, so users and crawlers cannot reach it by browsing.
- Google says every page you care about should have a link from at least one other page on your site.
- You find orphans by comparing a link-based crawl with lists of URLs from your XML sitemap, Search Console, analytics and server logs.
- Each orphan needs a decision: link it, merge and redirect it, noindex it, or remove it.
- Prevention is about process: templates, navigation, pagination and content workflows that always link new pages.
What Is an Orphan Page?
A page is orphaned when it exists and returns content, but no internal link points to it. External backlinks do not change that status: a page with a dozen links from other websites but zero links from your own site is still an orphan from a site-structure point of view.
It helps to separate orphans from a few look-alikes:
| Type of page | Internal links | Typical cause | Is it a problem? |
|---|---|---|---|
| Orphan page | None | Removed from menus, old campaigns, CMS quirks | Yes, if the page matters |
| Weakly linked page | One or two, deep in the site | Content buried in archives or pagination | Often; it is hard to reach and gets little link value |
| Dead-end page | Has incoming links, but no outgoing links | Thin templates, PDFs | Minor UX issue |
| Intentionally unlinked page | None by design | PPC landing pages, thank-you pages, test pages | No, if it is noindexed or not meant for search |
The last row matters. Not every orphan is a mistake. A paid search landing page or an order confirmation page can be deliberately kept out of navigation. The goal is not to have zero orphans at any cost but to make sure every page you want found in search is properly linked.
Why Orphan Pages Hurt SEO
Search engines discover most pages by following links. Google's own documentation on crawlable links is direct about it:
“Every page you care about should have a link from at least one other page on your site.”
— Google Search Central, SEO link best practices for Google
When a page breaks that rule, several things go wrong:
- Discovery is slower or depends on the sitemap alone. A URL in your XML sitemap can still be found, but a sitemap is a hint, not a vote of importance.
- No internal link signals. Google uses links as a signal of relevance. With no internal links, the page receives no anchor text context and no share of the authority flowing through your site.
- Weaker indexing. Pages that look unimportant are more likely to end up as "Discovered – currently not indexed" or "Crawled – currently not indexed" in Search Console. Our guide to the Page Indexing report explains these statuses.
- Lost users and conversions. A useful page that nobody can browse to is wasted content, and a forgotten outdated page that still gets search traffic can show wrong prices or offers.
Google's sitemap documentation also notes that on large sites it is harder to make sure every page is linked by at least one other page, which is exactly why orphans pile up on ecommerce stores, publishers and sites that have been through a redesign.
What Causes Orphan Pages?
- Navigation changes or redesigns that drop old sections from menus.
- Products that are out of stock or removed from categories but left live.
- Blog archives that only link the newest posts, with older posts reachable only through deep pagination or not at all.
- Campaign or seasonal landing pages built outside the main structure.
- Site migrations where old URLs keep resolving instead of redirecting (see our website migration checklist).
- CMS side effects such as tag pages, attachment pages or staging copies that get published.
- Internal links that point to a redirecting or broken URL, so the live destination effectively has no direct link.
How to Find Orphan Pages: Step by Step
The method is always the same: build a list of every URL that a link-following crawl can reach, build a second list of every URL that is known to exist, and compare them. URLs in the second list but not the first are your orphan candidates.
- Crawl the site. Use a crawler such as Screaming Frog, Sitebulb or the Semrush Site Audit tool, starting from the homepage and following internal links only. Export all indexable HTML URLs that return a 200 status.
- Export your XML sitemap URLs. Every URL in your sitemap is a page you are telling search engines matters. Read our XML sitemaps guide if you are not sure where yours lives.
- Export URLs from Google Search Console. In the Performance report, export pages that received impressions over the last 16 months. Also export examples from the Page Indexing report, including indexed pages.
- Export landing pages from analytics. In GA4, pull the landing page report for a long date range. Pages that receive visits but are not in your crawl are strong orphan candidates. Our GA4 guide shows where this report lives.
- Add server log data if you have it. Logs show every URL Googlebot actually requests, including ones nobody remembers. See our guide to log file analysis.
- Normalise and compare. Make protocols, trailing slashes and case consistent, remove parameters you do not care about, then use a spreadsheet lookup or the crawler's built-in orphan report to list URLs found in sources 2 to 5 but not in source 1.
- Check each candidate's status. Re-crawl the candidate list in list mode to confirm which return 200, which redirect and which are already gone.
Most desktop crawlers can automate steps 2 to 6 by connecting your sitemap, Search Console and GA4 accounts during the crawl and then reporting URLs that were found only in those sources.
Data sources compared
| Source | What it reveals | Limitation |
|---|---|---|
| Site crawl | Everything reachable through internal links | Cannot see orphans by definition; it is the baseline |
| XML sitemap | Pages you have declared important | Only as good as the sitemap generator |
| Search Console | Pages Google knows about and shows in search | Performance exports cap rows; low-traffic pages may be missing |
| GA4 landing pages | Pages that real visitors land on | Pages with no visits will not appear |
| Server logs | Every URL bots and users request | Needs access and processing; can be large |
| CMS database export | Every published page or product | May include drafts or private items |
How to Fix Orphan Pages
Once you have a verified list, sort each URL into one of four buckets. Be honest about value: linking a thin, outdated page just to clear an audit warning does not help anyone.
| Situation | Action | Notes |
|---|---|---|
| Valuable, current page that should rank | Add contextual internal links | Link from relevant hub pages, categories and related articles with descriptive anchor text |
| Outdated page with backlinks or traffic | Update it, or merge into a better page and 301 redirect | See our guide to 301 vs 302 redirects |
| Page needed for users but not search (PPC, thank-you) | Leave unlinked and add a noindex tag | Remove it from the XML sitemap |
| Page with no value, links or traffic | Remove it (404 or 410) | Remove it from the sitemap and any redirects pointing to it |
When you add links, think about where the page belongs in your structure rather than dropping a link into the footer. A good orphan fix places the page inside a topic cluster, links it from its parent category or pillar page, and links out to related pages. Our internal linking guide covers anchor text and link placement, and our post on website architecture shows how to plan a structure that keeps important pages within a few clicks of the homepage.
If you redirect, point each URL to the closest relevant equivalent and avoid stacking redirects on top of older ones. Our guide to redirect chains and loops explains why.
Common Mistakes
- Trusting the crawl alone. A crawl tool that only follows links will report zero orphans on a site full of them unless you connect other data sources.
- Linking everything from the footer or an HTML sitemap. It technically removes the orphan flag but provides little context or user value.
- Linking pages that should be retired. Reconnecting thin or duplicate pages can dilute your site and create keyword cannibalization.
- Forgetting the sitemap. Removed or noindexed orphans often stay in the XML sitemap, sending mixed signals.
- Using JavaScript-only links. Links must be real
<a href>elements to be reliably crawlable, as covered in our JavaScript SEO guide. - Treating it as a one-off. Orphans return every time products, campaigns or templates change.
How to Prevent Orphan Pages
- Add an "internal links added" step to your publishing checklist for every new page.
- Make sure category, tag and archive templates link to every item they contain, and use crawlable pagination.
- Use breadcrumb navigation so every page links back up its hierarchy.
- Run a scheduled crawl with sitemap and Search Console connected monthly, or after every major release.
- Include orphan checks in your regular SEO audit and in migration QA.
Related Guides
- Redirect Chains and Loops: How to Fix Them
- Search Console Page Indexing Report: Every Status Explained
- IndexNow: What It Is and How to Use It
Frequently Asked Questions
Are orphan pages bad for SEO?
Orphan pages you want to rank are a problem, because search engines struggle to discover them and they receive no internal link signals. Orphans that are deliberately hidden and noindexed, such as PPC landing pages, are fine.
Can Google index an orphan page?
Yes. Google can find an orphan through your XML sitemap, external backlinks or a manual submission. But indexing is not guaranteed, and a page with no internal links looks less important than well-linked pages.
Does adding orphan pages to the sitemap fix them?
No. A sitemap helps discovery, but the page still lacks internal links, context and link value. Add relevant internal links as well.
How often should I check for orphan pages?
Monthly is a sensible default for active sites, and always after a redesign, migration, CMS change or large product update.
What is the difference between an orphan page and a dead-end page?
An orphan page has no incoming internal links. A dead-end page has incoming links but no outgoing links, so users and crawlers have nowhere to go next.
Conclusion
Orphan pages are a quiet leak: useful content that search engines and visitors cannot easily reach, or forgotten pages that still show up with outdated information. Compare your crawl against your sitemap, Search Console, analytics and logs, decide what each orphan deserves, and build linking into your publishing process so they do not come back in 2026 and beyond. If you would like our team to run a full crawl-based audit and fix your site structure, see our SEO services or request a free quote.
