Are orphan pages bad for SEO? Mostly yes, but not for the reason usually given. Google does not punish a page for having no internal links. The problem is quieter: a page nobody links to is hard for visitors to reach, slow for search engines to discover, and receives none of the authority your other pages pass around. If it was worth publishing, it is now worth less than it should be.
The opposite case matters as much. Plenty of orphans are pages that should not exist at all: expired campaign landing pages, test pages, thin tag archives left behind by a migration. For those, adding links is the wrong fix.
What an orphan page is
Screaming Frog’s tutorial on finding orphan pages gives the working definition: an orphan page “cannot be found by crawling the internal links of a website from the start page”. It may still be live, indexed and listed in your sitemap. What it lacks is a path from the rest of the site.
That definition explains why orphans are invisible to the usual audit. A crawler follows links. If no link points at a page, the crawler never arrives, so the page never appears in the crawl report. You cannot spot what is missing from a list by reading the list.
Orphans tend to come from ordinary site management rather than mistakes anyone remembers making. A navigation redesign drops a section. A category is deleted and the posts inside it keep their URLs. A landing page is built for a paid campaign and never linked from the main site by design. Pagination changes so that older posts fall off the end of every archive.
Are orphan pages bad for SEO in practice?
The honest answer depends on which kind of orphan you have. Internal links do three jobs: they help crawlers discover URLs, they pass authority between pages, and they tell search engines and readers which pages you consider important. An orphan gets none of the three.
Discovery is the smallest of the problems if the page is in your XML sitemap, because search engines can find it there. But a sitemap entry says only that a URL exists. It says nothing about how the page relates to the rest of the site, and it passes no authority. A page that is discovered but unsupported is a common route into reports like crawled, currently not indexed.
The received wisdom says every orphan must be rescued. That is wrong for a large share of them. If a page was orphaned because nobody needed it, linking it back into the site spends internal authority on content that does not deserve it. The audit is only useful if it ends in a decision for each URL.
How to find orphan pages
Because a crawl cannot see orphans, you find them by comparison. Take every source that knows a URL exists, take the list of URLs your crawl reached through links, and look at the difference. Screaming Frog’s method uses three sources alongside the crawl.
| Source | What it knows | Orphans it surfaces |
|---|---|---|
| XML sitemap | Every URL you have told search engines about | Pages you still submit but no longer link to |
| Google Analytics (organic segment) | Landing pages that received organic visits | Pages people still arrive at from search |
| Search Console | Pages with impressions in Google Search | Pages Google shows but your site does not link to |
Each source catches a different set. The sitemap finds pages you are still promoting. The two traffic sources find pages that are earning something without help, which are usually the most valuable orphans to recover.
Find orphan pages with Screaming Frog
The tool runs the comparison for you once the sources are connected. The sequence in the tutorial is short:
- Connect the sources. Add your XML sitemap to the crawl configuration and connect Google Analytics, using the organic traffic segment, and Search Console.
- Crawl the site from the start page as normal.
- Run Crawl Analysis once the crawl finishes. This populates the three “Orphan URLs” filters, one for each source.
- Export the Orphan Pages report, which combines the three filters into one list.
Using the organic segment matters. Without it, the analytics list fills with URLs that only ever received referral, email or paid visits, which tells you little about search.
Link it, merge it or remove it
The export is a list of candidates, not a list of problems. Put it in a spreadsheet and give every URL one of three outcomes.
| If the page | Do this |
|---|---|
| Should rank and has no better equivalent | Link it in from relevant pages: its category, a hub, related articles |
| Overlaps a stronger page on the same topic | Merge the useful content and 301 redirect the orphan |
| Is expired, thin or a leftover test | Remove it, or noindex it if it must stay live |
When you link a page back in, do it from where a reader would expect to find it. A single link from the footer technically ends the orphan status and does very little else. A link from the category page and two or three related articles puts it back into the structure. Our guide to internal linking for SEO covers how to choose those source pages and anchors.
For merges, use a permanent redirect so the old URL’s signals consolidate to the page you keep; 301 vs 302 redirects explains why the code matters. For removals, the same judgement applies as in any content pruning exercise: remove what has no traffic, no links and no purpose, and keep a record of what you cut.
The limits of an orphan audit
Every method here depends on the sources it compares. A page that is not in your sitemap, has had no organic visits and shows no impressions in Search Console will not appear in any of the three filters. Those are often the most neglected pages on the site, and the method is blind to them. A server log or a full export of URLs from your CMS will catch some of what the three sources miss.
The crawl itself also has to be right. If the crawler is blocked from a section, cannot render links built with JavaScript, or is stopped by a crawl limit, perfectly well-linked pages will show up as orphans. Check a handful of results by hand before acting on the whole list. If a supposed orphan is plainly linked from a live page, the crawl configuration is the problem, not the page.
Finally, treat the audit as recurring rather than a one-off. Orphans are produced by normal publishing: redesigns, deleted categories, archive pages that only show the latest posts. Running the comparison after every structural change catches them while the decision is still easy. More on site structure sits in the link building archive.
Frequently asked questions
Are orphan pages bad for SEO?
They are not penalised, but they receive no internal authority, are harder to discover and are harder for visitors to reach. Whether that matters depends on whether the page deserves to rank.
How do I find orphan pages?
Compare a crawl of your internal links with URLs from your XML sitemap, organic landing pages in Google Analytics and pages with impressions in Search Console. URLs in those sources but not in the crawl are orphans.
Can an orphan page still be indexed?
Yes. Search engines can find it through a sitemap or links from other sites. Being indexed does not mean it is supported by the rest of your site.
Should I add internal links to every orphan page?
No. Link in the pages that should rank, merge and redirect the ones that overlap a stronger page, and remove the rest.
The takeaway Orphan pages cost you quietly rather than through a penalty. Find them by comparison, then give each one a decision: link it in, merge it or remove it.
