The Strawbale Association registry plus regional networks cover about thirty US states with active straw bale builders. That number is too small for a giant database and too large for a hand-maintained list. The interesting work is keeping climate notes, finish styles, and registered project counts accurate as the niche grows.

SleekRank treats each state as a row in src/pages/strawbale-builders.json. Fields like builderCount, finishStyle, and completedProjects populate a template that renders at /strawbale-builders/{slug}/. New states are appended as rows, not as full WordPress pages.

When a builder publishes a new project in Vermont, you bump the project count on that row and trigger a rebuild. The Vermont page reflows in seconds, its sitemap entry refreshes, and the other twenty-nine state pages stay served from cache. Updates feel like editing a spreadsheet, not maintaining a CMS. The dataset stays the source of truth, and rebuilds keep the directory aligned with each roster cycle without growing the editorial backlog over time.

Straw bale construction is a small but loyal niche. The people searching for it know what they want, and they expect deep, climate-specific information rather than generic intros. A page per state is the right unit of content for that audience.

A hand-built version of the directory dies a slow death. Project counts go stale, builders drop off the registry, and the WordPress pages keep claiming the same numbers from two years ago. Visitors notice, and so do search engines.

The credibility cost of stale data in a small niche is much higher than in a broad industry. SleekRank makes the dataset the unit of work. You maintain rows, not pages.

A registry update becomes a JSON diff, a rebuild, and a refreshed sitemap. The directory keeps pace with the niche instead of falling behind it. That is the difference between a directory worth bookmarking and one that quietly slides off the search results page over a year or two.