Parents and students rarely search for "tutor". They search for "GCSE maths tutor in Bristol", "SAT prep tutor Orange County", or "AP biology tutor near Pasadena". The query bundles subject, exam, level, and location, and each combination is its own ranking target. A single archive page filtered by subject cannot win those long-tail terms because Google ranks pages, not query-string filters.

SleekRank uses an existing WordPress base page as the template and reads a tutor roster from a Google Sheet, Notion database, or REST endpoint. Each tutor row becomes one URL with slug, name, subject, level, city, and hourly_rate mapped into the page. Add a row when a new tutor joins, archive a row when one leaves, and the directory updates on the next cache flush.

Subject and city hubs come from the same source. A second page group with /tutors/{subject}/{city}/ produces /tutors/maths/bristol/ and /tutors/sat-prep/orange-county/ from joined data. Tag, selector, list, and meta mappings handle the wiring; the sitemap auto-includes every URL and removes archived rows on the next refresh.

Tutoring search is bundled by definition. Parents type the subject, the exam board, the level, and the city, because tutoring is a high-trust local purchase and the budget commitment is real. A single archive page filtered by subject cannot rank for "GCSE maths tutor in Bristol" because Google ranks pages and the URL has to match the bundled intent.

Manual directory pages work for the first 30 tutors; past that, roster drift takes over. New tutors join, hourly rates shift, qualifications expand, exam boards update, and the directory stops matching the agency's actual booking calendar. SleekRank turns the roster into the SEO surface, which collapses the gap between the team that books lessons and the team that publishes URLs.

Each row maps to one page through declarative mappings, combinations like subject plus city come from a joined set, and the sitemap auto-includes every URL. The base page belongs to the theme, so design, tracking, and CRO experiments stay where they always lived. Adding a tutor becomes a row in the sheet rather than a developer ticket.

The directory stops being a static brochure and becomes a live view of the actual roster.