What are orphan pages? How to find and fix them, WordPress included

Google's link guidance states the rule they break: "Every page you care about should have a link from at least one other page on your site." Tools draw the line in different places. Screaming Frog counts as orphaned "any URL where there is no observed linking path from the start point of a crawl (generally the homepage)." Yoast is stricter: a post linked from "the homepage, sitemap, or category and tag pages" but from no article text is, in its words, "still considered orphaned content." The first definition asks whether a page can be found; the second, whether it is woven into the site.

Why orphan pages happen

Few are created on purpose. Ahrefs names the most common cause as "not having processes for site migrations, navigation changes, site redesigns, out-of-stock products, testing, or dev pages." The usual cases:

• A redesign or migration drops a section from the menu, and the pages under it stay published.
• A page is unlinked but never removed: an old offer, a job ad taken off the careers page, a product out of stock.
• The CMS creates URLs nobody links to, such as leftover template or attachment pages.
• New posts nobody links back to. Reviewing its own blog, Yoast found that "recent articles are often orphaned," because nobody went back to add links to them from older posts.
• Links a crawler cannot follow. Google can generally crawl a link only when it is an anchor element "with an href attribute." A page reached only through a script-driven button can look orphaned to a crawler even though visitors reach it.

Why they matter

Search engines discover pages mainly by following links. Google's sitemap documentation puts it plainly: crawlers "crawl the web by accessing URLs found in previously crawled pages," and on large sites "it's more difficult to make sure that every page is linked by at least one other page on the site," so Googlebot "might not discover some of your new pages." A sitemap helps, but it "doesn't guarantee that all the items in your sitemap will be crawled and indexed."

Discovery is only the first cost. Google uses links "as a signal when determining the relevancy of pages," and a page with no internal links gets none of that signal. An orphan may still be indexed through a sitemap or an external link, Screaming Frog notes, but without internal links "they won't be passed internal PageRank." Visitors cannot reach the page either, unless they already have the URL.

Keep the scale in proportion. Screaming Frog calls a small number of orphan pages "common and not generally a big issue"; at scale they "can contribute to index bloat and crawl budget waste."

How to find orphan pages

Every method compares two lists: the URLs that exist, and the URLs a crawler reaches by following links from the homepage. Anything on the first list and missing from the second is an orphan.

1. List the URLs that exist

Collect them from every source you have: the XML sitemap, an export from your CMS, the pages with impressions in Search Console, landing pages in your analytics, and server logs if you can get them. Ahrefs advises using "as many data sources as you have access to," because each one misses something.

2. Crawl the site from the homepage

Run an SEO crawler that starts at the homepage and follows links only. Screaming Frog's SEO Spider and Ahrefs' Site Audit both work this way. Ahrefs offers Site Audit free through Ahrefs Webmaster Tools; Screaming Frog needs a paid licence to crawl a whole site with its sitemap, Analytics and Search Console integrations switched on.

3. Compare the two lists

Crawlers do the comparison once you give them the extra sources. Screaming Frog adds the URLs from your sitemap, Google Analytics and Search Console to the crawl and lists those with no internal link path in an Orphan Pages report. Without a tool, paste both lists into a spreadsheet and filter for the URLs on the first that never appear on the second.

4. On WordPress, check your SEO plugin

Yoast SEO Premium has an orphaned content filter on the posts and pages overview that lists content with no text links pointing to it, and a guided workout for fixing it. Because it uses Yoast's stricter definition, expect it to flag posts that a crawler still reaches through your archives.

How to fix orphan pages

Do not simply link every orphan. Ahrefs warns that "marketers often make the mistake of simply adding internal links to all orphan pages across the board," when some were orphaned on purpose and others should go. Decide page by page, the way a content audit does:

The orphan is	Fix
Useful and meant to rank	Link to it from related pages, ideally ones that already get search traffic, so crawlers find the new link soon
A near-copy of another page	Merge its useful parts into the other page and 301 redirect it
Deliberately unlinked, like an ad landing page	Keep it out of the navigation and add noindex, leaving it crawlable so the tag is seen
Outdated and worthless, with no backlinks	Delete it and let the URL return 404 or 410
Worthless but with backlinks	Delete it and redirect the URL to the closest relevant page

Linking is the fix that matters most, so make the links count: put them in the body of related articles, with anchor text that names the topic, as set out in internal linking. Merging and deleting are content pruning, which has its own checks before anything is removed. If many orphans share a subject, one hub page that links to all of them fixes the set at once, which is the idea behind a content hub.

How to prevent them, including on WordPress

WordPress protects posts by default. As Ahrefs notes, "each time we publish a new blog post, WordPress adds an internal link from our blog homepage and archive." Those archive links keep posts reachable, but they are the weak kind: as posts age they slide deeper into paginated archives, and Yoast does not count them at all. Pages, as opposed to posts, get no archive listing, so a page left out of the menu and never linked from text is orphaned the day it goes live.

Four habits prevent most orphans:

• Link back when you publish. Add a link to each new post from one or two older posts on the same subject, ideally ones that already get traffic.
• Plan redirects before a migration or redesign, then crawl the site afterwards to catch the pages the new navigation dropped.
• On a headless site, build the lists. A custom front end renders only what you build, so the blog index, category pages and related-post links have to exist in its templates. Ahrefs makes the same point about any custom solution.
• Audit on a schedule. Ahrefs suggests running the crawl every month, so new orphans are caught while there are few of them.

How Structura handles this

Structura does not find or fix orphan pages. It does not crawl your site or compare it against your sitemap, and it never edits posts or pages you already published, so it adds no links into them, including links to the posts it writes.

What it controls is the links inside each new post. On paid plans, with internal link optimization switched on, a post links to related posts already published on your site, using their real URLs. On WordPress the candidates are a handful of your published posts that the plugin picks at random, so older posts get picked up over time; on headless sites they are your most recent posts in the same language. On WordPress, new posts also appear in your blog index and archives like any other post; on a headless site, listing them is your front end's job.

So a new post links out from day one but has no links pointing in, beyond the archives, until you add one from an older post. On headless sites with Search Console connected on a paid plan, a post Google still has not indexed two weeks after publication is flagged, and links from your stronger pages are the usual remedy. The blog SEO software page shows what each post includes and what the Search Console checks report.

FAQ