A butterfly species page is family, binomial, range, host plants, nectar sources, wingspan, flight season, and identifying features. Hand-built butterfly directories drift on host-plant formatting, flight-season notation (Jun-Aug vs summer vs June 1 to August 15), wingspan units, and family classification after the recent reshuffles in Nymphalidae and Lycaenidae.

SleekRank reads a butterfly sheet and renders one page per row at /butterflies/{slug}/ using a base WordPress page. Family and binomial slot into tag mappings, host plants and nectar sources into list mappings, range and flight season into selector mappings. The base page is the template; the sheet owns the per-species values.

The sample table shows the pattern: monarch (Nymphalidae, milkweed host, 8.9-10.2 cm, Jul-Sep migration), swallowtail (Papilionidae, various carrot-family hosts, 6.5-9 cm, May-Sep), red-admiral (Nymphalidae, nettle host, 4.5-6.5 cm, Apr-Oct), painted-lady (Nymphalidae, thistle host, 5-7 cm, Apr-Oct), karner-blue (Lycaenidae, wild lupine host, 2.5-3 cm, May-Jun and Jul-Aug).

Butterfly directories live or die on field-data consistency. A reader looking up the monarch wants to find the host plant (milkweed) in the same place on every page across the site, and a gardener planning a pollinator bed wants nectar sources rendered the same way for every species. Hand-built directories drift, especially across regional clubs where different editors prefer different conventions.

SleekRank pins butterfly content to a single source where host plants, nectar sources, flight seasons, and ranges live as structured fields. Bulk updates after a Nymphalidae or Lycaenidae taxonomic revision become a sheet edit instead of a multi-page audit. Pollinator-garden guides, lepidoptera societies, and field-guide companions all benefit from this discipline; readers find the host plant they need, editors keep field formatting consistent, and the catalog grows steadily as new species or new host-plant associations get documented.