No. Points, goal difference, and any other computed columns live in your sheet, computed via sheet formulas from the underlying match data. SleekRank renders the values you provide. Some sites maintain raw fixture results in a separate sheet and use sheet formulas to roll up into the standings sheet, which is the most maintainable pattern.

Carry a form column with a fixed-length string like WWDLW for the last five fixtures. The base template includes a form-strip slot with CSS styles for W, D, and L cells. Selector mapping injects the string; template styles transform each character into a colored cell, keeping visual treatment identical across every /league-tables/{slug}/ URL.

Yes, and it's the recommended pattern. Carry a team_slug column on each standings row, then run a separate SleekRank page group at /teams/{slug}/ for per-team pages. The list mapping on the standings table renders each team name as an anchor to /teams/{team_slug}/, keeping internal linking automatic across both URL sets.

Cache duration is configurable per page group. For live matchday updates, 60 to 300 seconds is reasonable; for daily roll-ups after fixtures complete, 3,600 seconds works well; for once-a-week updates in lower divisions, 86,400 is fine. Manual cache flush via wp db query gives an instant refresh when a single result needs correction mid-cycle.

Yes. Carry the season as part of the competition slug like premier-league-2024-25 versus premier-league-2025-26. Each season becomes its own permanent URL. Add a season selector on the base template that links to prior seasons through a related_slugs column on a parent record, preserving the historical archive.

Yes. SleekRank exposes every generated URL through its sitemap and noindexes the base template page automatically. Submit the sitemap in Search Console once; new competition slugs added to the sheet start getting crawled after the next rewrite flush. Old season slugs you keep alive accumulate the archive over time.

Yes. Point the page group's source at a REST endpoint that returns the standings rows. Configure the field mapping to match your league data provider's response shape. SleekRank caches the response per cacheDuration, parses the rows, and renders through the same list mapping the sheet workflow uses.

Yes. Use meta mapping at og:image pointing to a per-competition image URL column, or pair with SleekPixel and a templated suffix so /league-tables/premier-league-2025-26/ renders a preview showing the top three teams' points and form, regenerated automatically as standings change.