What Expected Goals Actually Measures (and What It Doesn't)

Every shot in football carries a probability of becoming a goal, and that probability is what expected goals, or xG, tries to put a number on. A tap-in from two yards with an open goal might carry an xG of 0.9. A speculative strike from thirty yards, hit from a tight angle with a defender closing in, might be worth 0.03. Add up every shot a team or player takes over a match, a season, or a career, and you get a total that says roughly how many goals that shot quality should have produced.

The model behind the number looks at thousands of historical shots and asks a simple question for each new one: of all the shots taken from this distance, this angle, under this kind of pressure, with this type of assist, how many went in? Distance and angle to goal do most of the work. Whether the shot was a header or hit with the foot matters. Whether the ball arrived from a cutback, a cross, or a through ball changes the number. Defensive pressure, the goalkeeper's position, and whether it was a one-on-one all shift it further, depending on how detailed the model is.

What xG is not is a prediction for that specific shot. Erling Haaland does not convert 0.9 xG chances 90 percent of the time because he is Erling Haaland; the model does not know who is taking the shot. It knows what the shot looked like geometrically. This is the most common misreading of the stat, and it is worth sitting with, because it explains most of the arguments people have about it.

It also explains why some players consistently score more than their xG suggests they should. A striker who repeatedly beats their expected total over several seasons is probably doing something the model can't see: exceptional placement, unusual composure, or simply being good enough at finishing that average conversion rates don't apply to him. One good month proves very little. Multiple seasons of overperformance start to look like a real skill rather than variance.

The number is most useful in the aggregate, over a run of matches rather than a single game. A team can lose 1-0 while producing 2.4 xG to their opponent's 0.3, and that tells you something a 1-0 scoreline alone cannot: that the process was sound even though the result wasn't. Managers get sacked on the back of results that xG suggests were unlucky, and other managers survive results that xG suggests were flattering. Neither observation changes the final table, but both change how you should read the next few matches.

Where the stat gets misused is when people treat it as a verdict rather than a description. "Team A deserved to win because their xG was higher" skips past everything that actually happened on the pitch: a goalkeeper having the game of his life, a team parking a bus and hitting on the counter, a red card that reshaped the second half. xG describes shot quality. It does not describe game plans, and it does not know that a team was playing with ten men for the last twenty minutes unless you adjust for it, which most public models don't.

There are also real limits to the underlying data. Different providers build their models on different shot samples and different input variables, which is why you'll see two websites disagree on the same match's xG total. Neither is lying; they're just weighting distance, assist type, and pressure differently. None of them account well for a shot taken a split second after a defender got a foot in the way, or a knockdown that arrived at an awkward height. The model reads geometry. It doesn't watch the game.

Used carefully, xG is one of the better tools for separating what a team did from what the scoreline says happened. Used carelessly, it becomes just another number people quote to win an argument they've already decided the outcome of.

For strikers who take a lot of penalties, the more useful number is non-penalty expected goals, which strips the guaranteed value of the spot kick out of the total. And none of this says anything about the goalkeeper on the other end of the shot, which is what post-shot xG is built to measure instead.