Rebuilding 91 Orphaned Pages: What It Cost Us

We inherited 91 pages with no internal links, no canonical tags, and traffic that had flatlined for over a year. Here is what the rebuild actually cost us in time, tooling, and decisions we got wrong the first time.

How Did 91 Pages Get Orphaned in the First Place?

Orphaned pages rarely happen in one go. They accumulate. A site migration drops a redirect. A CMS restructure moves content without updating the nav. A blog category gets renamed and old posts stop being linked from anywhere. Over enough months, you end up with a non-trivial slice of your index that Google can still crawl but has no reason to prioritise.

In our case, the 91 pages came from three sources:

• 34 were old service pages that survived two site rebuilds but were never wired into the new information architecture
• 29 were blog posts published before we had a proper tagging and internal-linking workflow
• 28 were landing pages built for specific campaigns that nobody decommissioned or merged after the campaigns ended

Screaming Frog 19.x identified them in about four minutes. The harder part was deciding what to do with each one.

What Does "Rebuilding" Actually Mean Here?

Not every orphaned page deserves to live. Before writing a single word, we ran each page through a four-column triage:

Page	Avg. monthly impressions (GSC)	Existing backlinks (Ahrefs)	Decision
Service page (old)	< 10	0	Redirect or delete
Blog post	40–300	1–3	Rebuild and link
Campaign landing page	< 5	0	301 to nearest canonical
Blog post	> 300	5+	Rebuild, expand, republish

Pages with zero backlinks and under 10 monthly impressions are not worth rebuilding. You are just adding maintenance overhead. We deleted or redirected 41 of the 91 outright.

That left 50 pages that had either search demand or backlink equity worth preserving.

The Rebuild Scope for the Remaining 50

Each page needed at minimum:

• A canonical tag pointing to itself (previously missing entirely)
• Two to four contextual internal links from high-authority pages on the same domain
• A revised title tag and meta description aligned to the primary query the page was already partially ranking for
• Content updated to reflect what the page actually covered in 2024, not 2021

Some pages needed full rewrites. Twelve of the blog posts were thin, under 600 words, covering topics where a competitor had a 2,000-word piece ranking in position two. We expanded those to between 1,400 and 1,800 words, keeping the original URL.

What Did It Actually Cost?

Time is the honest metric. Here is where the hours went across the full project.

Audit and Triage

Screaming Frog crawl plus GSC and Ahrefs export: 3 hours. Building the triage spreadsheet and making the delete-or-rebuild call on each page: 11 hours. A lot of that time was argument, specifically, debating whether a page with 200 impressions but zero clicks deserved a rebuild. The answer is almost always no unless the query it is showing for is commercially relevant.

Content Work

The 12 full rewrites averaged 6 hours each: research, writing, internal-link planning, and one round of edits. That is 72 hours of senior writing time, not junior content.

The 38 pages that needed updates rather than rewrites averaged 2.5 hours each. Most of that was updating statistics, replacing dead outbound links, and writing two or three new paragraphs to address angle gaps. Total: 95 hours.

Technical Implementation

Adding canonical tags and updating internal links across 50 pages took one engineer about 18 hours, mostly because our CMS at the time made bulk edits painful. If you are on a headless setup with a proper content API, this is closer to 4 hours of scripted work.

Redirecting the 41 deleted pages: 2 hours including testing.

The Running Total

Task	Hours
Audit and triage	14
Full rewrites (12 pages)	72
Partial updates (38 pages)	95
Technical implementation	18
Redirects and QA	4
Total	203

At a blended rate of £85/hour, that is roughly £17,255 of internal cost. You could compress this significantly with an external content team, but you would trade speed for quality control on the technical accuracy of the content.

What Did We Get Wrong?

Two things, both instructive.

First, we underestimated the time needed to find good internal-link anchor opportunities. You cannot just link from any page; the page you are linking from needs to be topically related and have some page authority of its own. For several rebuilt pages, we had to create new hub content first before the internal link had any value. We did not budget for that.

Second, we republished 12 pages without changing the original publication date. Google saw those as updated posts, not new ones, which was correct. But on three of them, the original date was 2019, and the content now referenced 2024 data. That date mismatch eroded trust signals. We should have updated the publication date to reflect the substantial revision, which is standard practice for posts where more than 30 to 40 per cent of the content has changed.

Did It Work?

Over 90 days post-launch, the 50 rebuilt pages collectively moved from an average position of 41.2 to 28.7 in Google Search Console. Organic clicks to those pages increased by 214 per cent compared to the same 90-day window the previous year.

Three pages crossed into position-one results for their primary query. None of those were the ones we expected.

The 41 deleted or redirected pages showed no measurable negative impact on overall domain traffic. One page had a backlink from a DA 60 domain; we made sure that 301 went to a semantically close live page rather than the homepage.

Conclusion

If you have an orphaned-page problem, start with the audit before you start writing. The triage decision, specifically what to delete versus what to rebuild, is where most of the value is. Getting that wrong means spending 200 hours on pages that deserved a 301.

Run Screaming Frog, pull your GSC impressions, cross-reference with Ahrefs for backlink equity, and build your triage table before you touch a single word of content. The rebuild work is straightforward once you know what you are actually rebuilding and why.

---

FAQ

What is an orphaned page in SEO? An orphaned page is any page on your site that has no internal links pointing to it from other pages on the same domain. Search engines can still find it via sitemap or external backlinks, but without internal links it receives no PageRank from your own site and is rarely prioritised in crawl budgets.

Should you always rebuild orphaned pages rather than delete them? No. Pages with under 10 monthly impressions and zero backlinks are candidates for deletion or redirection. Rebuilding costs real time and budget. The threshold worth crossing is roughly 50 or more monthly impressions, or any page with backlinks from domains with a DR above 30.

How long does fixing orphaned pages take? For a site with around 50 pages worth rebuilding, expect 150 to 220 hours of combined writing and technical work, depending on content depth and CMS flexibility. Auditing and triage add another 12 to 15 hours upfront. Timelines compress if you have a headless CMS with a content API.

Will deleting orphaned pages hurt your domain authority? Not meaningfully, provided you 301 redirect any page that has external backlinks to a semantically related live URL. Deleting pages with no backlinks and no traffic has close to zero impact on overall domain metrics.

How do you find orphaned pages quickly? Screaming Frog running a full crawl with "crawl all subdomains" enabled will flag any URL in your sitemap or on your server that has no inbound internal links. Cross-reference the output with Google Search Console's Performance report to separate pages worth saving from pages worth removing.

Have a project in mind? Contact Sodio Technologies to discuss your requirements and explore the right technology solution for your business.