Website problems
Pages nothing links to
A page that no other page on the site links to can still be opened by anyone holding the URL and may well be in the sitemap — and nothing on the site leads to it. Visitors do not find it by browsing and crawlers do not find it by crawling. The causes are unremarkable: a navigation entry removed in a redesign, a campaign landing page, a section left behind by a migration, a category page the content system generates and never links.
Why a sitemap entry does not replace a link
A sitemap says a page exists. Internal links say it matters and what it relates to.
Links also carry context: the anchor text and the surrounding page describe the target in a way a sitemap line cannot.
A sitemap-only page tends to be crawled less often, because nothing signals that it is part of the site's structure.
And for a human visitor it does not exist at all, which is usually the more expensive half of the problem.
Which is why the two are complementary rather than alternatives, and why a page in one and not the other is worth looking at.
How pages become orphans
A navigation entry removed during a redesign while the page stays published.
A campaign landing page created for an external audience and never linked internally, which is deliberate and then forgotten.
Category, tag or author pages generated automatically and never included in any menu.
Pagination linking only a few pages ahead, leaving everything past that reachable only by editing a URL.
A page linked only from another orphan, which is a cluster rather than a single page and hides the most content.
Which findings are false, and why
A crawl reaches what it reaches. A page linked only from a page outside the crawl budget looks orphaned and is not.
Links inserted by script after load are absent from the served markup, so a navigation built entirely client-side can make the whole site look orphaned.
That second case is worth knowing rather than dismissing: a crawler reads roughly what the scan read, so those links are invisible to discovery too.
A page deliberately excluded from navigation is reported as an orphan because it is one, which is correct rather than a false positive.
So the finding is read against the crawl coverage, which is reported alongside it.
What to do with the list
Decide whether each page should exist. A large share of orphans are pages nobody would recreate, and removing them is the right answer.
For the rest, link them from somewhere a reader would actually follow — a parent category, a related article, a relevant section.
Adding a link from an arbitrary page to clear the finding accomplishes nothing: the link has to make sense to a reader.
Where a page is genuinely for an external audience only, leave it unlinked deliberately and keep it out of the sitemap so the two agree.
Redirect rather than delete where the page has inbound links from elsewhere, which a removal would break.
The related structural findings
Click depth, which measures how far a page sits from the entry point and is the softer version of the same problem.
Navigation that changes between pages, which produces orphans on the templates where entries are missing.
Pages linked only from a sitemap, which is the specific shape this finding takes on a large content site.
A page excluded from crawling in the robots file, which is reachable and deliberately undiscoverable — a different decision with a similar appearance.
How to check it yourself
Crawl the site from the home page and compare the pages found against the sitemap.
Pages in the sitemap and not in the crawl are the candidates.
Check whether each is genuinely unlinked or whether the link is inserted by script, by viewing source rather than the inspector.
Look at server logs for requests to pages the crawl did not reach, which shows whether anyone is finding them another way.
Repeat after a redesign, which is when the list grows.
How VeriFixScan detects it
`structure.navigation_ux` measures depth, orphan candidates, breadcrumbs and return-to-home paths from the crawl data already collected.
`structure.navigation` compares navigation across the crawled pages and checks the key pages are linked from it.
`seo.sitemap` reads the sitemap, which is what makes a sitemap-only page visible as a contradiction.
`structure.menu` analyses the primary navigation region, including entries that lead nowhere.
Findings are relative to the crawl, and the coverage is reported alongside rather than implied.
Frequently asked questions
- Is a page in my sitemap still an orphan?
- Yes. A sitemap says a page exists; internal links say it matters and what it relates to. The two solve different halves of the same problem.
- Why is a page I can click to reported as orphaned?
- Usually because the link is inserted by script and is absent from the served markup. That is worth knowing — a crawler reads roughly what the scan read.
- Should I just add links to clear the finding?
- Only links a reader would follow. A link from an arbitrary page clears a report and does nothing for discovery, which was the point.
Sources
Related
VeriFixScan crawls a site and applies its checks to every page it reaches, keeping the evidence behind each finding. Scanning one website is free.
Scan a website