Yes. The rest_api source handles authenticated JSON endpoints, which is the natural shape for a platform-backed directory. Point SleekRank at the directory endpoint that already serves the platform's frontend and the same data drives the per-creator page generation.

Cache duration controls freshness. Set it to match the platform's metric sync cadence so pages refresh on the schedule that matches reality. Weekly metric updates pair well with a 24-hour or seven-day cache; daily updates can run shorter cache windows.

No. SleekRank links to whatever payment or checkout flow the creator already uses. The page renders the link from a column, so a Substack subscribe URL, a Gumroad product link or a custom Stripe checkout all flow through the same selector mapping. Payment lives where it lives.

Add a status column to the directory and filter paused creators out of the data feed before SleekRank reads it. The platform keeps the row internally for billing or comeback flows, but the public sitemap drops the URL until the status flips back to active.

Yes. Store recent posts as an array per creator with title, date and URL, and render through the list mapping. Refresh cadence depends on cache duration. Pair with a worker that syncs the array from the creator's RSS, API or platform-native source on a schedule.

Each profile URL is a real WordPress page in the sitemap, indexable and shareable. The base template stays noindex'd so only creator pages compete in search. Person, CreativeWork and Product schema added once to the template propagates across every profile in the directory.

Yes, within the template's mapped fields. Add columns for accent color, custom intro paragraph or pinned product and let the template render conditional blocks. The platform stays in control of structure; creators control content per row. No one-off page edits required.

Either pick a primary platform per creator and store the rest as an array of secondary handles, or model platforms as separate rows keyed by creator-plus-platform. The first pattern keeps URLs simple; the second creates per-platform indexable pages when each platform deserves its own ranking surface.