Most teams start with the ALC network public list and supplement it with self identified ALC inspired sites that may not be official starter sites. SleekRank reads the combined sheet as a CSV. A network membership column controls how each site is labeled in the directory, either as a starter site or as ALC inspired.

A controlled vocabulary lives in a separate tab of the sheet with values like 5 days per week, 4 days per week, 3 days per week, and mixed schedule. Each row picks one value. The normalized schedule drives per schedule hubs, so the column is the source of truth for both the text and hub URLs.

Yes. SleekRank groups by the city column and emits one hub per city at /agile-learning-centers/city/{slug}/. The hub lists every ALC in that city, and each ALC page links back to its city hub and age range hub for consistent internal linking across the entire directory.

Each row carries unique fields like weekly schedule, age range, starter mentor, and city. The template prints those fields in headings and lead copy, so the rendered HTML differs row by row. ALC sites without enough unique content can be filtered out at build time using a quality threshold.

A status column controls whether a row publishes. A closed ALC gets unpublished and 301 redirected to the city hub, so prior backlinks still land on a useful page. The age range and schedule hubs rebuild on the next cache pass and remove the closed site from every listing automatically.

Starter mentor is a regular field. When mentors change, refreshing the CSV pushes the new mentor name through to the ALC page on the next cache pass. The schema.org Person markup updates with the page, and prior mentor names can be archived in a separate column for historical reference if needed.

Often yes for non branded queries. A hub at /agile-learning-centers/ages/5-to-18/city/charlotte-nc/ ships a real HTML list and an entity rich H1, which tends to outrank individual ALC sites for "self directed school 5 to 18 Charlotte" style searches because the entity match is tighter and linking denser.

On a typical WordPress install the first build of 35 ALC pages plus city, age range, and schedule hubs takes around 2 minutes. After that, only changed rows refresh, so daily cache rebuilds finish in under 15 seconds even when several rows update at once during enrollment season.