Cache duration is configurable per data source, usually twelve hours since tutor availability changes weekly rather than daily. SleekRank re-fetches the sheet or REST endpoint at expiry and re-renders the affected pages, so rates and availability windows stay close to current without manual edits.

Yes. Add a subjects column as a comma-separated list and use a list mapping to render subject pills on each tutor page. Pair with subject collection page groups so each tag links to a /tutors/subject/{slug}/ page for that subject. The same row feeds the tutor profile and every relevant subject index.

Move the row to a /tutors/archive/ feed and keep the page indexed with a not-currently-accepting notice rendered conditionally. Accumulated backlinks survive, and visitors get pointed to similar active tutors. Removing the row entirely emits a 404 and drops the page from the sitemap on the next cache cycle.

Yes. The base page is a normal WordPress page rendered by whatever builder the site uses. SleekRank handles the data replacement layer and works alongside Bricks, Elementor, Gutenberg, and classic themes without touching their templates.

Yes. Run separate page groups against the same data, each with a different base page. SAT prep tutors can render with score-improvement stats, language tutors with conversation samples, and test prep tutors with practice resources. Filter the feed per group by primarySubject column.

Add a bookingUrl column to the row and inject it via selector mapping. The URL can point to the tutor's Calendly, a session booking plugin like Amelia, an email mailto, or a custom booking page on the site. SleekRank does not handle bookings itself; the booking logic lives wherever the URL points.

Use original framing on each page: teaching philosophy, sample lesson outline, student outcome examples, scheduling style. Avoid copying tutor bios verbatim from marketplace profiles. The page adds editorial framing and direct booking that marketplace profiles cannot.

If you collect them and add them as columns, yes. Add a reviews column as a JSON array of review objects with rating, name, and text, then use a list mapping to render review cards. SleekRank does not collect reviews itself; pair with a review collection plugin if you want a full review submission flow.