Ghost stories carry the same metadata shape whether they come from a Victorian penny dreadful, a regional folklore collection, or a contemporary haunting report. Each entry has a location (often a named building), a time period, a type of haunting (residual, intelligent, poltergeist, crisis apparition), a list of reported witnesses, a set of recurring phenomena, and a source attribution. The values change per story, the fields stay constant.

SleekRank reads a ghost-story sheet and renders one URL per row at /ghost-stories/{slug}/ using a base WordPress page as the template. Tag mapping handles the title, selector mappings drop in location and period, list mappings render phenomena and witnesses, and the body sits in a content block. A second page group can render location-index pages (every haunting at a single building or city).

Adding a freshly documented haunting from a regional newspaper is one row in the sheet. The story renders inside the existing template, joins the location and period indexes automatically, and inherits the schema markup and Open Graph card.

Haunting archives reward structure. A reader arriving at any ghost-story page expects the same shape every time: where, when, what kind of haunting, who reported it, what they reported. Search engines reward that structure too because well-organized pages surface for '{building} haunting' and '{city} ghost stories' queries.

The bottleneck on hand-built archives is never the writing of one report, it is the formatting drift across hundreds of stories when each lives in its own WordPress post. Programmatic generation removes that drift by design, so the template lives in one place and every entry inherits it. Investigators and historians focus on substance (accurate location, careful sourcing, clear period framing) and the platform handles structure.

The archive compounds in authority as new locations and reports get added to the source.