JW DigitalJW Digital
CASE STUDY
B2B corporate site / Technical SEOTechnical SEO20-year-old domainIndex recovery301 redirects

874 pages back in Google's index — a 20-year-old domain rescued

A 20-year-old domain was completely unreachable, its sitemap had not been read in 7 years and robots.txt was missing. A 301 consolidation, console reconnection and item-by-item triage of 65 dead URLs brought 874 pages back into Google's index — with zero impact on business email.

← Back to case studies
0% → 100%
Primary domain availability
Previously timed out on every request
0 → 874
Pages discovered by Google
Sitemap readable again
1,946
Crawl requests the day after the fix
No records before deployment
0
Business email addresses affected
MX / SPF / DKIM untouched

Client: Client A (a B2B site with a 20-year-old domain — name and domain anonymised at the client's request)

01 — Client background

A 20-year-old corporate site, quietly losing its authority

Client A is a traditional B2B manufacturer whose site is built around a product catalogue, news and enquiry forms, with 874 URLs of legacy content. Long-standing customers type the primary domain directly, and organic search has always been the main acquisition channel — both routes were dead when we took over.

G

Client A — B2B website with a 20-year-old domain

20+ year-old domain · 874 URLs of content · DNS and hosting run by two separate third-party vendors

B2B corporate site20-year-old domainSaaS template hostingTechnical SEO
02 — Where it started

12 technical findings: far more than “the site is down”

The unreachable domain was only the part above the waterline. The full audit surfaced 12 issues across four layers: availability, index status, DNS assets and page structure.

✕ On handover
  • Primary domain:Completely unreachable, requests timed out
  • Sitemap:Failed to read, 0 pages discovered
  • 874 URLs:All dead while the domain was down
  • robots.txt:No such file on the site
  • Search consoles:No platform connected
  • 404 pages:65, untriaged, no direction
  • Duplicate pages:49 sets, no canonical tags
  • DNS records:14 legacy records left behind
✓ After treatment
  • Primary domain:Serving normally, 301 consolidates authority
  • Sitemap:Read successfully, 874 pages discovered
  • 874 URLs:All reachable, index entry points restored
  • robots.txt:Live, recognised by Google as fully valid
  • Search consoles:Google and Bing both connected
  • 404 pages:65 triaged, 22 mapped to redirects
  • Remediation plan:P1–P3 list handed to the build vendor
  • Business email:Zero impact, sending and receiving intact
03 — Domain recovery

From connection timeouts to one 301 that consolidates authority

The primary domain is the entry point for every historical backlink. Restoring reachability is only step one — the real work is redirecting the scattered authority to the canonical site in a single 301 hop, preserving full paths and query parameters so every legacy link lands somewhere useful.

ItemBeforeAfter
Primary domainCompletely unreachable, persistent timeoutsServing normally
HTTP accessConnection could not be establishedReturns a 301 permanent redirect
HTTPS accessConnection could not be establishedReturns a 301, certificate valid and auto-renewing
Redirect targetNo canonical destinationwww.(client-site).com
AuthoritySplit across two separate sitesConsolidated on the main site, legacy authority keeps flowing
Security warningBrowser flagged the site as unsafeValid certificate, warning gone

Source: post-deployment measurements (DNS records and HTTP response headers re-checked item by item)

04 — Indexing channel

A broken sitemap that sat unnoticed for years

The sitemap was first submitted in December 2011, and read records stop after July 2019 — meaning Google had no way to discover new content through this channel for years. Once resubmitted, the indexing pipeline came back online.

0
Pages discovered by Google (before)
Read failed, 1 error reported
874
Pages discovered by Google (after)
Sitemap processed successfully
7 yrs+
Gap in read history
2019.07 → 2026.10, no records
100%
Of 874 URLs reachable
Pages can be discovered and indexed
Bing in parallel: not submitted before → submitted and processing now. One indexing action, two search platforms, two independent traffic channels.

Source: Google Search Console › Sitemaps report · Bing Webmaster Tools

05 — Crawl protocol

robots.txt: from missing entirely to 1,946 crawl requests the next day

robots.txt is the first file a search engine reads before entering a site. No such file existed, so crawlers were working blind. Once deployed, Google recognised it as fully valid and crawling resumed.

✕ Before deployment
  • File status:No robots.txt present
  • Crawl requests:No records
  • File contents:None
✓ After deployment
  • File status:All files valid
  • Crawl requests the day after:1,946
  • File contents:Allow all crawling + sitemap declaration

Source: Google Search Console › robots.txt report

06 — 404 triage

65 404s, triaged into six categories — not simply deleted

The point of 404 handling is deciding what to save and what to let go. All 65 dead paths were traced individually, grouped into six categories, and given a graded action plan by impact.

CategoryCountShareAction
Legacy section and content paths (left over from a redesign)3858.5%High-value sections get redirects; the rest leave the sitemap
Long-tail content pages (bulk-generated, later retired)1624.6%Restore or retire after checking business value
Old static-site files46.2%Redirect where a matching new page exists, otherwise retire
Retired content-hub modules34.6%Restore the module or redirect to the new news listing
Platform-generated junk paths34.6%Block crawling and fix the source in the CMS
Trailing-slash URL variants11.5%Standardise URL rules site-wide
4
Priority fixes
Highest impact tier
18
Redirects to configure
Redirect map delivered
33
Awaiting business sign-off
Restore or retire
10
Safe to retire
No residual value

Source: full-site 404 crawl and triage sheet (all 65 covered)

07 — Domain assets and business safety

All 30 DNS records audited, zero impact on email

DNS is the invisible foundation of a site. Auditing all 30 records surfaced 14 legacy entries pointing at retired services — both an operational and a security risk. Every change deliberately avoided mail-related records, so the client's enquiry channel was never at risk.

30
DNS records audited
Each marked keep or clean up
14
Legacy records
Pointing at retired services
12–14
Active records
Serving normally
0
Business email addresses affected
MX / SPF / DKIM intact
08 — Execution path

What we did right

A repeatable playbook for legacy sites: diagnose first, restore the entry points, then triage item by item — with measurements at every step.

STEP 1

Full technical audit

12 issues across availability, index status, DNS assets and page structure

STEP 2

301 edge deployment for the primary domain

Server + valid certificate + permanent redirect, with DNS and response headers verified on the spot

STEP 3

robots.txt + sitemap resubmission

Google Search Console and Bing connected together; sitemap reads restored

STEP 4

404 triage and redirect map

65 dead URLs in six categories; 22 mapped with source, target, priority and owner

STEP 5

Acceptance testing and handover

10 acceptance checks archived; P1–P3 plan handed to the build vendor; 3 documents delivered

All figures come from official search-engine consoles and post-deployment measurements. Shared with client authorisation; verification channels available on request. Client details anonymised. JW Digital

Your site may be losing search authority in silence too

An unreachable domain, a dead sitemap, a missing robots.txt — none of these trigger an alert. They just shrink your index coverage and enquiries year after year. Our four-dimension audit works through technology, content, layout and on-page, and puts every issue on the table.

Book a site audit