The NARA service record archive covers roughly 10,000 distinct military units across US history, from Continental Army regiments through modern brigade combat teams. Researchers usually arrive from a regiment and date pairing and need to know what campaigns the unit fought, who the commanding officer was, where the muster rolls live, and which microfilm reel covers the period. That context belongs on a unit landing page, not in a search results row.

SleekRank reads the unit index file and emits one WordPress page per unit. Each page carries branch, state of origin, mustered-in date, mustered-out date, principal campaigns, commanding officers, microfilm reel range, and a MilitaryUnit schema block, all driven by tag and selector mappings on a shared base. The URL pattern is /units/{slug}/, and new transcriptions appear after the next cache refresh.

Most heritage research traffic for these units bypasses the organisations that did the transcription work, which is the operational problem this category solves. SleekRank moves the index onto the society's own domain so the same CSV that fed the aggregator now also feeds an indexable corpus the society fully owns.

Military genealogy is one of the deepest long-tail traffic categories in family research. Searches combine regiment number, state of origin, battle name, and war year in specific permutations that aggregators handle through paywalls and search forms. The heritage organisations that produced the underlying transcriptions rarely see organic traffic from work they largely paid for, because the public-facing surface lives on a third party.

SleekRank flips that arrangement by turning the same CSV into a per-unit landing page corpus on the heritage group's own domain. Each unit becomes its own URL that ranks for regiment, war, and state-of-origin searches. Internal links across units, battles, and rosters form a cross-linked structure that strengthens the organisation's authority.

MilitaryUnit and Event schema make every unit eligible for entity panels and enhanced results. The corpus stays current with NARA and Fold3 through cache cycles, and volunteers continue contributing through the unit spreadsheet they already maintain. Aggregators win on breadth; the per-unit page wins on depth, citation precision, and on the long tail of regiment-and-battle queries that finally land where the heritage work was actually done.