The Ellis Island and Castle Garden archives cover roughly 50,000 voyages that landed in US ports between 1820 and 1957. Researchers usually arrive from a surname search and want context: which ship, which line, which port of origin, what the manifest image actually shows. That context lives only on the aggregator, and only behind a search step that costs another click and another page load.

SleekRank turns the manifest index into one WordPress page per voyage. Each page carries ship name, line, arrival date, port of departure, port of arrival, passenger count, manifest microfilm reel, and a Trip schema block, all driven by tag and selector mappings on a shared base. The URL pattern is /manifests/{slug}/, and new voyages appear after the next cache refresh.

Genealogy aggregators won this category because they own the index, not because their per-voyage pages are good. SleekRank flips that by making the per-voyage page the entry point, not the search box. Researchers land directly on the manifest they want, the society keeps the traffic, and the data file remains the canonical source.

Immigration research is one of the densest long-tail traffic categories on the open web. Researchers search by surname, by town of origin, by ship, by year, by port pair, and most queries are highly specific. The aggregators that currently own the category do so because they hold the index, not because their per-voyage pages match the depth of the query.

Local genealogical chapters and heritage projects produced the transcriptions that fill those indexes, yet none of the organic value flows back to them. SleekRank closes that gap by turning the same CSV into a per-voyage landing page corpus on the heritage organization's own domain. Each voyage becomes its own URL that ranks for ship name, line, year, and port pair searches.

Internal links across voyages strengthen the chapter's authority. Trip and Event schema make every page eligible for entity panels and enhanced results. Volunteers continue contributing through the manifest spreadsheet, while the public archive refreshes through cache cycles.

The aggregator model wins on breadth; the per-voyage page wins on depth, citation, and the long tail of surname queries that finally land somewhere the heritage organization owns.