Yes. Store seasons as an array column with one entry per season — year, team, games played, key stats — and use the list mapping to repeat a row inside the profile page for each season. The base template handles the table layout once, and historical seasons stay aligned with the source whenever the array is updated. This is the standard pattern for college programs covering four-year careers.

Update the roster sheet and flush the cache. The page can either reflect the new team if the athlete signed elsewhere in the same league, or 404 if you remove the row entirely. Many agencies keep the row but flag it as 'former' and adjust the template to render an alumni state with the athlete's career history. Either approach handles the change without touching WordPress directly.

Yes. The rest_api source handles JSON endpoints, so a stats provider feed from Sportradar, Stats Perform, or a league-supplied API can drive the per-athlete pages directly. Authentication headers go in the page-group config, and cacheDuration controls how often SleekRank refetches. This keeps the public site aligned with the same source of truth analysts and broadcasters use.

Define one page group per sport with its own sheet and URL prefix like /soccer/athletes/{slug}/ and /basketball/athletes/{slug}/. Each group has its own template page, so per-sport stat fields and layout differences are easy to handle. Multi-sport agencies and federations run this regularly with one WordPress install backing five or more sports.

Yes. SleekRank maps an OG image URL via a meta mapping, so the og:image tag varies per athlete based on a column in the source. Tools like SleekPixel can generate the per-athlete image dynamically from a template that includes the headshot, name, and team logo, then you point the meta tag at the SleekPixel URL pattern. Social previews stay branded across the entire roster.

Each profile is a normal WordPress URL added to the sitemap. The base template stays noindex'd so only the athlete pages appear in search. This means marcus-holloway, elena-ortiz, and the rest each get their own indexable URL targeting the branded name query, while the template URL stays out of the index — the standard SleekRank pattern across page groups.

Add a 'visibility' or 'consent' column to the roster sheet. The template can gate the page based on whether the athlete has signed off on public profile rendering, or skip rendering entirely for rows flagged private. Compliance offices typically maintain that flag alongside eligibility, so the public site stays in sync with the consent status without a separate workflow.

Yes. Add a 'status' column distinguishing roster, recruit, redshirt, or alumni, and use it in the template to adjust which sections render. A recruit page might emphasize hometown and high school; a roster page surfaces season stats; an alumni page shows career retrospective. One sheet, one page group, one template, four rendering modes based on a column value.