Squad depth guide
Kickoff Lens treats squad depth as a football context layer, not as a fantasy list, transfer rumor feed, or copied roster database. The point is to explain how player roles, rotation load, availability visibility, and key-player dependency change a match read.
The World Cup section already contains 1248 player records across 48 teams. The club-football layer will reuse the same idea more carefully: future club player pages stay noindex until role, club, availability context, contribution trend, and source notes are reliable.
Current World Cup squad layer
| Teams with squad data | 48 |
|---|---|
| Player records | 1248 |
| Role mix | Defender 420 · Midfielder 371 · Forward 312 · Goalkeeper 145 |
| Indexable player limit | Only high-value profiles enter the sitemap; lower-signal player pages stay out of search expansion. |
Squad depth scorecard
| Layer | What it means | Publishing rule |
|---|---|---|
| Role clarity | Goalkeeper, defender, midfielder, forward, and hybrid roles need readable context rather than raw roster rows. | Do not publish club-player pages until the role and club are source-backed. |
| Rotation depth | How much a team can change its lineup without losing its core style. | Use as model context, not as a claim of private team news. |
| Key-player dependency | Where one player carries chance creation, control, defense, or finishing value. | Explain dependency from public facts and observed role, not insider availability claims. |
| Availability visibility | Whether injuries, suspensions, minutes load, or lineup uncertainty are publicly visible. | Unknown status stays unknown; do not invent injuries or predicted lineups. |
| Rest and schedule pressure | How fixture congestion, travel, extra time, and tournament load affect player use. | Connect to matchweek briefs and source timestamps. |
| Post-match adjustment | How a player's role or absence changed the final match read. | Connect to post-match recaps with event availability notes. |
League-specific squad depth angles
| Competition | Depth-related radar | Planned module | Seed examples |
|---|---|---|---|
| UEFA Champions League | Away travel, Rotation depth | travel and rest load | Real Madrid: late-game control, knockout experience, and midfield balance; Manchester City: positional control, chance volume, and rotation depth; Bayern Munich: tempo, box pressure, and transition defense |
| Premier League | Rotation depth, Fixture congestion | fixture congestion and European rotation | Arsenal: pressing control, set-piece pressure, and young-core continuity; Manchester City: positional dominance, rotation depth, and chance suppression; Liverpool: tempo, counter-pressing, and transition volume |
| La Liga | Possession control, Chance quality, Press escape | Squad depth and availability context | Real Madrid: chance quality, transition finishing, and late-game control; Barcelona: possession control, high-line risk, and youth integration; Atletico Madrid: defensive compactness, counter timing, and set-piece value |
| Serie A | Rotation stability, Set-piece load | chance suppression and set-piece load | Inter: defensive structure, wing progression, and chance suppression; Milan: wide threat, transition defense, and shot quality; Juventus: block control, set-piece pressure, and game-state management |
| Bundesliga | Youth impact, Rest load | young-player impact tracking; European-workload rebound games | Bayern Munich: box pressure, tempo control, and defensive exposure; Borussia Dortmund: transition volume, youth impact, and high-line risk; Bayer Leverkusen: structure, chance creation, and game-state control |
| Ligue 1 | Squad depth | talent development watch; player pipeline notes | Paris Saint-Germain: talent concentration, pace lanes, and European rotation; Marseille: home pressure, transition energy, and derby intensity; Monaco: young-player output, chance creation, and defensive spacing |
Player page release gate
Club player pages stay noindex until each profile has a role, club, availability context, contribution trend, source note, and rights-safe presentation. A player page that only repeats a name, age, shirt number, or copied bio is not allowed into the sitemap.
Rights-safe publishing boundary
- No club crests, league logos, kit images, player headshots without rights, official profile copies, copied bios, broadcast screenshots, or highlight embeds.
- No private injury claims, predicted lineup certainty, transfer rumors, betting prompts, paid-pick language, or guaranteed-result wording.
- Player and club names are used as text identifiers for independent analysis and reader navigation.
Reader workflow
- Start with club dossier fields to understand the team's style and depth profile.
- Use the radar glossary for squad depth, rest load, and rotation dimensions.
- Use matchweek briefs when fixture congestion or travel changes rotation risk.
- Use post-match recaps after full time to see whether the dependency actually mattered.