A redesign finishes, and a crawl report lists pages that have lost every incoming link. Some were published without a link from another page. Others disappeared from the menu when the company changed its offer. The addresses alone do not tell you which pages deserve attention.
A page on that list may still answer a search buyers make. Putting it in the sitemap would leave visitors without a link to follow through the site. Begin with the page's subject and search data, then decide where it belongs.
Orphan pages go unfound because Google follows links
A page can still exist at its address after the rest of the site stops pointing to it. Google and buyers lose a route to that page.
Google Search Central says it uses links to discover pages for crawling and to understand their relevance. It recommends linking to every page you care about from another page on the site. Pasting an address into the browser tests whether it opens; the review also needs to find the incoming link.
Consider the buyer reading a service page. They want more detail about a problem mentioned there. The site has a guide answering it, but the service page and family hub have no link to that guide. The buyer has reached a related subject without a route to the answer.
Read the surrounding pages as a group. Its hub introduces the subject and links to the related answers. A useful guide belongs with that family. The navigation and footer help visitors find the group and understand which subjects the company explains.
Choose the page's place in the site before adding its incoming link. The related family gives a reader a reason to continue to it. Whoever maintains that family also has a place to review the connection when the company changes its offer or rebuilds the navigation.
- Locate the missing route. Identify which live page should lead a buyer to the orphaned answer.
- Choose its page family. Place the answer beside related pages so visitors can continue reading about the same problem.
- Connect the useful page. Add the incoming link where it helps someone reach the next explanation.
A sitemap entry cannot stand in for a link
Adding an address to a sitemap leaves the missing route through the website unresolved. A buyer reading the site still needs a link to follow.
Google describes sitemaps as help for crawling larger or more complex sites. Its guidance also says it can usually discover most pages on a properly linked site. Review both: the addresses listed for search engines and the links available to someone reading a live page.
A sitemap also needs to point to the right place. We found a site with no pages in Google because its sitemap and canonical tags referred to an old domain. Canonical tags identify the preferred address for a page. In that case, both sets of references directed search engines away from the current site.
That finding matters when an orphan report follows a redesign. The visible menu may have changed while older domain references remain elsewhere. Adding more addresses to the same file would leave the underlying references unchecked. The person doing the repair needs to inspect the addresses already there against the current site.
Keep the sitemap repair and the internal-link repair explicit. Fixing an old-domain reference addresses where search engines are directed. Adding a link from a live hub addresses how a buyer reaches the page. Neither completed task proves that the other has happened.
Once the addresses agree with the current site, return to the orphan list. Each page being kept still needs a place in its family. The sitemap supports discovery; the links make that family usable to someone reading it.
Check an orphan page's searches before you delete it
Search impressions show which retired pages still appear for questions people ask. Read those questions before deciding that a page has outlived its purpose.
In Search Console's Performance report, read the page and query views together. The page view identifies the address shown in search. Its impressions record those appearances. The queries tell you what people searched for when the address was shown, giving the content review a question to examine.
Compare the query with the page it brought up. An older title may describe the company's former offer, while the query concerns work the company still does. Read the answer with that in mind. If it remains useful to current buyers, the missing menu link is a reason to restore its place.
A pivot can hide that connection. The company changes its menus to explain a new direction and retires a comparison post associated with the old one. Buyers can continue making the searches that led to the comparison. Removing it from navigation changes the site, but does not establish that the question disappeared.
Start with the answer already appearing for relevant searches. If it was retired, restore it; if parts are outdated, refresh them. Then link it from its family. A new article on the same search would leave that original answer disconnected, with its continuing impressions still unexplained in the orphan report.
The review therefore produces a decision beside each address. Keep and refresh the page when its searches and purpose still fit. Consider a redirect when both its search activity and its place in the offer are absent. The report supplies evidence for that decision; it does not make every orphan disposable.
Link each new page from its family hub
Publishing needs to include the links that connect the new page to the rest of its family. Otherwise, the next useful article can become the next orphan.
Put the link task beside the page task in the publishing assignment. The new page needs an incoming link from its family hub and a route back to it. The person keeping the site plan can choose those connections before publication, then inspect them when the page goes live.
Redesigns need another review because they change those routes. A menu rebuilt around a new offer can remove the only link to an older answer. The page may still matter, so someone needs to compare the remaining links with the pages the company intends to keep.
A one-time crawl audit can supply the list for a cleanup. Assign someone to review each orphan, decide which pages stay and add their links. Also decide who requests the next inspection after a redesign, because the delivered list describes the site at the time it was checked.
An internal-linking tool suggests connections between pages. Those suggestions give the person maintaining the site candidates to review. The publishing arrangement still needs to identify who chooses the receiving page, adds the link and checks what changed later.
People who maintain the site plan can carry those decisions through publication. They place the page in its family, add the links as it goes up and return to the link map after a change of offer. When assessing the work, follow those responsibilities from the suggested connection to the live page.
Redirect orphan pages that no buyer searches for
A page can leave the site when it has no search impressions and no role in the current offer. Its redirect should take visitors to the closest relevant live page.
Both parts of that decision matter. No impressions answers a question about the search data being reviewed. No place in the offer answers a question about what the business now sells. Reading them together helps distinguish a retired page from a useful answer that merely lost its links.
Read the old page's subject beside the possible destinations. Which current page comes closest to answering the same question? That is the redirect to consider. Choosing the homepage for every retired address would send different buyer questions to the same general introduction, even when a closer answer exists.
Our own site plan assigns each old lander a 301 redirect to its closest new page. We made that choice per address as part of replacing the older site structure. The destination follows the subject of the retired page, so the redirect decision is recorded alongside that page's replacement.
If the address continues appearing for relevant searches, read the old answer before redirecting it. It may need restoration, a content refresh and a link from its family. The comparison below was such a case: the page lost its place after a pivot while its search appearances continued.
The end of the review should leave each orphan with a purpose or a destination. Kept pages rejoin the site through links. Retired pages lead to the closest current answer. Use those decisions in the next publication or redesign to keep the page families connected.
Example: bringing back a page a pivot cut off
A compliance startup's retired comparison post kept appearing in search after the company changed direction.
Change the offer
The startup pivoted, and its old comparison post lost its place on the site.
Retire the post
The comparison address redirected to the homepage, where the original answer was no longer available.
Inspect the searches
Search data showed that the retired post still earned impressions.
Restore the answer
Bringing back the comparison became the first move because people still searched for what it covered.
The useful page was identified by its continuing search appearances. That gave the restoration a reason beyond clearing an audit report.
List your orphan pages, then check their searches
List the disconnected pages
Use the crawl report or site plan to identify addresses without an incoming link from another page on the site.
Inspect each page's impressions
Read the page and query views in Search Console to see which retired answers still appear for searches.
Restore the useful connections
Link pages that still answer relevant searches from their family hub, and add a link back to the hub.
Redirect the retired addresses
For pages with no impressions and no current purpose, choose the closest live page as the redirect destination.