How to find and fix orphan pages in WordPress

Why orphan pages quietly hurt you

An orphan page is a published post or page with no internal links pointing to it from the rest of your content. It can still sit in your sitemap, but nothing on the site actually links a reader (or a crawler) to it.

That matters for three concrete reasons:

• Discovery. Internal links are how both readers and crawlers move through a site. A page with no inbound links leans entirely on the sitemap and external links to be found — a weaker position. Google has been explicit that a sitemap is a hint, not a guarantee of crawling; pages it can’t reach by following links get crawled less often, if at all.
• Link equity. Internal links pass authority between your own pages. An orphan receives none of it, so even a genuinely good post can stay invisible in search.
• Reader journeys. There’s no contextual path into the content. People who’d find it useful never stumble onto it, which shows up as a page with impressions but almost no clicks — or no impressions at all.

The sneaky part: orphans accumulate over time. Your best older posts slowly become orphans as you stop linking back to them, and new posts go up without anything pointing to them yet. It’s rarely one big mistake — it’s drift. On a site that publishes weekly, a year of that drift can leave a real chunk of the archive effectively unlinked.

The template-link trap

Here is the framing almost every orphan-page guide gets wrong, and it’s the reason most audits quietly fail.

Your header menu, footer, sidebar, “recent posts” widget, “related posts” block, and category archives all generate internal links — on every page, automatically. A crawler counts those links. So when you run a generic crawl and look at “pages with the fewest inbound links,” almost nothing shows up as a true zero. Every post has the footer linking to it, or appears in a category archive, or rode the “recent posts” widget for a week. The tool reports “0 orphans” and you move on, convinced the site is healthy.

It isn’t. For SEO purposes, those template links barely count.

Why do contextual links carry the weight? Three reasons, and they’re worth internalising:

• Placement signals topical relationship. A link inside a paragraph about, say, sourdough hydration tells Google the two pages are about the same thing. A footer link to your privacy policy tells it nothing.
• Boilerplate links get discounted. Search engines have decades of experience ignoring sitewide navigation noise. A link that appears identically on 800 pages is treated very differently from one a writer placed deliberately in a sentence.
• Widgets are temporary. A “recent posts” link disappears the moment you publish the next post. It was never a durable path into the content.

So the practical definition you’ll work from for the rest of this guide is: an orphan is a published, indexable URL with zero in-content inbound links — regardless of how many menu, footer, or widget links point at it. Hold onto that. It changes which pages you’ll go fix.

Step 1 — Find your orphan pages

You need one number for every published URL: the count of in-content internal links pointing to it. Below are three ways to get it, from most thorough to fastest. The recurring trick is the same in all of them — exclude template links so you measure the real signal.

Method A — Screaming Frog (free up to 500 URLs, most thorough)

Screaming Frog is the standard crawler for this, and the free tier handles small-to-mid sites (500 URLs). The steps:

1. Crawl your site: paste your domain into the bar and hit Start. Let it finish.
2. The fast path: open the Bulk Export menu → Links → All Inlinks. That gives you a spreadsheet of every internal link on the site, with a Link Position column (Header / Navigation / Content / Footer / Sidebar) on recent versions.
3. In the spreadsheet, filter the Link Position column to Content only. Now build a count of how many content links point to each Destination URL (a pivot table on the destination column does it). Any published URL that appears zero times in that filtered list is a true orphan.
4. Alternatively, work interactively: click any URL in the crawl, open the Inlinks tab at the bottom, and read the Link Position of each inbound link. If they’re all Navigation/Footer/Sidebar, it’s an orphan.
5. Reconcile against your sitemap. Use Mode → List to crawl your sitemap.xml, or in Configuration → Spider → Crawl enable XML sitemap crawling, then compare. Any URL that’s in the sitemap but the regular crawl reached only via the menu is exactly the kind of page you’d otherwise miss.

This is the most reliable manual approach and it costs nothing. The downside: the template-link filtering is fiddly, and you’ll want to repeat the whole thing every quarter.

Method B — Google Search Console (free, signals not certainty)

Search Console won’t hand you a literal orphan list, but it surfaces the symptoms, and it’s already watching your live site:

• Open Indexing → Pages. Scan the “Crawled — currently not indexed” and “Discovered — currently not indexed” buckets. Pages that land here despite being decent content are often orphans: Google found them (usually via sitemap) but sees little reason to index them, partly because nothing internal vouches for them.
• For any suspect URL, use the URL Inspection tool and read “Referring page” / how Google discovered it. If the only discovery path is the sitemap, that’s a strong tell.
• In Performance, sort by impressions. Pages with near-zero impressions that you’d expect to perform are worth checking for inbound links.

Treat GSC as the second opinion that confirms what the crawl found, on the pages Google actually cares about.

Method C — The sitemap-vs-crawl diff (free, fastest sanity check)

The quickest way to catch the worst orphans without any paid tool: take the list of URLs in your XML sitemap (every published post) and subtract the list of URLs a crawler reaches by following only in-content links. Whatever’s left is your orphan candidate list. You can do the crawl side in Screaming Frog with header/footer/sidebar link positions excluded, or with any crawler that lets you ignore boilerplate regions. It’s a blunt instrument, but it finds the genuinely unlinked pages fast.

For a wider rundown of options — analytics, log files, and crawler configuration — see how to find orphan pages on a website.

Step 2 — Fix them with relevant internal links

For each orphan, the fix is to add a small number of contextual inbound links — links from inside related posts, pointing to the orphan. The principles first, then a fully worked example so this isn’t abstract.

• Relevance over volume. Find 2–3 genuinely related existing posts and link from them to the orphan. Two strong, on-topic links beat ten weak ones. Past three or four good contextual links, returns flatten quickly.
• Anchor text taken from the real sentence. Use the natural wording already in the sentence the link sits in — not “click here,” and not your target keyword bolted in awkwardly. The anchor should read like it was always there.
• Mid-content placement. Put the link where the topic actually comes up in the body — ideally in the first half, where the reader is still engaged. Don’t bolt links into the intro, a call-to-action, or the middle of a list where they break the flow.
• Link both directions. Add a couple of outbound links from the orphan to related posts too, so it’s woven into the topic cluster on both sides, not just rescued from one.

A worked example

Say your crawl turns up an orphan: a post titled “How to Store Fresh Sourdough So It Stays Crusty”. It has the footer and a category-archive link, but zero in-content inbound links. Here’s the actual fix, start to finish.

Find the 2–3 sources. You search your own archive for posts where storing bread would naturally come up, and find three good candidates:

• “A Beginner’s Guide to Baking Sourdough at Home” (high-traffic pillar post)
• “Why Your Sourdough Crust Goes Soft” (closely related, troubleshooting)
• “Meal-Prep Bread: Baking Once, Eating All Week”

Write the links into sentences that already exist. The point is to add a link to a sentence, not to add a sentence for a link. In the beginner’s guide, there’s already this line:

Before: Once your loaf has cooled completely, it’s ready to eat — though how you store it makes a real difference to the crust.

After: Once your loaf has cooled completely, it’s ready to eat — though how you store it makes a real difference to the crust.

The anchor is a phrase that was already in the sentence and describes the destination exactly. No keyword stuffing, nothing added. In the “crust goes soft” post, the existing line “the most common culprit is how the loaf is stored overnight” becomes the link, with how the loaf is stored as the anchor. One more from the meal-prep post and the orphan now has three contextual inbound links from genuinely related pages.

Close the loop. From inside the (formerly orphan) storage post, add one or two outbound links back to the pillar and the troubleshooting post. Now it’s a node in the cluster, not a dead end.

That’s the entire fix: three sentences edited, no new content written. A pass like this across a handful of orphans is some of the highest-leverage on-page SEO you can do in an afternoon.

When an orphan doesn’t matter

Being honest about this saves you wasted effort: not every orphan is a problem, and chasing a zero-orphan count is the wrong goal.

• Intentionally noindex pages. Thank-you pages, checkout confirmations, gated download pages, login screens — you don’t want these ranking, so being orphaned is correct. Exclude anything marked noindex from your audit entirely.
• Utility and legal pages. Privacy policy, terms, contact. A footer link is genuinely all they need; they don’t require contextual links and you shouldn’t manufacture them.
• Landing pages with their own traffic source. A page you drive paid or email traffic to, deliberately kept out of the site’s normal navigation, is “orphaned” by design. Leave it.
• Tag/archive and paginated URLs. Often these should be noindex anyway; don’t pour internal links into them to chase a clean report.

The pages that matter are your indexable, content-bearing posts and pages — the ones you want to rank. Filter the rest out before you start fixing, or you’ll spend an afternoon solving a problem you didn’t have.

Step 3 — Fix broken internal links while you’re in there

The same audit is the right moment to catch broken internal links. After slug changes, deletions, or migrations, internal links quietly rot into 404s. They waste link equity and erode reader trust — and they’re easy to spot in the same crawl you just ran.

In Screaming Frog, filter the crawl by Response Codes → Client Error (4xx), then for each broken URL open the Inlinks tab to see which posts link to it. Update the link to the correct URL, or set up a 301 redirect if the page genuinely moved. It’s cheap, fast, and pure SEO hygiene.

A repeatable workflow

Don’t over-engineer this. How often to re-audit depends on cadence: a site publishing a few posts a month is fine quarterly; a daily-publishing site wants a monthly pass. The loop:

1. Re-crawl and pull the All Inlinks export, filtered to content-position links.
2. Filter out noindex and utility pages so you only see real orphans.
3. Fix each new orphan with 2–3 relevant contextual links, anchored to sentences that already exist.
4. Fix or redirect any 4xx internal links.
5. Resist the urge to over-link — relevance is the whole game.

If you publish often and this pass keeps slipping, the same audit can be automated safely — suggestions you approve and can undo, not silent bulk edits.

FAQ

How many internal links does an orphan page need?

Two or three good contextual links from genuinely related posts is plenty to bring a page back into the cluster. There’s no magic number, and stuffing in eight links doesn’t help more than three — relevance and placement matter far more than count.

Does a link from my menu or footer fix an orphan?

Not really. Sitewide template links are heavily discounted by search engines because they appear identically on every page. An orphan needs in-content links — placed inside the body of related posts — to actually pass meaningful signal. That’s the whole reason generic crawls under-report orphans.

How often should I re-audit?

Quarterly for most sites; monthly if you publish daily. The practical trigger is “after every batch of new posts,” because that’s when fresh orphans appear — new posts go live before anything links to them.

Do orphan pages hurt SEO directly, or is it indirect?

Mostly indirect. Google won’t penalise you for having orphans, but those pages get crawled less, receive no internal link equity, and have no contextual path for readers — so they tend to under-perform or stay unindexed. Fixing them removes a ceiling rather than lifting a penalty.

Should I worry about orphaned tag, category, or noindex pages?

No. Exclude anything you’ve set to noindex, plus utility pages (privacy, contact) and deliberate standalone landing pages. The audit is only about indexable, content-bearing pages you actually want to rank.

The takeaway

Orphan-page audits fail when you trust a raw crawl that counts menu, footer, and widget links as “inbound.” Measure in-content links only, exclude the pages that are orphaned on purpose, and fix the rest with two or three contextual links anchored to sentences that already exist. Do that once a quarter and your archive stays discoverable, crawlable, and connected — no new content required.

---