Orphan pages: how to find and fix them
No page the crawler reached links to this URL, so it was found only through the sitemap. Search engines use internal links to find pages and judge their importance, and visitors cannot browse to a page nothing links to. Link to it from a relevant page, or, if it should not exist, redirect it or take it out of the sitemap.
Updated 28 September 2026
- Severity
- Warning
- Issue type
orphan-page- How the audit flags it
- Checked once the crawl has finished, because it needs the whole link graph. A 2xx page is flagged when no other crawled page links to it and no crawled URL redirects to it. The start URL is never flagged. Any
<a href>in the server HTML counts as a link, includingnofollowones. If the link graph was too large to store in full, the check is skipped rather than guessed. - How to check
- Site crawl only. Needs the site's full link graph to know that nothing links here.
Why orphan pages matter
Google uses links to find new pages and as a signal of relevance. A sitemap tells it a URL exists, but a page that the site itself never links to is a page the site is saying nothing about. Such pages tend to be crawled less often and rank weakly, whatever their content.
Orphans are also a sign of drift: a campaign page left live after the campaign, a product removed from the catalogue but not from the sitemap, a blog post dropped from pagination by a category change.
When an orphan is not really an orphan
The audit sees the HTML your server sends, not the page after JavaScript runs. Google can find links that scripts add, as long as they are real <a href> elements, so a page linked only from client-rendered navigation or a search widget can be an orphan to the audit and not to Google. That is still worth fixing: server-rendered links reach every crawler, including AI crawlers that do not run JavaScript.
If the audit stopped at its page budget, pages that link to a URL may not have been crawled, and the URL can look orphaned when it is not. Run a larger audit before retiring anything.
Landing pages that only receive paid or email traffic are orphans by design. If they should not rank, add noindex and remove them from the sitemap. If they should, link them.
How to fix it
Go through the list and put each page in one of three groups.
- Should rank: link to it from the pages most related to it, with anchor text that says what it is. A hub or category page is the natural home, plus a contextual link from one or two articles.
- Replaced by another page: 301-redirect it to the replacement and remove it from the sitemap.
- Should not exist: return a 404 or 410 and remove it from the sitemap.
Then fix the cause, so the list does not grow back. Sitemaps generated from the database, rather than from what the site links to, are the usual source. Related-content blocks, category pages and breadcrumbs are the usual cure.
Orphans can only be found by crawling the whole site, so there is no single-page check for this. The free SEO checker can confirm that a page you have just linked is live and indexable.
Fix it with a coding agent
Connect Claude Code, Cursor or Codex to IndexZero's MCP server, open your site's repo, and paste:
Run a site audit of example.com and wait until it completes. Read the orphan-page issues and put each URL in one of three groups: should rank, replaced by another page, or should not exist. For pages that should rank, suggest two pages on the site that should link to each one and the anchor text to use. Then find where the sitemap is generated in this repo and tell me why these URLs are in it. Don't change anything until I've approved the groups.
Behind that prompt the agent calls run_site_audit, polls get_audit_status until the crawl completes, and reads get_audit_issues with issueType: "orphan-page". Your repo is where the fix happens: IndexZero reads your site and never changes it.
Frequently asked questions
- Does Google index orphan pages?
- It can, if it finds them through a sitemap or a link from another site. They tend to be crawled less and to rank weakly, because the site gives no internal signal that they matter.
- Is a page in the sitemap enough?
- It helps discovery. It does not replace internal links, which tell search engines how the page relates to the rest of the site and pass it some of the site's authority.
Audit the whole site
Find every page with this issue
An agent connected to IndexZero's MCP server can crawl the whole site, read the issues of one type, find the templates in your repo and fix them, then re-crawl to confirm. The crawl itself spends no credits; only the optional Lighthouse sample does. The free plan includes the MCP server, audits of up to 50 pages, and 2,000 credits a month.
Related issues
- Redirect chains: how to find and fix themHow chains build up across migrations, what each extra hop costs, and how to collapse them to one redirect.
- Thin content: how to find and fix itWhat a low word count does and does not tell you, the client-side rendering trap, and whether to expand, merge or noindex a thin page.
- SEO issues and how to fix themEvery check the site audit runs, grouped by severity.