Urban legends share a tight metadata shape even when the stories themselves vary wildly. Each entry carries an origin region, a first recorded date or era, a set of recurring themes, a list of known variants, and a veracity status (debunked, partially true, unverified). Snopes-style sites already work this way internally; the public pages just present the fields in a consistent layout.

SleekRank reads a legend sheet and renders one URL per row at /urban-legends/{slug}/ using a base WordPress page as the template. Tag mapping handles the title, selector mappings drop in origin and first-recorded date, list mappings render themes and variants, and the body sits in a content block. A status column gates which legends appear in 'debunked' versus 'unverified' indexes.

Updating a verification status when new evidence emerges is one cell edit in the sheet. Adding a fresh legend that is currently spreading on social media is one row, not a new WordPress post.

Verification archives reward freshness. A reader checking whether the vanishing hitchhiker has any documented basis wants the current status, not an opinion from 2014. Search engines reward freshness too, because pages that update their veracity field when new evidence appears tend to outrank ones that froze in time.

The bottleneck on hand-built urban-legend libraries is never the first writeup, it is keeping veracity and references current across the set when each entry lives in its own WordPress post. Programmatic generation removes that drift by design, since the data side carries veracity, last reviewed date, and references, while the template lives in one place. Researchers focus on substance (well-sourced verdict, careful citation) and the platform handles structure.

The archive stays current as long as the sheet stays current.