Counting a player’s trophies requires more than matching a club and season

A trophy list appears simple: identify the winning team, find the player's club in that season and add one. That shortcut fails whenever a player transfers, goes on loan, appears for multiple teams in the same competition year, or is registered without meeting a chosen participation rule. A club-season match proves association, not necessarily that the honour belongs in the player's personal record.

The first fact to verify is the competition outcome. The IFAB Laws define the winning team at match level, while competition organisers publish the season winner and their own regulations. The second fact is player association: which team employed or registered the player during the relevant period? The third is eligibility under the site's stated methodology. Those are separate claims and should have separate evidence.

Different questions can produce different defensible totals. One list may count every competition won while a player was registered. Another may require an appearance. A medal-based list may depend on allocation rules that vary by organiser and season. UEFA regulations explicitly discuss trophies and medal allocations at competition level. A website must state which concept it counts instead of presenting one total as self-explanatory.

Transfers create a dangerous automated error. A player's season-stat row can show participation for one club while a trophy feed records a winner without identifying the winning team in the same record. Joining those rows on player, competition and season can attach the honour to the participant's losing club. Both source rows may be individually accurate; the inferred relationship is false.

Duplicates arise when competition names vary, split seasons use different labels, or the same honour is returned through club and player endpoints. Normalising text helps identify candidates but cannot decide whether similarly named tournaments are identical. Youth leagues, reserve competitions, super cups and friendly invitation events also need explicit inclusion rules. Hiding those choices inside code makes totals impossible to audit.

FootIndex uses a conservative publication gate. Vendor honours enter a private candidate queue. Participation evidence may suggest a team, but it is not enough for automatic publication. A record needs an independently verified winner, correct team association, valid season and documented inclusion decision. Uncertain records remain invisible; career totals count only published verified rows.

This approach produces smaller totals than permissive databases while historical evidence is processed. That is intentional. Missing data says verification is unfinished. A wrong 'verified' trophy changes comparisons, rankings and search snippets with false confidence. In an evidence-led product, the honest blank is more useful than the impressive guess.