Yes. Each row carries arrays for subjects and grade bands plus a format string. List mappings surface them as repeating chips or list blocks on the base page, while tag mappings drive title and h1 so the URL ranks for the right subject-plus-grade combination.

Create a second page group that points at the same feed with urlPattern set to /subject/{slug}/. Add a base WordPress page styled as a subject directory and use a filter at the page-group level so each subject URL only renders tutors who cover that subject. Both groups share the source of truth.

Remove or flag the row. If removed, the URL falls out of the sitemap on the next cache cycle. If flagged inactive, the URL can either be hidden or redirected to a subject index, depending on whether you want to preserve accumulated backlinks for that profile in case the tutor returns later.

Yes. Rate is a column on the tutor row, so each profile renders its own rate. If a tutor charges differently for SAT prep versus elementary reading, model that as a separate row or as a JSON array on the row, then surface it through a list mapping that shows subject-plus-rate pairs.

Add a format column with values like online, in-person, or both, then surface it through a tag mapping on the base page. You can also filter the per-subject index by format so /subject/sat-math/?format=online filters down to remote tutors only, useful for online-first agencies competing against Wyzant.

Yes. Add a weekly availability column with structured strings or a JSON array, then surface it via a selector or list mapping in the base page as a schedule block. The sheet is the source of truth, so coordinators update windows in one place and every tutor page reflects the change after the next cache flush.

SleekRank renders pages and does not handle bookings or payments. Embed your existing booking tool, like Calendly or a custom CRM form, on the base page template and pass the tutor slug through hidden fields so the booking lands in your pipeline tagged to the right tutor without manual reconciliation.

Optional. For a small agency, a city column on the tutor row plus mention in the bio is enough. For larger agencies covering many cities, run a third page group at /tutors-in/{city}/ that reads the same feed filtered by city. The roster stays single-sourced, but the SEO footprint grows across tutor, subject, and city axes.