Skip to content
Get Ranked On TopIllustrative case studySignal plan

A fictional business. The figures are a modelled scenario, not a client result.

Glacierline Cold Freight · Chicago

How a Chicago cold-freight carrier got its lane pages back after a botched CMS merge

Soft 404s cleared, then +69% quote requests from search

180-truck reefer fleet & cold storage · Chicago · 10 months · North America · Signal plan

Status-code audit · Redirect hygiene · Server-side rendering · Crawl monitoring

Pallet manifestLoad no.GCF-0412-1240
Ship fromChicago
ConsigneeSearch engines
Contents1,240 lane & service URLs
Keep at-18 °C
Condition on arrival620 damaged in transit
4012 1240 69
Quote requests from search · month 10+69%

[01]The challenge

Two websites merged. Half the freight fell off the truck.

After a CMS merge, half of Glacierline's 1,240 lane and service pages returned soft 404s or long redirect chains, and quote requests from search fell by a third.

Glacierline ran two sites: one for the reefer fleet, one for its cold-storage warehouses. Merging them into a single CMS was meant to give shippers one place to book a lane. Instead the new templates loaded rates in the browser, old URLs bounced through layers of redirects, and retired lanes kept answering “OK”. Rankings for lane searches like Chicago to Atlanta vanished within weeks, and the quote form went quiet.

Lane & service URLs after the merge · one square = 10 URLs

  • Working (200) 620
  • Soft 404 380
  • Redirect chain 240

Quote requests from search, per month

[02]Diagnosis

What the scanner found on the dock.

Soft 404s

380

Lane pages answered 200 OK with an empty rate table: the new CMS fetched lane data in the browser and the call often timed out. Google saw “No rates found” and filed the pages as missing. Retired lanes and blanket redirects to the homepage added to the pile.

Finding 1 of 4

Redirect chains

240

Old trucking URLs went http → https → new domain → temporary 302 → trailing slash before reaching a page. Fourteen chains looped back on themselves; the longest ran seven hops.

Finding 2 of 4

Average hops

3.4

Every legacy link, bookmark and partner listing paid that toll. The temporary 302s left from launch week told Google to keep the old URLs, so ranking signals were split instead of passed on.

Finding 3 of 4

Internal links

9,800

Navigation, lane tables and blog posts still pointed at old addresses: 9,800 internal links landed on a redirect, which kept crawlers busy on detours instead of live pages.

Finding 4 of 4

Where Googlebot spent its visits

Merge month · server-log sample
Month 10 · server-log sample
  • Redirects & loops
  • Soft 404s
  • Rate-calculator parameters
  • Live lane & service pages

[03]The strategy

Four checks before anything leaves the dock.

Built on our Signal plan: the technical engagement for sites where status codes, rendering and crawl decide what search engines can see.

Pick list4 / 4

  1. GCF-01

    Status-code audit

    Every URL from both legacy sites, the new CMS, the sitemaps and five years of backlinks was requested and classified by what it really returned: real 200, soft 404, redirect, chain or loop. Each one was matched to the quote requests it used to bring in.

  2. GCF-02

    Redirect hygiene

    One redirect map replaced three layers of rules: 3,700 legacy URLs sent with a single permanent 301 to their closest equivalent, the leftover 302s converted, loops broken and retired lanes given an honest 410.

  3. GCF-03

    Server-side rendering

    Lane pages now ship their transit times, temperature ranges and equipment in the HTML. The rate table loads on the server, so crawlers and shippers see the same page, even when the rates API is slow.

  4. GCF-04

    Crawl monitoring

    A status-code crawl runs every week and before every release, and server logs raise an alert when a new chain or soft 404 appears. The XML sitemaps list only canonical URLs that answer 200.

[04]Scan the dock

Eight pallets, eight URLs. Scan one and hear what it answers.

Each pallet is one kind of page from the merged site. The scanner reads its HTTP response the way Googlebot does: the status code, every hop on the way and where it finally lands. Switch to month 10 to scan the same pallets after the fix.

Tab to a pallet and press Enter to scan it. With the beeper on, each beep is one response.

Manifest · Merge day0 of 8 pallets scanned

Ready to scan

Pick a pallet on the dock or press “Scan next pallet”.

  • 200 OK×1
  • Soft 404×3
  • Redirect chain×3
  • Redirect loop×1

Status codes, as the scanner reads them

200OK
The page exists and here it is. Only correct when the HTML has real content in it.
301Moved permanently
The page has a new address for good, and links and rankings follow it. Best as one hop, straight to the final URL.
302Found (temporary)
A short detour. Search engines keep the old URL, so a 302 left behind after a migration holds signals back.
404 / 410Not found / Gone
Honest answers for pages that no longer exist. 410 says the page was removed on purpose, and crawlers let it go sooner.
Soft 404OK, but empty
The server says 200, but the page is empty, an error message or a redirect to the homepage. Google files it as missing anyway.

[05]Month by month

10 months, bay by bay.

Broken lane & service URLs left, by month
  • Soft 404s
  • Redirect chains
  1. Month 1

    Triage

    Crawl of the merged site and both legacy domains, 90 days of server logs, the Search Console soft 404 list and quote-form leads matched to the pages they came from.

  2. Month 2

    Soft 404s

    Lane template rendered on the server, honest 410s for 46 retired lanes, and homepage redirects replaced with like-for-like 301s.

  3. Months 3–4

    Redirect hygiene

    One redirect map for 3,700 legacy URLs, 302s made permanent, 14 loops broken and 9,800 internal links rewritten to final URLs.

  4. Months 5–6

    Clean signals

    XML sitemaps cut to canonical 200s, rate-calculator parameters kept out of the crawl, canonical tags fixed on duplicate service-page variants.

  5. Months 7–10

    Watch & build

    A weekly status-code crawl wired into releases, log alerts for new chains, and 24 new lane pages for routes added this year.

[06]Results

Every pallet scans clean, and the quote form is busy again.

Quote requests from search (vs merge month)

+69%

208 → 351 a month · 312 before the merge

Soft 404s

380 → 0

Soft 404s left on lane & service pages, by month

Average redirect hops

3.4 → 1

Every legacy URL now reaches its page in one hop

Lane & service pages indexed

598 → 1,196

598 → 1,196 of 1,240 pages in the index

Modelled scenario for a fictional business — not a client result. Rankings and traffic are never guaranteed; see our Terms.

Quote requests from search, per monthQuote requests
200250300350Before the merge: 312M1M2M3M4M5M6M7M8M9M10351208
Broken URLs, per month
0300600M1M2M3M4M5M6M7M8M9M10
  • Soft 404s
  • Redirect chains

Lane searches: lost at the merge, then back

QueryBefore the mergeMerge monthMonth 10
reefer trucking chicago to atlanta#5not in the top 50#3
frozen ltl midwest#7#24#4
cold storage bolingbrook il#2#2#1
refrigerated freight chicago to dallas#6not in the top 50#4
pharma cold chain logistics chicago#9#31#5
temperature controlled trucking chicago#8#19#6

Positions modelled from a Chicago location, tracked weekly. Lane & service pages in the index: 598 → 1,196.

Get a plan like this

Merging sites, replatforming or tidying years of redirects? Start with the Signal plan, or tell us what you are moving.

← All case studies