Skip to content
Get Ranked On TopIllustrative case studySignal plan

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

THORNRAIL TRANSLOAD · Rail-to-truck transload, 26 terminals · Kansas City

How a Kansas City transload operator got all 26 of its terminals found by Google

26/26

terminal pages indexed, up from 5

Kansas City, United States · 10 months · Industry, energy & mobility

MOIANEKSOKTXHUMP060404050403

How to read the yard: cars leave the home page over the hump and switch onto a track for each state. A green signal means a crawler can reach that track by following links. Modelled data.

Yard boardMonth 0 → Month 10

Indexed
5/2626/26
Orphaned
210
Sitemap
214 days oldnightly

01THE CHALLENGE

26 terminals on the ground. Five on the map Google could read.

Terminal pages hid behind a JavaScript map with no real links, and the sitemap was months out of date: only 5 of 26 terminals were indexed.

A shipper who needs a transload in Wichita or Tulsa searches for exactly that, and Thornrail had a terminal in both. But the Locations page was a JavaScript map: lovely for a visitor with a mouse, a blank wall for a crawler. A page existed for every terminal, and almost nothing linked to them.

The fix was not more content. It was track: real links, a hierarchy a crawler can walk, and a sitemap that tells the truth.

YARD INSPECTION · MONTH 0

  1. BAD ORDER · 01

    5/26

    Five of 26 terminals indexed

    The five in the index were exactly the five the old Services page linked to. The other 21 were unknown to Google or stuck as “discovered, not indexed”.

  2. BAD ORDER · 02

    21

    Orphaned terminal pages

    A crawl from the home page reached five terminals. The other 21 lived on the server, but no page pointed to them with a real <a href>.

  3. BAD ORDER · 03

    214 days

    A stale, hand-made sitemap

    Written by hand when the site launched with eight terminals. Three of those have since closed, and the 21 opened later were never added.

  4. BAD ORDER · 04

    0

    Crawlable links on Locations

    The map drew its pins in JavaScript and opened terminals with click handlers. Googlebot’s rendered HTML held a map container and not one link to a terminal.

  5. BAD ORDER · 05

    3

    Dead URLs in the sitemap

    The closed terminals were still listed and answered 404, so every crawl spent requests on pages that no longer existed.

  6. BAD ORDER · 06

    1.8 MB

    Of map script first

    Terminal names appeared only after the map bundle loaded. Even rendered, the page offered the crawler pins, not paths.

02THE SWITCHYARD

Throw the switches. Watch the crawler find its way.

Each car is a terminal page and the number on it is its click depth from the home page. Throw the four levers we pulled, in any order, then pick a terminal to trace its route.

Presets
HOMEServices pageLocations listState hubsMOIANEKSOKTXMO-012MO-022MO-03—MO-04—MO-05—MO-06—IA-01—IA-02—IA-03—IA-04—NE-01—NE-02—NE-03—NE-04—KS-012KS-02—KS-03—KS-04—KS-05—OK-012OK-02—OK-03—OK-04—TX-012TX-02—TX-03—
  • Up to 3 clicks
  • 4 clicks or more
  • Sitemap only
  • Orphaned
Reached by links
5 of 26
Orphaned
21
Deepest route
2 clicks
In the sitemap
5 of 26
Terminals by click depth

Terminal board · pick one to trace the crawler’s route

  • MO
  • IA
  • NE
  • KS
  • OK
  • TX

Route to NE-02

Click depth: no route

No page links here and the sitemap does not list it: to the crawler, this terminal does not exist.

5 of 26 terminals reached by links. Deepest route: 2 clicks.

03THE FOUR LEVERS

Four switches, thrown in order.

Built on our Signal plan: technical SEO for sites where crawling and architecture decide what gets found.

  1. 01LEVER 1 · INTERNAL LINKING

    Real links under the map

    The Locations page now server-renders an A–Z list of all 26 terminals as plain <a href> links beneath the map. Visitors keep the map; the crawler gets paths.

    21 orphans → 0

  2. 02LEVER 2 · HUB PAGES & BREADCRUMBS

    Six state hubs

    A hub page for each state in the main menu, listing its terminals with the rail lines, commodities and truck access they serve. Breadcrumbs on every terminal link back to the hub and to Locations.

    every terminal ≤ 2 clicks

  3. 03LEVER 3 · XML SITEMAP

    A sitemap that builds itself

    Generated nightly from the terminal database with an honest lastmod. Closed terminals drop out and 301 to the nearest open one; the file is submitted in Search Console.

    26 URLs · 0 dead

  4. 04LEVER 4 · LOG-FILE ANALYSIS

    Proof in the logs

    Server logs checked every week to confirm Googlebot really requested each terminal, and how often. A terminal not crawled for 14 days got a link from a busier page.

    26 of 26 crawled

04RUNNING LOG

Ten months, milepost by milepost.

  1. MONTH 1JAN

    Yard inspection

    A full crawl from the home page, the Search Console page report and twelve weeks of server logs. 21 orphans found, 3 dead sitemap URLs.

    Indexed
    5/26
    Orphans
    21
  2. MONTH 2FEB

    Pilot list: Missouri & Kansas

    The HTML list under the map shipped for two states first, so the effect could be measured. Eight orphans gained a link.

    Indexed
    5/26
    Orphans
    13
  3. MONTH 3MAR

    Every state listed, sitemap rebuilt

    All 26 terminals linked from Locations. The sitemap now builds nightly from the terminal database and was resubmitted.

    Indexed
    9/26
    Orphans
    0
  4. MONTH 4APR

    State hubs

    Six hub pages in the main menu and breadcrumbs on every terminal page. No terminal is more than two clicks from home.

    Indexed
    16/26
    Orphans
    0
  5. MONTH 5MAY

    Nearby-terminal links

    Each terminal links to its neighbours on the line, so link signals flow sideways between them, not only down from the hubs.

    Indexed
    21/26
    Orphans
    0
  6. MONTH 6JUN

    The logs confirm

    Googlebot requested 24 of 26 terminal pages this month. The two it skipped got a link from the busiest hub.

    Indexed
    23/26
    Orphans
    0
  7. MONTH 7JUL

    Pages worth indexing

    Every terminal template gained the rail lines served, track capacity, commodities and truck gate hours: reachable and worth reading.

    Indexed
    25/26
    Orphans
    0
  8. MONTH 8AUG

    26 of 26 indexed

    Every terminal page in Google’s index. Quote forms on terminal pages tagged so organic requests can be counted.

    Indexed
    26/26
    Orphans
    0
  9. MONTH 9SEPT

    Dead URLs closed

    The three closed terminals now 301 to the nearest open one, so old inbound links keep their value.

    Indexed
    26/26
    Orphans
    0
  10. MONTH 10OCT

    Yard report

    No orphans, 4,900 organic sessions a month on terminal pages and 39 organic quote requests a month, against 14 before.

    Indexed
    26/26
    Orphans
    0

05YARD REPORT · MONTH 10

Every track lit.

5 → 26

Terminal pages indexed
26 terminals5JanAprJulOct

21 → 0

Orphaned terminal pages
212113JanAprJulOct

+179%

Organic quote requests / month
14 · month 039JanAprJulOct

420 → 4,900

Organic sessions to terminal pages / month
4204,900JanAprJulOct

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

TRACK BY TRACK · TERMINALS PER STATE

Terminal pages per state: indexed, orphaned and click depth before and after the engagement
StateTerminalsIndexed, month 0Indexed, month 10Orphaned, month 0Deepest, month 10
MO62642 clicks
IA40442 clicks
NE40442 clicks
KS51542 clicks
OK41432 clicks
TX31322 clicks

CLEAR SIGNAL

Get every page onto the map

If your locations, products or listings live behind a widget, we will lay the track so search engines can reach every one of them.

← Back to all case studies