Most teams start with the Sudbury Schools network public list and supplement it with self identified Sudbury inspired schools that may not appear on the official network. SleekRank reads the combined sheet as a CSV. A model lineage column controls whether a school is labeled official network or Sudbury inspired.

A controlled vocabulary lives in a separate tab of the sheet with values like low cost, mid range, premium, and sliding scale. Each row picks one tier. The normalized tier drives per tier hubs, so the column is the source of truth for both the text and hub URLs across the entire directory.

Yes. SleekRank groups by the state column and emits one hub per state at /sudbury-schools/state/{slug}/. The hub lists every Sudbury school in that state, and each school page links back to its state hub and age range hub for consistent internal linking across the directory.

Each row carries unique fields like founding year, judicial committee participation, age range, tuition tier, and state. The template prints those fields in headings and lead copy, so the rendered HTML differs row by row. Schools without enough content can be filtered out at build time using a quality threshold.

A network membership column is a regular field. A school that leaves the official Sudbury network gets re labeled "Sudbury inspired" on its page on the next refresh, and the network membership hub list updates automatically. No redirect is needed because the school continues to operate and keeps the same slug.

Tuition tier is published alongside a clear note on sliding scale availability. Schools with sliding scale that they prefer to discuss in conversation can set the tier to sliding scale and the field hides specific dollar amounts. The remaining fields still drive ranking and discovery.

Often yes for non branded queries. A hub at /sudbury-schools/ages/4-to-19/state/massachusetts/ ships a real HTML list and an entity rich H1, which tends to outrank individual school pages for "4 to 19 Sudbury school Massachusetts" style searches because the entity match is tighter and linking denser.

On a typical WordPress install the first build of 35 school pages plus state, age range, tuition tier, and founding year hubs takes around 3 minutes. After that, only changed rows refresh, so daily cache rebuilds finish in seconds even when several rows update at once during an enrollment cycle.