Cooking school search splits by cuisine and class type first. "Sushi classes Los Angeles" and "bread-baking school Brooklyn" are different queries with different shortlists, even when one school covers both. A directory that ranks needs a page per cuisine in every city, with the right schools, class prices, and current schedules.

SleekRank reads a Google Sheet with one row per school and renders each through a WordPress base page. A cuisine column drives /cooking-schools/{cuisine}/{city}/ and a slug column drives /cooking-schools/{slug}/ profile pages. Both page groups share the same sheet, so adding a Korean barbecue class is a column value, not a template fork.

Class price, instructor credentials, class duration, and next-available-date map to tag and selector mappings on the base page. When schools update their fall or spring schedules, you sync the column from a CSV (or a connected Notion database), clear the SleekRank cache, and every page rebuilds with the new schedule without touching individual posts.

Cooking school searches behave more like leisure-class queries than like vocational queries because students filter by cuisine first and by city second. The cuisine is the head term: French, Italian, Japanese, sushi, baking, plant-based, Indian, Korean. Each cuisine has its own typical class length, its own equipment requirements, and its own student profile.

A sushi class needs grade-A fish and a long demonstration on rice technique. A bread-baking class needs a full oven block and a multi-hour proofing schedule. Mixing them on one page hurts both queries because students who want one will not enroll in the other.

Class schedules also move on their own cadence as schools open new sessions for each season, and a directory that surfaces last spring's schedule in October is worse than not surfacing one at all because would-be students assume the school is dormant. Programmatic generation makes the maintenance loop manageable. One row per school, one cell per schedule, one cache flush per season.

The directory stays current with each school, the page-per-cuisine structure matches how Google interprets the queries, and editorial work shifts to the things that need judgment, like instructor profiles and class write-ups. SleekRank does not validate schools, but it removes the structural reason cooking-school directory data goes stale.