# Orphan Pages in SEO: How to Find Them Beyond Search Console

> Search Console can list URLs Google knows but cannot confirm orphan pages. Build the candidate list from three sources, then give each URL one verdict.

- URL: https://missiongrowth.io/blog/orphan-pages
- Published: 2026-11-14 · Updated: 2026-11-15
- Author: Furkan Aktaş, Co-Founder, Mission Growth
- Publisher: Mission Growth. Company facts: https://missiongrowth.io/llms.txt

Orphan pages are live URLs that no click path from the homepage reaches. This guide builds the candidate list from several data sources, shows exactly where Google Search Console stops short of confirming one, and ends with a single verdict for every URL on the list.

## What is an orphan page?

An orphan page is a URL that a visitor or crawler cannot reach by clicking from the homepage, even if it is live and returns 200 status. Orphan status is therefore a question of reachability, and a count of links does not answer it. A page can have inbound links and still be an orphan when none of them sits on a path that starts at the homepage.

Take a small site where the homepage links to pages A and B. Pages P and Q link to each other and to nothing else, and nothing reachable links to them. A link counter reports one inlink for P and one for Q, so a filter for zero inlinks skips both.

Click from the homepage and you never arrive at either. P and Q form an orphan island, a group of URLs that point at each other and are cut off from the rest of the site.

Screaming Frog states the same rule in its tutorial. It classifies a URL as an orphan when there is "no observed linking path from the start point of a crawl (generally the homepage)", and it adds that an orphan can be linked from other orphans.

::figure{src="/blog/figures/orphan-pages-1.svg" alt="Flow of links from the homepage to two reachable pages, beside two orphan pages that only link to each other" caption="Orphan pages can link to each other: P and Q each have an inlink, yet no click path from the homepage reaches either." width="720" height="202"}

The shortcut to avoid is "one inbound link means the page is not an orphan". It fails on the island above, and it fails whenever the only linking page is itself unreachable. Google advises at least one inbound link from elsewhere on the site for every page you care about. Read that as a reachability test: a link from a stranded page does not help anyone arrive.

## Orphan pages, dead-end pages and thinly linked pages

A dead-end page has inlinks but no outlinks, an orphan has outlinks but no inlink from a reachable page, and a thinly linked page hangs on one fragile link. Each one needs a different fix, and each shows up differently in a crawl.

| Page type | Inlinks | Outlinks | How it shows in a crawl | What to do |
|---|---|---|---|---|
| Orphan | None from a reachable page | Usually some | Absent from the crawl, present in the sitemap, logs or Search Console | Give it a verdict (see the fix section) |
| Dead-end | One or more | None | Crawled, with no outlinks listed | Add links onward to related pages |
| Thinly linked | One | Some | Crawled, with a single inlink | Add a second link from a stable page |
| Normal | Several | Some | Crawled on a shallow path | Leave it alone |

A page linked only from the last page of a deep archive is thin and still reachable, because a crawler can click its way there. It is fragile, though. If the archive page changes, the only link disappears and the page becomes an orphan overnight.

The dead-end page is the one most often mislabelled as orphaned content. It has no outlinks, so visitors arrive and have nowhere to go. That deserves links added onward. The orphan label belongs to pages with no way in.

Google's advice that every page you care about needs an inbound link from another page applies to all three types. Only the orphan fails it outright.

## Why do pages become orphans?

Pages become orphans when the last link to them is removed while another channel, such as a sitemap, a backlink or an old crawl, keeps the URL alive. That surviving channel tells you where to look for the page.

Google discovers URLs through links on known pages and through submitted sitemaps, so an orphan that still gets found is being kept known by one of those routes or by a link from another site. Matching log URLs against your crawl and sitemap is covered in [log file analysis SEO](https://missiongrowth.io/blog/log-file-analysis).

| Cause | What happened | Surviving channel | Where to see it |
|---|---|---|---|
| Forgotten link at publish | The post went live and nobody linked it | Sitemap entry | CMS post list against the crawl |
| Navigation or category removed | A parent page that linked its children was deleted or hidden | Sitemap, backlinks | Crawl gap, Search Console known URLs |
| Migration leftovers | Old URLs still respond after a redesign | Old crawl, logs, backlinks | Server logs, Search Console |
| Expired or out-of-stock products | The category listing dropped them but the product URL stayed live | Sitemap, backlinks | Sitemap against the crawl |
| Orphan-generating templates | A template or filter creates URLs that nothing links to | Sitemap or old crawl | Crawl gap |
| Links that are not crawlable | Links exist but sit in script handlers a crawler does not follow | Sitemap | Crawl gap against a rendered view |

The migration row leaves a recognisable signature. After a redesign, the old structure often leaves a leftover URL: it still serves a live page, shows up in server logs, and has no link from the new navigation. The redirect map and URL mapping belong to the migration process itself, which our guide on [site migration seo](https://missiongrowth.io/blog/site-migration-seo) covers. Here the leftovers are one source of candidates.

The category case splits two ways. Removing a category page strands its live children, because the category was the link that reached them. Deleting a single post strands nothing, because a deleted post has no page left to be an orphan.

The status code tells you which case you have. A live response means the page still exists and needs a verdict, while a 404 or 410 means it is already gone.

## Do orphan pages hurt SEO?

Orphan pages hurt discovery and internal signals in a way Google documents, but they do not trigger a penalty and a few earn traffic.

The orphan pages SEO question starts with URL discovery. Google finds new URLs when it extracts a link from a known page, as when a category page links to a new blog post, or through a sitemap. Whichever route finds an orphan, the links you add to it need good [anchor text](https://missiongrowth.io/blog/anchor-text), which that guide breaks down by link situation.

Its Search Console help adds that Google needs a way to find a page in order to crawl it, so the page must be linked from a known page or listed in a sitemap.

An orphan can still reach Google. A sitemap makes a URL known without linking it, and a backlink from another site does the same. Search Console cannot separate sitemap-only discovery from crawl discovery, a limit the Search Console section below spells out.

So an orphan in a sitemap can be crawled and indexed, and one that keeps earning backlinks can even rank. What it lacks is the internal link that tells Google the page matters on your own site.

| Status or symptom | What Google documents | Orphan evidence? |
|---|---|---|
| Discovered - currently not indexed | Found but not crawled yet; typically Google wanted to crawl it, expected that to overload the site and rescheduled | No |
| URL missing from a crawl | The crawl never reached it from the start page | Yes, if the URL is live |
| URL in the sitemap only | Known through the sitemap, with no link path | Candidate |

The first row is the common mistake. "Discovered - currently not indexed" is a crawl-scheduling status, a crawl rescheduled to avoid overloading the site. It says nothing about links. A page can carry that status with plenty of internal links, and an orphan can be indexed without ever seeing it.

Measured evidence on the size of the effect is thin. Botify shows one site where orphan URLs made up more than 70% of the pages Google explores, yet only 5% of that site's organic visits came from them. That is one site's example and it should not be generalised.

Some forum threads argue that unlinked pages struggle to rank because a lack of internal connections signals low importance. Treat that as opinion. Google documents the discovery route and the advice to link every page you care about, and it documents no ranking penalty for orphan status.

On cost, orphans that still get requested spend part of your crawl budget. The guide on [crawl budget](https://missiongrowth.io/blog/crawl-budget) explains that mechanism, and one sentence is all this post needs.

## Which orphan pages are fine to leave alone?

Orphan pages are fine when they were never meant for navigation, such as thank-you pages and paid landing pages, provided they are not indexed copies of each other. Expected orphans include newsletter confirmation screens, order confirmations, paid ad destinations, member-only areas and URLs kept live because external links point to them.

Keep them out of results with a noindex tag. A crawler cannot see a noindex tag on a page that robots.txt blocks, so if the URL is already indexed, allow crawling long enough for the tag to be read. Blocking through robots.txt suits URLs that are not indexed.

The risk with intentional orphans comes from Google's spam policy on doorway abuse. It lists two patterns that can describe indexed landing pages nobody links to. One is creating substantially similar pages that are closer to search results than a clearly defined, browseable hierarchy. The other is having multiple domain names or pages targeted at specific regions or cities that funnel users to one page.

That is Google's definition of doorway abuse, and it is not a statement about orphans. Apply it as a reading: if you run city or region landing pages that no menu links to and that are near copies of each other, check them against it before leaving them alone.

If such URLs are also indexed and duplicative, the larger problem is the one our guide on [index bloat](https://missiongrowth.io/blog/index-bloat) describes.

## How to find orphan pages

Finding orphan pages is a set difference: take every URL your other sources know about and subtract the URLs a crawl from the homepage reached. In shorthand, known URLs minus crawled URLs gives the candidate list. A candidate is not yet an orphan, because a source can know a URL for reasons other than a live page, so each one is checked against its status code afterwards.

That is how to find orphan pages without a special tool. Each source sees a different slice of the site, which makes the choice of sources the real decision. The source map below lays out what each one reveals and misses.

::figure{src="/blog/figures/orphan-pages-2.svg" alt="Four-step flow from collecting known URLs to subtracting the crawl, checking status codes and giving each orphan page candidate one verdict" caption="Known URLs minus crawled URLs gives the candidate list, and a status-code check comes before any verdict." width="720" height="233"}

| Source | Reveals | Misses |
|---|---|---|
| XML sitemap | URLs you chose to submit | URLs left out of the file; says nothing about links |
| Search Console | URLs Google knows, linked or not | URLs Google has not met; rows past the cap |
| Google Analytics | URLs that received visits | URLs with no visits |
| Server logs | URLs bots requested | URLs no bot has asked for; requests blocked before the server |
| Backlink data | URLs other sites link to | URLs with no outside links |
| CMS export | Every published post | URLs built outside the CMS |

A sitemap entry makes a URL known and leaves it unreachable, so the sitemap alone is not enough to remove orphan status. Google's help page says a page must be linked from a known page or listed in a sitemap. The sitemap is the second route and the link stays the first. The xml-sitemap guide in this series covers the file and its export. Here the sitemap is one input.

The nine-URL audit below uses illustrative numbers. It is an example rather than a measurement. A sitemap lists 9 URLs and a crawl from the homepage reaches 6 of them, so 9 minus 6 leaves 3 sitemap-only candidates. Search Console shows one more URL that is in neither the sitemap nor the crawl, a Search Console-only URL. That makes 4 candidates in total.

| URL | In sitemap | Reached by crawl | In Search Console | Status | Verdict |
|---|---|---|---|---|---|
| /pricing | yes | yes | yes | Live | Not a candidate |
| /features | yes | yes | yes | Live | Not a candidate |
| /about | yes | yes | yes | Live | Not a candidate |
| /blog/seo-basics | yes | yes | yes | Live | Not a candidate |
| /blog/link-building | yes | yes | yes | Live | Not a candidate |
| /blog/case-study | yes | yes | yes | Live | Not a candidate |
| /blog/migration-notes | yes | no | yes, with impressions | Live | Link from a reachable post |
| /legacy-promo | yes | no | no | Live | 301 to the closest replacement |
| /blog/team-retreat | yes | no | no | Live | 410 |
| /landing/spring-sale | no | no | yes | Live | noindex tag, keep |

Copy those columns into a sheet and add a verdict log: URL, in sitemap, reached by crawl, impressions, status and verdict. One row per URL keeps every decision visible, and the same sheet becomes the record you re-check after the fix.

## Find orphan pages without paid tools

You can find orphan pages without paid tools by exporting your sitemap or CMS post list and subtracting the URLs that a crawl or Search Console shows as linked or known. The free methods, in the order worth trying, cover most small and mid-sized sites.

1. **Export your known URLs.** A sitemap export or a CMS post list gives the first column of the sheet. On WordPress, the posts and pages lists are that export.
2. **Export what Search Console knows.** The Performance report's pages and the Page indexing report give URLs Google has met, with the limits the next section covers.
3. **Run a crawl you can afford.** Semrush's Site Audit lets a free account crawl up to 100 pages, enough for a small site and a sample of a larger one.
4. **Subtract.** Remove every URL the crawl reached from the combined list.
5. **Fill the audit sheet.** Add columns for in sitemap, reached by crawl, impressions, status and verdict.

A free checker comes down to a spreadsheet and a crawl. The Search Console exports cost nothing, the sitemap is a file you already have, and each candidate's status code is one request away.

State the ceiling of whichever crawl you use before trusting a short result. A crawl capped at 100 pages cannot speak for a site of several thousand, so on a large site a full crawl or an API export of Search Console data is the working route.

Site size decides which free route can see every URL:

| Site size | Free route that sees the whole site | Where the free route truncates |
|---|---|---|
| Up to 100 pages | Sitemap plus a free Semrush Site Audit crawl | Nowhere: the free crawl reaches every page |
| Over 100, up to 1,000 pages | Sitemap plus the Page indexing example lists | The free crawl stops at 100 pages, so it covers a sample |
| Over 1,000 pages | Sitemap plus an API export of Search Console data | Example lists stop at 1,000 rows and are not guaranteed complete |

Read your own row before you trust an empty result. On a site of a few thousand URLs, a clean free audit means the tools ran out of rows; it says nothing about the URLs past that limit.

## Find orphan pages in Google Search Console

Google Search Console can list URLs Google knows about, but it cannot confirm that any of them is an orphan. The orphan pages Google Search Console shows are candidates only. Four parts of the console touch the question, and each carries a documented limit that stops it from settling it.

| Tool | Useful for | Documented limit |
|---|---|---|
| Performance report, pages | A list of known URLs that earn impressions | Shows only URLs with impressions, so it needs a crawl list to subtract |
| Page indexing | All known pages, submitted pages or unsubmitted pages | A URL counts as submitted even if crawling also found it; example lists are limited to 1,000 rows |
| URL Inspection | Sitemaps and Referring page fields | The Sitemaps field lists only sitemaps submitted or in robots.txt; the Referring page can be empty or a distant ancestor |
| Links report | Internal links, ranked by most-linked pages | A sample of links, with tables limited to 1,000 rows |

### Performance report pages

The pages in the Performance report are a known-URL source. Export them and subtract the crawl list to see which URLs earn impressions while sitting outside the crawl. This catches orphans that get shown in results.

It cannot catch orphans with no impressions, so it is the first column of the sheet and never the whole list. Google Analytics gives the same kind of list from the visit side, and a landing-page export from it can sit beside this one.

### Page indexing filters

The Page indexing report offers three filters. All known pages shows URLs known to Google whether or not a sitemap lists them, and the other two split submitted from unsubmitted. Unsubmitted pages only looks like an orphan finder, since a URL outside your sitemap that Google knows must have come from a link.

Google's help page breaks that logic. It says a URL is considered submitted by a sitemap even if it was also discovered through some other mechanism, such as organic crawling from another page. So a sitemap URL the crawl also reaches and a sitemap URL known only from the sitemap both land under submitted, and the filter cannot separate them.

Example lists in the report do not necessarily show all URLs with an issue and are limited to 1,000 rows.

### URL Inspection fields

URL Inspection has two fields that look useful. The Sitemaps field lists only sitemaps submitted or in robots.txt, and sitemaps discovered through other means are not listed.

The Referring page field is the more tempting one. Google says that when the value is absent it does not mean that no referring page exists, only that the information might not be available to the tool at that time.

When a value is shown, the referring page might link directly to the URL, or it might be a grandparent or great-grandparent of a page that links to it. An empty Referring page therefore proves nothing, and a filled one does not prove a direct link.

::shot{src="/blog/tools/search-console-url-inspection-product.webp" width="1600" height="1000" alt="Search Console URL Inspection Discovery panel listing the Sitemaps and Referring page fields for an indexed blog post" caption="URL Inspection Discovery panel in Search Console" captured="2026-11-15"}

### Links report

The Links report is a sample. Google says the report does not list every link on your site and shows only a sample, and its tables are limited to 1,000 rows, so they may be truncated on larger sites. The internal table ranks your most-linked pages.

::shot{src="/blog/tools/search-console-links-report-product.webp" width="1600" height="1000" alt="Search Console Links report table of top internally linked pages, with link counts blurred" caption="Top internally linked pages in the Links report" captured="2026-11-15"}

A URL missing from an export of that table is worth checking and proves nothing by itself. A step that treats the export as the list of linked pages needs that caveat, since a truncated sample will omit linked URLs for reasons unrelated to links.

The working recipe follows from the limits. Export pages with impressions, subtract the crawl list, and inspect the remainder one by one. Treat everything Search Console returns as a candidate source and let the crawl decide.

## Find orphan pages with Screaming Frog and other crawlers

Screaming Frog flags an orphan when it finds a URL through a sitemap, Google Analytics or Search Console that has no linking path from the crawl start. The orphan pages Screaming Frog reports are therefore only as complete as its extra sources. Its tutorial says additional URL sources are required: XML sitemaps plus the Google Analytics and Search Console API connections.

### The Screaming Frog recipe

1. Crawl the site from the homepage.
2. Switch on the extra URL sources in the configuration: the sitemap crawl plus the Analytics and Search Console connections.
3. Set the date range for the integrations. Screaming Frog suggests ideally at least a month of data, as with Google Analytics.
4. Run Crawl Analysis from the crawl menu.
5. Open the Orphan Pages report and export it.
6. Check each exported URL's status code and add it to your sheet.

The classification rests on the rule you met earlier: no observed path from the crawl start. Because the tool can only report URLs that an extra source knows, the date range limits what it sees. A URL with no visits in the window and no sitemap entry will not appear.

Semrush's Site Audit also reports orphaned pages, and a free account crawls up to 100 pages. Put that ceiling beside the others.

| Source | Limit that matters | Consequence |
|---|---|---|
| Screaming Frog | Needs sitemaps, Analytics or Search Console as extra sources | A URL no source knows is invisible |
| Screaming Frog integrations | Date range, ideally at least a month | Short windows miss low-traffic URLs |
| Semrush Site Audit | Free accounts crawl up to 100 pages | A sample on larger sites |
| Search Console tables | 1,000 rows | Truncated on larger sites |

Other crawlers define the crawl start and accept extra sources in their own ways, so read each tool's definition of an orphan before trusting its list.

### Why tools disagree

Tools disagree because each makes a different guess about which URLs count, and every false alarm costs an investigation. One small-blog guide reports its own numbers. On one site, a sitemap compared with a Search Console export flagged 45 of 122 posts, and only 2 were real orphans. Dividing 45 by 2 shows the export overstated the problem by 22.5 times.

The same guide counted links on a 232-post travel photography blog two ways. A count of all on-page links turned up 18 orphans. A count restricted to links in the post body turned up 74, because a related-posts box linked the rest. Dividing 74 by 18 gives 4.1 times.

Those ratios are our own derived figures from the guide's numbers, and they come from small blogs. Read them as an illustration of how a false alarm happens, and expect no particular rate on your site.

::figure{src="/blog/figures/orphan-pages-3.svg" alt="Bar chart comparing two audits that overstated orphans, by 22.5 times and by 4.1 times" caption="A sitemap-versus-export compare overstated the problem by 22.5 times, and an in-post-only link count by 4.1 times." width="720" height="198"}

Both false alarms trace back to how a link is defined. A related-posts box counts as a link to a crawler that follows everything, and the in-post-only count treats it as absent. The remedy is the same each time: confirm the URL has no path from the homepage in a crawl before acting on it.

## Find orphan pages with server logs

Server logs find orphans a crawl cannot see, because Googlebot keeps requesting URLs that no page links to any more. Compare the URLs bots requested in the logs with the URLs a fresh crawl reached, and the difference is a list of URLs that something still points at.

Botify separates expected orphans from unexpected ones, and the status code is the quickest test. A URL that still returns a live response and that Googlebot requests is an unexpected orphan, because it serves content nothing links to. A URL that returns 404 or 410 is Googlebot revisiting something you removed, which is expected and usually needs no action.

For example, take a hypothetical log check where Googlebot requested five URLs last month that a fresh crawl never reached:

| URL Googlebot requested | Status | Verdict |
|---|---|---|
| /blog/old-pricing-update | Live, status code 200 | Unexpected orphan: link it from the pricing hub, or 301 it to the current page |
| /landing/spring-sale | 410 Gone | Expected: the page was retired, leave it |
| /docs/v1/setup | 301 Moved Permanently | Expected: the redirect is doing its job |
| /tag/seo-tips?page=7 | Live, status code 200 | Unexpected: a parameter URL nothing links to; noindex it or stop generating it |
| /case-studies/old-client | 404 Not Found | Expected, unless it still has backlinks worth a 301 |

Only the two live rows need work. The other three are Googlebot revisiting URLs you retired, and the status code already tells it so.

Botify's one-site example, the same one from the SEO section, showed orphan URLs above 70% of the pages Google explores. It is a reminder that logs can show a scale of problem a crawl never would, though one site's figures do not predict yours.

This post does not teach the log method. Our guide on log file analysis covers reading bot hits, status codes and crawl waste end to end.

## How to fix orphan pages

To fix orphan pages, give each one a verdict, link, redirect, remove or keep, chosen from its impressions, backlinks, status code and intent. One verdict per URL keeps the audit from stalling on the middle cases. When the verdict is redirect, a [301 redirect](https://missiongrowth.io/blog/301-vs-302-redirect) is the permanent choice, and that page covers how it differs from a 302.

| Impressions | Backlinks | Status code | Intent | Verdict |
|---|---|---|---|---|
| Some | Any | Live | Meant to rank | Link it from a reachable, related page |
| None | Some | Live | Replaced content exists | 301 to the closest replacement |
| None | None | Live | No closest replacement exists | 410 |
| Any | Any | Live | Never meant for navigation | noindex tag, keep |
| Any | Any | 404 or 410 | Already removed | Leave it, check nothing links to it |

Start with the link verdict, because most orphans are pages somebody meant to keep. The linking page must itself be reachable. A link from another orphan only widens the island.

Pick a related page that already gets crawled and put the link in running text, with an anchor that describes the target. The anchor text guide in this series covers that choice. The mechanism behind link value and the audit order sit in the guide on [internal linking and seo](https://missiongrowth.io/blog/internal-linking-strategy). If the orphan belongs to a topic cluster, link it from the hub that the guide on the [pillar page](https://missiongrowth.io/blog/pillar-pages) model describes.

A redirect fits only when a closest replacement exists. The 301 sends visitors and backlinks to the page that now serves the same need, and the 301 redirect guide in this series covers the choice between redirect types. When no replacement exists, a 410 says the URL is gone deliberately.

Conductor asks three questions before deciding: traffic, external links and useful content. It then sends the page to a redirect or to deletion. The table above keeps that logic and adds the 410 versus 301 split by whether a closest replacement exists, the noindex branch for intentional pages, and the branch that links from a reachable page.

Check status code first and traffic second. A URL that already returns 404 needs no redirect, and a URL with backlinks deserves a link or a 301 before any deletion. Write the verdict beside each row of the sheet.

## How to verify the fix

A fix is verified when a fresh crawl from the homepage reaches the URL, and adding the link does not count as proof. Re-crawl and confirm the URL now appears with a crawl depth. A link that sits on a page the crawl never visits changes nothing.

Do not wait for Search Console to confirm. The URL Inspection Referring page may stay empty or show an ancestor after the fix, as the documentation warns, so a stale field is no reason to doubt the link. The sitemap filter in Page indexing will not change either, because it counts a URL as submitted whether or not crawling also found it.

Keep the evidence in your own sheet: the crawl depth, the date of the re-crawl and the verdict. No timing for Google's re-crawl can be promised, so the crawl you run yourself is the proof.

## How to keep new orphans out

New orphans appear at predictable events, so the audit runs after each of them instead of on a calendar alone. An event trigger is a change that can strand a URL, and the check follows the change.

| Event trigger | What to run |
|---|---|
| Publish a page | Confirm a reachable page links to it before it goes live |
| Navigation change | Re-crawl and compare against the previous crawl after every navigation change |
| Category deletion | List the children of the removed category, then relink or remove them |
| Migration | Run the sitemap-minus-crawl subtraction and check logs for leftover URLs |
| Product expiry | Decide 301 or 410 for each expired product URL |
| CMS template change | Re-crawl a sample of URLs that use the template |

A calendar still has a place. A scheduled audit catches drift from edits nobody logged, and the general routine is in our guide on [how to do seo audit](https://missiongrowth.io/blog/how-to-do-seo-audit). The events make the schedule cheap, since most sites need the full subtraction only after something above has changed.

Orphan status is reachability from the homepage, and Search Console can only suggest candidates: its Referring page can be missing, its sitemap filter counts a URL as submitted even when crawling found it, and its example lists stop at 1,000 rows. So build the candidate list from several sources, let a crawl decide, and give each URL one verdict.

Your next step is concrete. Export your sitemap today, run one crawl with Search Console connected, and fill in the six-column audit sheet for the first few candidates before you touch a single link.

## FAQ

### Can an orphan page be indexed?

Yes. Google finds URLs through links on known pages and through sitemaps, so an orphan listed in a sitemap or linked from another site can be discovered, crawled and indexed. What it lacks is an internal link from your own reachable pages, which is the signal that the page matters on your site. The [xml sitemap](https://missiongrowth.io/blog/xml-sitemap) guide covers what the file lists and how to submit it.

### Can an orphan page rank?

It can. A URL that Google knows through a sitemap or a backlink may appear in results, and Botify's one-site example found 5% of organic visits arriving on orphan pages. Google documents no penalty for orphan status. What it misses is the internal link that tells Google the page matters on your own site.

### Does adding a page to the sitemap fix an orphan?

No. A sitemap makes the URL known to Google but does not make the page reachable by clicking. Google says a page must be linked from a known page or listed in a sitemap, and Search Console counts a URL as submitted by a sitemap even if crawling also found it. Add the link, then verify with a crawl.

### How many internal links does an orphan need?

Google advises at least one inbound link from elsewhere on your site for every page you care about, and the linking page must itself be reachable from the homepage. One reachable link ends the orphan status. A second link from a stable page removes the fragile case where one edit strands the URL again.

### Should I delete orphan pages?

Only when status code and traffic support it. A URL with impressions or backlinks should be linked or redirected first. One with neither and no closest replacement can return a 410. Pages never meant for navigation, such as thank-you pages, stay live with a noindex tag. Choose one verdict per URL, then act.

### How often should I check for orphan pages?

Run the check after each event that can create one: publishing, a navigation change, a category deletion, a migration, product expiry or a template change. A scheduled audit on top catches unlogged edits. Re-crawl from the homepage each time and compare the result against the sitemap and Search Console lists.

### Are PPC landing pages orphans?

Usually yes, and usually by design. Paid landing pages are reached by ads rather than navigation, so no reachable page links to them. Add a noindex tag if they should stay out of results. If city or region variants are indexed, check them against Google's doorway abuse wording.

### Is a dead-end page an orphan?

No. A dead-end page has inlinks but no outlinks, so visitors can arrive and then have nowhere to go. An orphan has no inlink from a reachable page. The fixes differ: a dead-end page needs links added onward, while an orphan needs a link in from a reachable page, a redirect, removal or a noindex tag.
