How to Find Orphan Pages by Joining Your Crawl to GA4 and Search Console
A crawler alone can never find an orphan page. The join that can, the Screaming Frog setup, and how to tell which orphans are worth a link.
An orphan page has no internal links pointing at it, which means a crawler following internal links can never reach it. You cannot find orphans by crawling harder; you find them by comparing the crawl against lists of URLs that came from somewhere else:
- GET FOUR LISTS OF URLS: The crawl (what your links reach), the XML sitemap (what your CMS publishes), Search Console (what earns Google impressions), and GA4 (what records pageviews).
- THE ORPHANS ARE THE DIFFERENCE: Any URL in the sitemap, GSC or GA4 that the crawl never reached is an orphan. In Screaming Frog: connect the APIs, crawl, run Crawl Analysis, then open Reports, then Orphan Pages.
- TRIAGE BEFORE YOU LINK: An orphan earning Search Console clicks is the most valuable page on the list. A filtered parameter URL is orphaned by design. Treating them the same wastes a day.
- THE FIX IS ALMOST ALWAYS A LINK: Link the ones that earn, redirect the ones that are superseded, remove the rest from the sitemap so it stops advertising pages you do not support.
The most expensive orphan is the one already ranking. It is earning clicks with zero internal support, which is the clearest upgrade in technical SEO.
The three-way join this guide performs by hand is what CrawlRaven runs on a schedule: your crawl, your Search Console data and your GA4 data compared on the same URLs, with orphans ranked by what they earn. Here is the manual version. Try CrawlRaven free: 1 site, no credit card →
Here is a puzzle that breaks most technical audits. You want to find pages nothing links to. Your crawler finds pages by following links. So the crawler will never, at any crawl depth or budget, find the pages you are looking for.
This is not a limitation to work around with better settings. It is arithmetic. Orphan pages are defined by their absence from the link graph, and the link graph is the only thing a crawler can see.
The way out is to get a second list of URLs from somewhere that is not your internal links, then subtract.
Why a crawler alone can never find one
An orphan page is a live page with no internal links pointing at it. It can be indexed, it can rank, it can take real traffic. What it cannot do is receive link equity from the rest of your site, or be discovered by anyone navigating it.
Which produces the strange situation this guide exists for: the page is simultaneously invisible to your own tooling and visible to Google. Your crawl says the page does not exist. Search Console says it earned 400 clicks last month.
Nobody creates one deliberately. They accumulate: a campaign landing page published outside the nav, a product retired from the category listing but left live, a template that lost its related-posts module in a redesign, a CMS migration where the link structure did not survive. Every one of those is invisible until you go looking.
The four lists you need
Orphan detection is a set comparison. You need one list of what your links reach, and three lists of URLs that exist independently of your links:
Four lists of URLs. The orphans are what the crawl misses.
Each external source finds a different flavour of orphan, which is why using all three beats using any one:
- Sitemap orphans are pages your CMS publishes and your navigation forgot. Common after a category restructure.
- Search Console orphans are the expensive ones. Google ranks them, people click them, and your site does not link to them.
- GA4 orphans catch what Google never indexed: pages taking email, ad or referral traffic that search cannot see at all.
Doing it in Screaming Frog
Screaming Frog builds this join for you, and its orphan report is the reason most SEOs keep a license. Our Screaming Frog review covers the tool broadly; this is the orphan workflow specifically.
The setup, step by step
- Connect the APIs before you crawl. Configuration → API Access → Google Analytics, and again for Google Search Console. Authorize the account, then pick the right property and date range. This must happen before the crawl, not after.
- Enable sitemap crawling. In the spider configuration, turn on crawling of linked XML sitemaps, or supply the sitemap URL directly so its URLs enter the comparison.
- Run the crawl and let it finish completely. A partial crawl invents orphans, because URLs it simply never got to look identical to URLs nothing links to.
- Run Crawl Analysis. Top menu → Crawl Analysis → Start. This is the step that performs the join, and skipping it leaves the orphan report empty. It is the single most common reason people conclude they have no orphans.
- Open Reports → Orphan Pages. The export lists every URL found by the APIs or the sitemap that the crawl never matched, with a Source column naming where each came from.
Where this workflow trips people up
- An empty report usually means Crawl Analysis never ran. Check that first, before concluding the site is clean.
- Date range matters. A 30-day Search Console window finds fewer orphans than a 12-month one. Seasonal pages hide inside short ranges.
- Property mismatch produces phantom orphans. A GSC property covering a subdomain the crawl never touched will flag every URL on it. Match your API properties to the site you crawled.
- Blocked URLs are not orphans. A page excluded by robots.txt or by your crawl configuration is unreachable for a different reason. Check your robots.txt rules before assuming.
No Screaming Frog license? The method is a set comparison, not a product. Export your sitemap URLs with our sitemap extractor, pull the Pages report from Search Console and the landing pages from GA4, and subtract whatever your crawler reached. A spreadsheet handles a small site fine.
Triage: which orphans actually matter
The first orphan report on a real site returns hundreds of URLs and reads like a disaster. It usually is not. Most of that volume is pagination, filters and parameter URLs that are orphaned by design.
Sort by Search Console clicks and impressions before anything else. That single sort turns the list into a priority order:
Not every orphan deserves a link
| What the data shows | Verdict | What to do |
|---|---|---|
| Earning Search Console clicks | Link it, today | It ranks with zero internal support. Add links from your strongest related pages and watch the position move. |
| Impressions but almost no clicks | Link it, then fix the snippet | Google shows it and nobody picks it. Internal links first, then the title and meta description. |
| GA4 pageviews, no Google impressions | Check indexability | People reach it from email, ads or referrals, but Google is not ranking it. Look for noindex, a canonical elsewhere, or a crawl block. |
| In the sitemap, no traffic anywhere | Decide if it should exist | You publish it and nothing uses it. Either give it a purpose and links, or remove it from the sitemap. |
| Old campaign or superseded page | Redirect it | 301 to the page that replaced it, so any residual links and rankings consolidate instead of evaporating. |
| Paginated, filtered or parameter URL | Usually leave it | Faceted and paginated URLs are orphaned by design in most setups. Confirm the canonical is right, then move on. |
Fixing them without making it worse
Three fixes, matched to what triage told you:
- Link it properly. Not a footer dump. Links from pages that are topically related and already have authority, with anchor text that describes the destination. Two or three good placements beat twenty bad ones, and our internal link analyzer shows what each page currently points at.
- Redirect it. If a newer page supersedes it, a 301 consolidates the residual links and rankings instead of letting them evaporate.
- Remove it from the sitemap. If it should not exist, stop advertising it. A sitemap listing pages you do not link to sends Google a contradictory signal about what matters.
One thing not to do: bulk-link every orphan from a single hub page. It is the fastest way to close the report and the slowest way to help, because a link module nobody reads passes little and can look engineered. Fix the ones that earn.
Why orphans come back
A quarterly orphan audit is accurate on the day you run it and decays immediately, because orphans are created by the events you least want to miss:
- Migrations. The single biggest producer. Link structures rarely survive a platform change intact, which is why the migration checklist treats internal links as a first-class concern.
- Template changes. A related-posts module removed from one template can orphan an entire content section in a single deploy.
- Content pruning. Unpublishing a hub page orphans everything it was the only link to, which is a common side effect of pruning done by page rather than by cluster.
None of those announce themselves. The page keeps loading, Search Console reports no error, and the traffic decays over months rather than dropping in a day. Running the crawl-to-GSC-to-GA4 comparison continuously rather than quarterly is the difference between catching that in a week and finding it in the next audit.
That continuous join is what CrawlRaven does: the same three sources, compared on the same URLs, with the orphans that earn traffic surfaced first. For the wider picture of what the join catches, see why your Search Console and GA4 numbers never agree.
Frequently asked questions
What are orphan pages in SEO?
An orphan page is a page on your site with no internal links pointing to it. It may still be live, indexed and even ranking, but nothing on your own site links to it, so crawlers following your internal links never reach it and it receives no internal PageRank from the rest of the site.
How do I find orphan pages with Screaming Frog?
Connect the Google Analytics and Search Console APIs before crawling (Configuration, then API Access), enable XML sitemap crawling in the spider configuration, run the crawl, then run Crawl Analysis from the top menu. Open Reports, then Orphan Pages. The Source column shows whether each URL came from GA, GSC or the sitemap.
Why can't a crawler find orphan pages on its own?
Because a crawler discovers pages by following internal links, and an orphan page has none. Crawling more deeply or raising the limit changes nothing: the page is unreachable by definition. Finding orphans requires a second list of URLs from outside the link graph, which is what the sitemap, Search Console and GA4 provide.
Are orphan pages bad for SEO?
It depends entirely on the page. An orphaned page that earns Google clicks is a real problem, because it is ranking with no internal link support and would likely rank better with some. An orphaned parameter or filter URL is usually orphaned deliberately and needs nothing. Triage by what the data shows before fixing anything.
Do orphan pages get indexed by Google?
They can. Google may have found the page from an external link, an old internal link, your sitemap, or a previous crawl, and it can stay indexed indefinitely. That is exactly why Search Console is such a useful orphan source: it lists URLs Google knows about that your own internal links no longer reach.
How do I fix an orphan page?
Usually by adding internal links from relevant pages that already have authority, using descriptive anchor text. If the page is superseded, 301 redirect it to its replacement so residual links and rankings consolidate. If it should not exist, remove it from your sitemap so you stop advertising a page nothing supports.
Can I find orphan pages without Screaming Frog?
Yes. The method is a set comparison, not a product: export your sitemap URLs, your Search Console pages, and your GA4 landing pages, then subtract the URLs your crawler reached. Any tool that crawls and exports will do, and a spreadsheet handles the join for a small site.
Why does my orphan pages report list hundreds of URLs?
Almost always pagination, filters and parameter URLs, which many sites orphan on purpose. Before treating it as a crisis, sort by Search Console clicks and impressions. The handful earning real traffic are the story; the rest are usually noise from faceted navigation working as designed.
Does the XML sitemap fix orphan pages?
No. A sitemap helps Google discover a URL, but it passes no internal link equity and does nothing for users navigating your site. A page that only exists in the sitemap is still an orphan in every sense that affects rankings. Sitemap inclusion is discovery; internal links are support.
How often should I check for orphan pages?
Quarterly for a stable site, and always after a migration, redesign or CMS change, which is when orphans appear in bulk. A template that loses a link module can orphan an entire section overnight, and nothing in Search Console will announce it.
15+ years of growing SaaS websites through SEO | Author, 200-Point Audit Checklist
Aditi has spent 15+ years helping SaaS companies scale organic traffic through technical SEO and content strategy. She is the author of the CrawlRaven 200-Point Audit checklist used by agencies and in-house teams to systematically improve search performance.