What WhoScored Publishes and Where the Opta Depth Stops
WhoScored is a football analytics site run from London, and every figure on it rests on Opta data. That shapes what a WhoScored scraper can reach: the event data comes from Opta, and the ratings and characteristics on top are the platform's own.
Coverage and depth are two separate questions here. The tournament menu currently carries 433 competitions across 114 regions, from the Premier League down to regional and continental minor cups, and scores, fixtures, lineups and tables run across all of them. Event detail does not. The competitions that carry it are named in the player comparison filter, 46 of them: the top five European leagues, the senior English tiers below them, Eredivisie, Liga Portugal, Super Lig, MLS, Copa Libertadores, the European club competitions and the major national-team tournaments. Anywhere else a player row shows apps and goals with N/A in the minutes, shots, pass success and rating columns. The scores data marks the split itself with an isOpta flag on the stage and a matchIsOpta flag on the fixture, so a crawl can tell in advance which games repay a deep pass.
Addresses are numeric and predictable. A match lives at /matches/{id}/{tab}/ with tabs for live, livestatistics, matchreport, preview and betting; a team at /teams/{id}/{tab}/ with fixtures, statistics, refereestatistics and archive; a player at /players/{id}/{tab}/ with matchstatistics, fixtures and history; a season at /regions/{region}/tournaments/{tournament}/seasons/{season}/stages/{stage}/{tab}/. The trailing slug is decoration: it is translated on the language subdomains while the numeric id stays put, so ids are the join key and the slug never is.
Get a Quote