Sources and Methodology

Shared data sources

Headline career totals, six-team totals, assists, scoring methods and body-part aggregates are attributed to RonaldoStats.app at its stated source date. The publisher provides no data-reuse licence, so Ronaldo Records imports only limited factual aggregates and does not describe them as independently verified. Detailed season, goal-event, competition, opponent and Portugal rows continue to come from revision-pinned English Wikipedia pages through the MediaWiki Action API under CC BY-SA 4.0.

Wikipedia itself cites sources such as the Portuguese Football Federation, Soccerway and WorldFootball.net. Those references support Wikipedia’s table; this site does not claim a direct data feed from them.

Counting policy

• Included: official senior first-team matches for Sporting CP, Manchester United, Real Madrid, Juventus, Al Nassr and Portugal.
• Excluded: Sporting CP B, youth teams and other reserve football.
• Manchester United’s two spells are merged into one team total.
• Club and Portugal rows are summed once; source grand-total rows are used only for reconciliation, not added again.
• Combined calendar-year goals are derived from the senior career goal-event table; Portugal-only yearly appearances and goals remain separately labelled.

Automatic checks and validation

The existing scheduler checks Wikimedia approximately every 30 minutes and performs a cached conditional RonaldoStats.app aggregate check no more than once every six hours. A candidate update must contain all expected teams, a plausible career range, at least 20 Portugal calendar-year rows and totals that reconcile exactly. An unchanged source reuses its existing snapshot, preventing duplicates.

If retrieval, parsing or validation fails, the candidate is rejected and the last valid snapshot remains published. Missing figures are not converted to zero. Large unexplained regressions are also rejected pending review.

Cutoff versus check time

The statistical cutoff is the match date printed by the source. The check time is when this WordPress installation last requested the source. A successful check does not mean the source has already incorporated the latest match. That publication delay is why both timestamps are shown.

Corrections

Every changed dataset becomes a new immutable snapshot with its source revision and checksum. Historical snapshots remain in the database, allowing a later source correction to be audited. The public site always reads one designated, fully validated snapshot.