The idea, in plain English
Start here.
Site architecture is how pages are organized and connected. An orphan page has no incoming internal page links in the scope you have checked. To investigate orphans, compare an independent URL inventory with a link-based crawl, check the crawl’s limits and inspect candidate pages before choosing a fix. A sitemap can help discovery but does not replace a useful reader route.
Imagine a useful size guide that opens from a bookmark but has disappeared from the product pages. It still exists; shoppers simply have no obvious route to it. This lesson turns a list of pages into a map of journeys and shows why a missing crawl result is a clue to investigate, not a deletion instruction.
A few words you’ll meet.
OPEN WHAT YOU NEED ↙Site architecture
The organization of pages and the links that let readers and crawlers move between them.
Orphan candidate
A known URL missing from a particular link-based crawl or showing no incoming links in the checked data. Confirm scope and implementation before calling it an orphan.
Crawl depth
The number of link steps along a measured route from a crawl start page. It is not the number of folders in the URL.
XML sitemap
A file supplying search engines with information about selected URLs and resources. Inclusion is not a guarantee of crawling or indexing.
Map the tasks behind the pages
Start with a small section and its reader tasks. A store might need a collection, product details, a fitting guide and care instructions. Write where each page belongs and where a reader would naturally need it. A folder name alone does not create that path: actual links connect the pages.
Use navigation to make the broad organization understandable and contextual links for a useful next step within an answer. Important routes should be easy to find, but there is no universal click count or link quota that proves a structure is good. Walk the real task rather than optimizing only a diagram.
Compare two different views of the site
Gather a published URL inventory independently of the crawl. This might come from the CMS, a sitemap and other appropriate records. Then run a link-following crawl from a stated start page and save the settings: allowed hosts, robots handling, rendering, exclusions and limits. An inventory says an address is known; a crawl says what that run reached.
Compare normalized addresses carefully, retaining the original URLs and any redirect observations. Inventory URLs missing from the crawl become candidates for investigation. A crawler starting from the homepage cannot discover every disconnected page solely by following the same connected links. Its output is not a complete inventory just because the run finished.
- Inventory: which URLs are known from independent records?
- Crawl: which pages did this configured run reach?
- Inlinks: which checked pages link to each candidate?
- Scope: which areas or behaviors did the run omit?
Five known pages. One route to investigate.
Inspect a candidate before choosing a fix
Open the candidate and check its purpose, current response and incoming-link evidence. A run may miss a page because of its limit, host boundary, blocked resource, rendering settings or an unvisited section. A page linked from a footer is not literally an orphan just because it lacks a body link. A chain of isolated pages can link among themselves while remaining unreachable from your starting section.
For a useful public page, choose an appropriate parent or related answer and a descriptive link that fits the reader task. For a retired campaign, duplicate, draft or confidential file, review its actual requirement separately. Do not automatically delete, redirect or noindex every missing URL. Those actions affect access and meaning, not merely a crawl label.
Verify the path and keep it maintained
After adding an authorized route, follow it as a reader and repeat a comparable crawl. Check the real link destination, page response and inlink record. A before-and-after map can confirm that the chosen route now exists. It cannot establish a guaranteed ranking, traffic or AI citation improvement.
Keep sitemap and page-link decisions coherent. Google says sitemaps can help discover URLs without guaranteeing that every listed item will be crawled or indexed. As pages are created or moved, record their intended place and useful routes. Recheck the affected section after navigation or template changes so the next release does not quietly remove the path again.
Known does not always mean reachable
Fictional inventory of five public pages and a crawl that reached four. The counts describe this exercise only; they are not a normal orphan-rate benchmark.
| Known page | Reached in this run? | Investigation |
|---|---|---|
| Store home | Yes | Crawl start page. |
| Desk collection | Yes | Linked from home. |
| Desk lamp product | Yes | Linked from collection. |
| Lamp care guide | Yes | Linked from product. |
| Lamp fitting guide | No | Check scope and incoming links; if useful and unlinked, add an appropriate product-page route. |
Put it into practice
Reconnect one useful answer
Use the fictional five-page lamp inventory. The fitting guide is public and accurate, but your run did not reach it. You have not yet inspected the crawler’s rendering settings or the product template.
- Save the inventory, crawl start page and relevant settings.
- List at least two reasons the run could miss the fitting guide.
- Inspect its current role and incoming links before labeling it an orphan.
- If it is useful and unlinked, propose one relevant source page and descriptive anchor.
- Write a reader check and a comparable recrawl check.
Keep your working notes in your own document. This page saves only your completion check, not your answers or customer data.
Check your understanding
Make the call.
Choose an answer for each question. Then compare the reasoning.
You have a useful next step.
- Organize around reader tasks and actual routes, not folder counts alone.
- Compare an independent inventory with a clearly scoped link crawl.
- Investigate candidates, choose a purposeful fix and verify the delivered path.
Completion is your own learning record. Quiz scores and practice checks are saved separately, on this browser.
Sources & context
The sources below explain the factual foundations and editorial methods used in this lesson. Worked examples, planning models and exercises are illustrative teaching material.
- Google: Sitemaps overview
Primary guidance on sitemaps, internal discoverability and the absence of crawling/indexing guarantees.
- Google: Link best practices
Primary guidance on crawlable links, descriptive anchors and linking to useful important pages. The inventory comparison is original teaching methodology.