Pottery teaching and writing leans on a small but precise vocabulary of vessel forms: tea bowl, bottle, jar, plate, vase, ewer. Each form has an origin, a typical technique (wheel-thrown, slab-built, coiled, pinched), a clay-body family that suits it, a function, and a small set of canonical examples. Visitors search for those forms by name and expect a dedicated page that answers the query.

SleekRank reads a form library from a Google Sheet or JSON file and renders one page per form at /pottery/forms/{slug}/ from a single base page. Tag mapping pushes the form name into the H1. Selector mapping fills the technique and clay-body badges. List mapping renders the typical-function list and the canonical-example list. The base template is a regular WordPress page, so the studio site keeps its existing typography and image treatment.

Updating a technique note after a new workshop is a single cell edit, not a post-by-post hunt. The XML sitemap covers every form URL automatically, the base template is excluded and noindexed, and pulling a form from the library returns a clean 404 instead of a stale page.

Pottery form vocabulary is precise and stable, which is exactly the kind of subject that rewards a per-term URL. A page about tea bowls, a page about bottles, a page about jars: each answers a specific search query better than any combined listing can. Studios and editorial sites that maintain a separate URL per form rank for form names directly, and they build internal link structure that search engines recognize as a coherent topic cluster.

Doing this with hand-written posts is a maintenance trap. A studio that adds a new clay-body family or revises a technique label has to find and edit every affected post, and the inevitable drift in terminology weakens the topical signal. With one source of truth feeding every URL, the form library itself is the editorial surface.

The instructor edits one row, every page that references that field updates after the next cache refresh. Cross-links between related forms become trivial because the source can carry a related-slugs array that list mapping renders consistently. The XML sitemap stays current automatically, the base template is excluded from indexing so it does not compete with the generated pages, and adding a new form to the library means appending a row, not creating, configuring, and proofreading another post in the WordPress editor.