The Pacific Yurts dealer network covers most of the country, but combined with regional builders the working list lands at roughly forty states. Maintaining forty hand-built WordPress pages, each with capacity notes, kit ranges, and contact details, is the kind of grind that quietly stalls a directory project for months.

SleekRank turns the same forty rows into forty indexed pages. You point it at src/pages/yurt-builders.json, set urlPattern to /yurt-builders/{slug}/, and the plugin generates pages like /yurt-builders/oregon/, /yurt-builders/colorado/, and /yurt-builders/new-mexico/ from a single base template.

When a builder discontinues a kit or you add a new dealer for Maine, you edit one JSON entry. The next rebuild reflows the affected state page, refreshes its meta, and leaves the other thirty-nine untouched. Sitemap, schema, and internal links update from the same data row. The dataset stays the source of truth, and rebuilds keep the directory aligned with each roster cycle without growing the editorial backlog over time.

Yurt searches are heavily regional. Buyers in Oregon and buyers in Vermont have very different climate needs, lead times, and dealer networks. A single national page cannot answer either query well, and it competes against itself when search engines try to pick a landing URL.

A page per state solves that problem on day one. The harder problem is the maintenance tail. Manually built pages drift.

A dealer closes, a new kit size launches, lead times stretch, and the WordPress page sits unchanged for months because nobody wants to edit forty pages by hand. The dataset gets stale, internal links rot, and the directory loses authority slowly. With a row-driven approach, the source of truth is the JSON.

Updating a dealer count or a lead time is a one-line change, and every page that reads that field refreshes on the next rebuild. The work shifts from page production to data curation, which is what the project should have been all along.