How to Find Orphan Pages in WordPress Using Content Suite’s Built-In Crawler
An orphan page is a live, published URL on your WordPress site that has zero internal links pointing to it, and the fastest way to find every one of them is running a full crawl with a tool like Content Suite’s built-in crawler rather than clicking around your site by hand.
Your site can look completely normal from the dashboard — traffic reports show numbers, pages load fine — while a chunk of your published content sits with no path leading to it from anywhere else on the site. Google may have indexed those pages years ago and simply lost interest since. This post walks through what orphan pages actually are, why they cost you more than people assume, how to run a proper crawl with Content Suite, and what to do once you’ve got the list in front of you.
What actually counts as an orphan page?
An orphan page is a URL that returns a normal 200 status and loads fine, but has no internal links pointing to it from anywhere else on your site — no menu item, no related-posts widget, no in-content mention. That’s a different problem from a 404. A 404 means the page is gone; an orphan page is very much alive, it just has no friends. Search engines lean heavily on internal links to discover and judge the importance of a page, so a page with zero internal links is quietly telling Google it doesn’t matter much, even if it’s some of your best work. Orphans usually pile up from boring, ordinary causes — a redesign that drops old category pages, a retired nav menu whose landing pages stay put, or a blog post that gets homepage placement for two weeks and then never gets linked to again.
Why does it actually matter if a few pages go unlinked?
It matters because orphan pages waste crawl budget, dilute your site’s link structure, and are often pages you spent real time and money creating. On a WordPress site with around 600 published posts built up over several years, it’s genuinely common to find anywhere from 30 to 80 orphan pages once you run a proper crawl. That could be a batch of location pages for local SEO, a set of comparison posts, or a few cornerstone guides that used to live in a menu that got redesigned away — all losing rankings slowly and silently with zero equity flowing to them. There’s also a crawl-efficiency angle: Google allocates a finite amount of attention to every site, and sites with messy internal linking tend to get crawled less thoroughly. Cleaning up orphans isn’t just about individual pages — it’s about making the whole site easier for search engines to read.
How do I set up the crawler and run a scan?
You run it the same way you’d run any other tool inside Content Suite — install the plugin, open the Site Crawler tab, and click Start. Here’s the process end to end:
- Install and activate the plugin through Plugins > Add New, or manually if you downloaded the zip directly.
- Open the Content Suite dashboard and find the Site Crawler tab, listed alongside the content and keyword tools rather than buried in settings.
- Click Start Crawl. The tool works through your published posts, pages, and custom post types, following internal links the way a search bot would. On a site with a few hundred pages this usually takes two to ten minutes; sites with a few thousand URLs will take longer.
- Open the Orphan Pages report once the crawl finishes — a filtered view of every URL published in your database that was never reached by following a link from anywhere else on the site.
The mechanism behind it is simple: the crawler compares everything WordPress has actually published (pulled straight from the database, so nothing hides) against everything it can reach by clicking through links starting at your homepage, sitemap, and menus. Anything in the first list that never shows up in the second gets flagged. That comparison is the whole trick, and it’s exactly why a manual “click around the site” audit almost never catches everything.
How do I know the crawl actually caught everything?
Compare the crawler’s total URL count against your published post count in wp-admin before you trust the report. If your site uses password-protected staging areas, aggressive caching, or a firewall that challenges bots, the crawler can get blocked partway through and report a smaller site than you actually have. If the numbers look wildly off from your expected post count, something interrupted the crawl — whitelist the crawler or temporarily pause an overly strict security plugin and run it again.
How do I read the orphan report without wasting time on the wrong pages?
Sort by traffic and backlinks first, not by publish date. The report lists each orphan URL with publish date, word count, and — the genuinely useful column — whether it still gets organic traffic or has any backlinks according to the data Content Suite pulls in. Not every orphan deserves the same reaction. A five-year-old page with decent traffic and a couple of backlinks that just lost its internal links is an emergency worth fixing today. A thin, 200-word page from 2017 with zero visits ever is a completely different situation, and probably belongs in the trash rather than the rescue pile.
What should I actually do with each orphan page I find?
What you do depends on why the page went orphaned and whether it still has value. Here’s a quick way to triage the list:
| Orphan type | Signal | Action |
|---|---|---|
| Forgotten high-value page | Has traffic and/or backlinks | Add contextual internal links now, consider main nav or footer placement |
| Outdated but still relevant | Some traffic, stale content | Refresh the content first, then link to it from newer posts |
| Thin or redundant | Little or no traffic, overlaps with a stronger page | 301 redirect into the stronger page |
| Dead weight | No traffic, no purpose (old test page, abandoned draft) | Delete and return a 410, or redirect to a relevant hub |
Say you run a mid-sized home services blog with about 350 published posts. A crawl flags 41 orphans. Sorting by traffic, three old “best water heaters” comparison posts are still pulling a combined 400 monthly organic visits despite zero internal links — easy wins: update the year and pricing, add them to a buying-guides menu, and link to them from newer related posts. The other 38 are mostly dead tag archives and abandoned drafts with no traffic — those get redirected or deleted in an afternoon. That’s a realistic, unglamorous cleanup session, and it moves the needle more than the effort suggests. For a broader once-over of thin, stale, or unlinked content beyond just orphans, running the same site through NetoTraffic Content Suite gives you a fuller picture of what’s dragging on your rankings.
How often should I re-run the orphan check?
Monthly, or right after any significant site change, is the realistic cadence. The common mistake is running one big cleanup, feeling good about it, and never checking again — six months later new orphans have already formed from posts that weren’t linked properly, a menu redesign, or a category restructure that quietly cut old pages loose. Since the crawler lives inside the same plugin you’re probably already using for content work, re-running it takes a few minutes and catches problems while they’re small, rather than letting them compound for another two years.
What else do people usually ask about orphan pages?
Does an orphan page still show up in Google’s index even with no internal links?
Yes, often it does, especially if it was linked to at some point in the past or is included in your XML sitemap. Google can keep an old page indexed for a long time after all internal links to it disappear, but its rankings usually decline gradually as it loses relevance signals from your site’s link structure.
Will removing a page from my sitemap fix the orphan problem?
No. A sitemap entry isn’t an internal link, so removing one doesn’t change your site’s actual link structure. The real fix is adding genuine contextual links from other pages on your site, which is exactly what the crawler is checking for in the first place.
How is this different from just checking Google Search Console’s coverage report?
Search Console tells you what Google has crawled and indexed, but it doesn’t clearly show which of those pages have zero internal links pointing to them from your own site. That’s a structural detail only a site-side crawl like Content Suite’s can map out accurately.
Can a brand-new post become an orphan right after I publish it?
Yes, and it happens more than people expect. If a post only gets linked from a homepage feed or a temporary promotion block, it can drop out of every internal link path within weeks once that placement rotates away, turning into an orphan almost immediately.
Should I track how much traffic comes from the links I add to rescued orphan pages?
It’s worth doing, especially if you’re also running paid traffic to the same site — tagging your links and checking how to filter Netotraffic visits in GA4 helps you separate the lift from internal linking fixes from any traffic you’re buying separately.