Every poem has the same fields: an author, a date or period, a poetic form, a set of themes, the full text, often a line-by-line analysis, and a place in a body of work. The substance varies wildly per poem; the shape does not. That makes a poetry library a clean fit for per-entry pages, especially for public-domain corpora that already span thousands of works.

SleekRank reads poem data from a sheet, CSV, or JSON and produces one page per poem at /poems/{slug}/. Tag mapping fills the title, selector mapping handles author and form, list mappings render the stanzas and analysis notes. Editors maintain the catalog in the source; the template lives in WordPress.

When an analysis gets revised or a new poem enters the public domain, that change ships to the live site on the next cache cycle. The library grows by adding rows.

Poetry sites win on coverage and faithful presentation of the text. A reader looking up a specific poem wants the full text, clean line breaks, correct stanza spacing, and basic context: who wrote it, when, what form, what themes. The risk on hand-built poetry sites is uneven line-break handling and inconsistent metadata across the corpus, both of which damage credibility for serious readers.

Programmatic generation fixes that because every poem inherits the same template and every line break comes from data rather than from editor formatting. Public-domain poetry alone provides thousands of works ready to publish; modern licensed poetry adds to that catalog with explicit rights. The site captures search for title queries, first-line queries, and theme queries because every page meets the same structural bar, and authority compounds as the catalog grows.