Regular WordPress orphan pages are published pieces of content that receive no useful internal links from the rest of your site. They may still be accessible via their URL, appear in an XML sitemap, or attract some external visits. However, they don’t fit well into your readers’ journey.
The problem isn’t solved by adding links at random. First you need a reliable inventory, then decide the actual role of each URL. Some pages deserve a contextual link. Others should be merged, redirected, or removed from indexing.
What an orphan page really is
A page becomes orphaned when no other content on your domain links to it in an actionable way. Google says every important page should receive at least one link from another page on the site. Standard HTML links, with a tag <a> and an attribute href, also help bots discover URLs.
See Google's best practices on discoverable links : anchor text should clearly describe the destination and fit into relevant context. A vague link like «click here» rarely helps the reader understand what they’ll find.
Note: a link in a menu, archive, breadcrumb trail, or sitemap doesn’t necessarily make an article usefully integrated into your content. Yoast defines orphan content as a page that receives no contextual links from other posts. This distinction is valuable during your audit.
Why audit orphan pages
An isolated URL first creates a human discoverability problem. A reader finishing a relevant article can’t easily move on to that resource, even if it answers their next question.
Internal links also provide context. Google explains that link text and the destination help it interpret relationships between a site’s pages. An XML sitemap supports discovery, but it doesn’t replace a clear link architecture. Google notes a sitemap is a hint for crawling, not a guarantee of indexing or ranking.
So before hunting isolated URLs, make sure your WordPress XML sitemap is consistent. It will serve as a comparison list, not proof that a page is properly connected to your content.
The reliable method: compare three inventories
One tool isn’t enough. A serious audit compares the content WordPress knows about, the URLs declared in your sitemap, and the links a crawler can actually follow on the public site.
1. Export the WordPress inventory
In the admin, list your posts, pages, and public custom post types. For each item note the title, URL, status, and last modified date. Include product pages or downloadable resources only if they should be found in search results.
This list answers a simple question: «What have we published or made public?» It also helps spot old content, drafts accidentally published, and pages created for a finished campaign.
2. List the sitemap XML URLs
WordPress can expose a sitemap index at /wp-sitemap.xml. SEO plugins can, however, generate or replace that file. So check the sitemap actually declared on your site and in Search Console.
Google recommends including the canonical URLs you want to appear in its results. Its documentation on creating and submitting a sitemap also reminds you to avoid listing multiple variants of the same content.
Then compare your WordPress export with the sitemap. A public URL missing from the sitemap deserves a separate check. It isn’t automatically orphaned, but it can indicate an indexing setting, an unexpected canonical, or a content type that’s excluded.
3. Crawl the site like a bot
Use a crawling tool that can traverse your domain and export, for each URL, the number of incoming internal links. Start the crawl from the homepage and include the site’s important sections. Keep navigation links in the report, then distinguish them from links placed in the body of content.
A URL present in the sitemap or WordPress but absent from the crawl is your best candidate for an orphan page. However, check the limits of your audit: a protected page, one disallowed by robots.txt, non-indexable, or only linked after a JavaScript action may require special analysis.
Finally, keep a spreadsheet with these columns: URL, content type, incoming links found, source of the link, intent, useful traffic, decision and action to take. This sheet prevents handling pages one by one without an overall logic.
Don’t fix every URL the same way
An isolated page isn’t always an error. Before making changes, ask whether it still serves a specific intent, whether its content is unique, and whether you want it to be discoverable by search engines and your visitors.
Add contextual links to a useful page
If the page still answers an important question, find two or three pieces of content that naturally precede it in the reader’s journey. Add a link in a sentence explaining why the resource helps them continue.
For example, an article about indexing can point to a page that explains a specific check in Search Console. However, avoid placing a long, unrelated list of links at the end of every article. To choose the right relationships, rely instead on a WordPress internal linking strategy focused on the reader.
A pillar page, a well-structured category, or a starter guide can also serve as an entry point. The goal remains simple: a reader should be able to reach the page because it logically complements what they’re already viewing.
Merge or redirect redundant content
If two pages cover the same question, keep the more comprehensive one or the one that best meets current intent. Transfer useful elements, then create a permanent redirect from the old URL to the retained content when the destination is a true replacement.
Google explains how permanent redirects work : they signal that the new target should become the canonical version. However, don’t redirect an old page to the homepage or to a distant category just to avoid an error. The target must meet the expectation set by the old URL.
Keep a page but remove it from search
Some content should remain available without being offered in results: a thank-you page, a resource reserved for a campaign, temporary documentation, or information intended for a small group. In that case, the noindex may be appropriate if the page remains accessible and you are not trying to have it discovered.
Google states, in its guidelines for blocking indexing with noindex, that the rule must be visible to its crawler to work. So you should not block this URL in robots.txt before the crawler can read its directive. Also see our guide for using noindex in WordPress without removing an important page.
Remove a page that has become unnecessary
Remove content that is no longer useful, that needlessly duplicates another page, or that should no longer be accessible. Also remove its internal links and its URL from the sitemap. If there’s no comparable replacement page, Google recommends returning a proper 404 or 410 status code rather than an unrelated redirect.
Before deleting a URL, check its inbound links, conversions, external mentions, and history in Search Console. That way you avoid removing a low-profile but still useful page.
Verify the result after corrections
Re-crawl after your changes. Each important page should now receive at least one crawled internal link, ideally from closely related content. Also check that redirects lead directly to the correct destination and that noindex pages are no longer in the sitemap intended for indexing.
Repeat this audit after a restructuring, migration, category deletion, or several months of sustained publishing. This will prevent useful content from gradually disappearing behind an overly complex architecture.









