Most teams start with the National Microschooling Center public list and supplement it with state ESA participating provider lists. SleekRank reads the combined sheet as a CSV. The sheet stays the source of truth, and ESA acceptance, model, and state columns drive their own hubs without duplicate authoring.

A controlled vocabulary lives in a separate tab of the sheet with values like Acton inspired, Prenda, self directed, project based, and outdoor mixed age. Each row picks one or more values. The normalized model drives per model hubs, so the column is the source of truth for both the page text and hub URLs.

Yes. SleekRank groups by the state column and emits one hub per state at /microschools/state/{slug}/. The hub lists every microschool in that state, and each microschool page links back to its state hub and model hub for consistent internal linking across the entire directory.

Each row carries unique fields like model, age range, ESA acceptance, tuition, and state. The template prints those fields in headings and lead copy, so the rendered HTML differs row by row. Pods without enough unique content can be filtered out at build time using a quality threshold check.

A status column controls whether a row publishes. A closed microschool gets unpublished and 301 redirected to the state hub, so prior backlinks still land on a useful page. The model hubs rebuild on the next cache pass and remove the closed school from every listing automatically.

Tuition is optional. Microschools that prefer not to publish a range can leave the column blank and the field hides automatically from the rendered page. The remaining fields still drive ranking, so the lack of tuition data does not penalize a microschool in the directory's ordering.

Often yes for long tail queries that include a state or metro. A hub at /microschools/model/acton-inspired/state/arizona/ ships a real HTML list and an entity rich H1, which tends to outrank a national brand page for "Acton inspired microschool Arizona" style searches because the entity match is tighter.

On a typical WordPress install the first build of 700 microschool pages plus state, model, and ESA hubs takes around 20 minutes. After that, only changed rows refresh, so daily cache rebuilds finish in under a minute even when several dozen ESA program updates land in the sheet at once.