Cache duration is configurable per page group. Setting it to 60 seconds means standings refresh at most once a minute, which is enough for nearly any public competition without hammering the source. Shorter intervals are possible, but most sources rate-limit or cost money per call, so 60 to 300 seconds is a healthy floor for live use. For weekly or monthly leagues, 86,400 seconds is more typical.

Yes. Run wp db query "DELETE FROM wp_319_sleek_rank_items" to clear cache immediately. The next request to any /leaderboards/{slug}/ URL refetches data from the source. Operators with mid-cycle corrections, like fixing a disputed score, can flush, edit the source, and have the new standings live within one page load.

Yes. For sources behind auth, configure the page group's REST source with the right credentials, then put the resulting WordPress pages behind a membership or capability check via your existing access plugin. Internal sales leaderboards work this way: the standings are real-time but only visible to logged-in team members.

Yes, and this is the recommended pattern. Add a leaderboard_slug column on each row, fill it with values like sales-q1-2026 or coding-challenge-week-12, and the page group filters rendering per slug. Adding a new leaderboard is appending rows under a new slug value, no new page group needed unless schema differs significantly.

Carry the rank explicitly in a rank column and use the same rank value for tied competitors, with a tie_breaker column to control display order within the tie. SleekRank renders the rank you provide; deciding how ties resolve is part of the scoring logic, not the page. Some leagues prefer dense ranking (1, 2, 2, 3), others standard (1, 2, 2, 4); both work.

Yes. SleekRank exposes every generated URL through its sitemap and noindexes the base template page automatically. Submit the sitemap in Search Console once; new leaderboard slugs added to the source start getting crawled after the next rewrite flush. For private leaderboards, exclude the URL pattern from the sitemap output via standard sitemap filters.

Yes. The base ranking page is a normal WordPress page, so any chart block or script works. Carry the data you want charted in its own row column, expose it as a JSON blob via selector mapping, and let your chart library read from that DOM node. The rendered leaderboard and the visual then share the same source data.

Two patterns work. Either keep the slug permanent and let the data row stop receiving updates (the page freezes at the last cached state) or add a status column like archived and filter the list mapping to hide rows where status equals archived. The URL keeps resolving but the standings table shows the final state.