Dance school search splits by style and age group first. "Ballet classes for 5 year olds Brooklyn" and "adult contemporary dance Brooklyn" are different queries with different shortlists, even when one studio offers both. A directory that ranks needs a page per style and age band in every metro, with the right studios, class prices, and current schedules.

SleekRank reads a Google Sheet with one row per dance studio and renders each through a WordPress base page. A style column drives /dance-studios/{style}/{city}/ and an age_group column drives /dance-studios/{style}/{age_group}/{city}/ pages. All page groups share the same sheet, so adding a teen jazz track is a column value, not a template fork.

Class price, instructor credentials, age band, and next-term-start map to tag and selector mappings on the base page. When studios update their fall or summer schedules, you sync the column from a CSV (or a connected Notion database studios maintain themselves), clear the SleekRank cache, and every page rebuilds with the new schedule without touching individual posts.

Dance school searches behave more like youth-activity queries than like fitness queries because parents filter by age first, by style second, and by location third. The age band is often the head term for kids classes: pre-school dance, ages 5 to 7, ages 8 to 12, teen, adult. Each band has its own typical class length, its own pedagogical approach, and its own enrollment cycle.

A pre-school dance class runs 30 minutes and focuses on body awareness and music play. An adult contemporary class runs 75 minutes and assumes prior training. Style also splits behavior.

Ballet enrollment is sticky and recital-driven. Hip-hop enrollment is open and drop-in friendly. Ballroom enrollment is couple-based.

Mixing them on one page hurts every query because the right answer for one is the wrong answer for the others. Class schedules also move every term, and a directory showing last spring's schedule in October is worse than not surfacing one at all because would-be families assume the studio is dormant. Programmatic generation makes the maintenance loop manageable.

One row per studio, one cell per schedule, one cache flush per term. The directory stays current with each studio, the page-per-style-and-age structure matches how Google interprets the queries, and editorial work shifts to recital coverage and instructor profiles. SleekRank does not vet studios, but it removes the structural reason dance directory data goes stale.