A gardener catches a moth on the porch light and wants to know what it eats. A lepidopterist tracking range expansion wants to know where the species has been recorded. A naturalist photographing a giant silkmoth wants the wingspan and the caterpillar host. All three queries hit the same kind of page: one focused species page with the right fields filled in. Around 3,000 North American species cover most of the search demand.

SleekRank reads the species sheet as the schema. Columns for slug, common_name, scientific_name, family, wingspan_mm, host_plants, flight_months, range_states, and image_url feed the base page at /moth-id/{slug}/. List mappings render host plants and range as scannable lists. A meta mapping wires the OG image from the same row.

The cluster blocks at the bottom of every page work the same way. Family column groups Saturniidae with Saturniidae, host_plants column groups moths that share a host plant. Both are list mappings against the same sheet, returning six related species per page deterministically.

Moth identification is a niche but devoted audience. Lepidopterists and citizen scientists post records year-round, and the search queries follow the seasons. In spring people search for cecropia and luna moth caterpillars; in summer they search for sphinx moths nectaring at evening flowers; in autumn they search for the tussock moths defoliating their trees.

A site with a structured page per species, with flight phenology and host plants surfaced clearly, ranks for those seasonal long-tail queries because the page exactly matches the question. Building that corpus by hand is impossible at 3,000 species. Building it from a curated sheet is realistic, and the curation work concentrates on the data layer where it should: which species belong in the regional library, which host plants are confirmed, which photographs are licensed.

The other reason this corpus benefits from data-driven generation is the bidirectional linking between moths and host plants. A native plant site that lists its plants can list, on each plant page, the moths whose caterpillars eat it. The moth pages reciprocate.

Both lists flow from the same sheet with parallel arrays, and the link graph stays consistent because it is generated, not hand-maintained.