Shots on Target vs. Total Shots: What They Really Measure
Shots on Target vs. Total Shots: What They Really Measure
A shot on target is any deliberate attempt that would have gone in without a save or a last-line block. Total shots is the full count: every attempt at goal, on target or not, including most blocked efforts depending on the provider. The relationship is simple math:
Total shots = Shots on target + Shots off target (with blocked attempts often tracked as their own category).
- A striker curls a finish into the bottom corner: it counts as a shot and a shot on target, since it beat the goalkeeper outright.
- A midfielder blasts one over the bar from 30 yards: it counts as a shot, but never as a shot on target, since it never threatened to go in.
That distinction, on target versus off target versus blocked, is where most fan confusion about shots on target vs total shots explained actually starts.
Key Takeaways
Shots on target measures whether an attempt actually tested the goalkeeper, while total shots counts every attempt regardless of accuracy, and neither number reveals chance quality without expected goals.
| Point | Details |
|---|---|
| Core formula | Total shots equals shots on target plus shots off target, with blocked attempts often tracked separately. |
| Provider definitions align closely | Opta and Sportmonks both count goals and keeper saves as shots on target, excluding shots blocked before reaching the keeper. |
| Scorer discretion drives most disputes | Intent calls on crosses, blocks, and woodwork explain why different feeds sometimes disagree by one or two shots. |
| Accuracy alone isn’t enough | Shot accuracy (SOT divided by total shots) should be paired with xG or Big Chances to judge chance quality, not just volume. |
| Live tools show the full picture | Shot maps and momentum tracking turn raw SOT and total shot counts into context you can actually read during a match. |
Table of Contents
- Shots on Target vs. Total Shots Explained by the Data Providers
- Why Blocks, Woodwork, and Crosses Cause Confusion
- Turning Shot Counts Into Real Analysis: Accuracy, xG, and Big Chances
- How Betsyscore Puts These Stats to Work
- See These Stats in Action
- The Editorial Take: Stop Treating Shots on Target as the Whole Story
- Sources
- FAQ
Shots on Target vs. Total Shots Explained by the Data Providers
The cleanest way to settle any argument about these numbers is to go straight to how the people who count them define the terms.
Opta’s event definitions describe a shot on target as a deliberate attempt to score that is, in fact, on target, a category that includes both goals and shots the goalkeeper saves. Opta calculates shooting accuracy as shots on target divided by total shots, with blocked attempts and own goals excluded from that ratio. That last part matters: a team can rack up ten blocked shots and still show a tidy shooting-accuracy percentage, because those blocks never entered the equation.
Sportmonks frames it almost identically but adds a useful clarification: shots blocked before they reach the goalkeeper, whether by a defender stepping into the passing lane or a last-ditch slide, do not count as shots on target. Only attempts that test the keeper, or that a defender stops on the goal line acting as the last line of defense, make the cut. That framing is what makes shots on target a cleaner read on finishing threat than total shots. It filters out the blocked, deflected, and wayward attempts that inflate a shot count without ever pressuring the goalkeeper.
A few practical clarifications follow from this:
- Penalties count as both a shot and, if struck on target, a shot on target, regardless of the outcome.
- Headers and deflected efforts count the same as any other shot, provided the deflection still travels toward goal.
- Rebounds are treated as fresh shot attempts, so a saved shot followed by a scrappy tap-in generates two shots, not one.
- Providers that separate “blocked shots” as their own category, rather than folding them into total shots, tend to give analysts a more complete picture of how much defensive pressure a team faced.
A shot on target includes goals and shots saved by the goalkeeper or blocked by a last-line defender. Shots blocked before reaching the keeper are not counted as shots on target.
That one sentence resolves most disputes fans have when comparing a broadcast graphic to a betting app’s live feed.
Why Blocks, Woodwork, and Crosses Cause Confusion
Most disagreements over shot counts come down to three gray areas: where a block happens, what hitting the woodwork means, and whether a given play was even a shot.
- Where the block occurs. A shot smothered by a midfielder 25 yards out is a blocked attempt, full stop. A shot that a defender stops on the goal line, acting as the last man, often still counts as a shot on target under Opta and Sportmonks rules, because it would have gone in without that intervention.
- The woodwork rule. Hitting the post or crossbar only counts as a shot on target if the ball goes in on the rebound or would clearly have gone in absent the woodwork. Most post-and-out efforts are logged as shots, not shots on target, which surprises casual fans who assume “hit the post” automatically means “on target.”
- Intent and the shot-versus-cross question. A low ball whipped across the box that a keeper has to palm away might get scored as a shot on target by one provider and as a cross by another, depending on whether the scorekeeper judged the player was actually aiming for goal. Action Network’s breakdown of prop-betting counts points to exactly this subjectivity as the main reason bookmaker totals and broadcast graphics sometimes disagree on the same match.
That third point explains most of the “why doesn’t this stat match what I saw on TV” moments. Scorekeeper judgment, not a hidden rulebook, drives the gap.
Pro Tip: If a shot gets immediately smothered inside the box and never reaches the keeper, expect it logged as a blocked attempt in most feeds. If it’s stopped on the goal line by the last defender, many providers still count it as a shot on target.
For bettors specifically, this variability is worth knowing before placing a shots-on-target prop, since two operators can post different lines off the same match because their data source made a different intent call on one or two plays.
Turning Shot Counts Into Real Analysis: Accuracy, xG, and Big Chances
Shot accuracy is the fastest way to turn these two raw numbers into something useful. The formula is straightforward: shots on target divided by total shots. A team with 6 shots on target from 15 total shots is shooting at 40% accuracy, a reasonable clip. A team with 4 shots on target from 20 attempts is at 20%, which usually points to low-quality, speculative shooting rather than a lack of possession.
But accuracy alone still misses the most important question: how good were those chances? That’s where Big Chances and expected goals (xG) come in. Big Chances flag situations where a player should reasonably be expected to score, while xG assigns each shot a probability value based on distance, angle, and defensive pressure. Two teams can finish a match with identical shots-on-target totals, say 5 apiece, yet post wildly different xG figures if one team’s shots came from tight one-on-ones and the other’s came from speculative long-range efforts a keeper barely had to move for, a concept explained in detail by How a Poisson Goal Model Predicts Football Match Scores.
| Stat | What It Tells You |
|---|---|
| Shots on target | Direct pressure applied to the goalkeeper |
| Total shots | Overall shooting volume, including blocked and off-target attempts |
| Shot accuracy (SOT/total shots) | How efficiently a team is finding the target |
| xG | The quality of chances created, independent of whether they were scored |
| Big Chances | Situations a player should reasonably be expected to convert |
Sportmonks notes that shots on target measure whether a team tested the keeper, not whether the chances themselves were dangerous, which is exactly why analysts pair SOT with xG and save percentage when judging attacking efficiency or a goalkeeper’s actual workload. For a fast read during a live match, shots on target tells you who’s pressuring the goalkeeper right now; xG tells you who’s actually generating the better chances.
How Betsyscore Puts These Stats to Work
Betsyscore surfaces shots on target and total shots side by side in every live match view, alongside shot maps that plot exactly where each attempt came from on the pitch. That combination turns a bare number into context: you can see whether a team’s shot volume came from central, high-danger positions or from the wings, where accuracy tends to drop.
Those same inputs feed into Betsyscore’s broader analysis layer:
- Shot maps show shot location and outcome for every attempt in a match, which you can explore further in Betsyscore’s shot map guide.
- Momentum tracking blends shot volume, shot quality, and territory to show which side is controlling a match minute by minute.
- AI-powered predictions weigh shots on target, total shots, and expected-goals patterns alongside form and head-to-head history to generate win-probability percentages, a process explained in Betsyscore’s expected points (xP) breakdown.
Readers who want to sharpen their in-match reading further can also check Betsyscore’s guide on interpreting live match statistics, which walks through how to weigh SOT against xG when a match is still unfolding.
See These Stats in Action
Understanding the gap between shots on target and total shots is one thing. Watching it play out in real time, as shot maps update and win probabilities shift with every attempt, is where the numbers actually earn their keep. Betsyscore’s live match center tracks both stats alongside shot maps and momentum for every fixture in progress, and the AI predictions page shows how those same inputs, shots on target, xG, form, and head-to-head data, combine into a single win-probability read before kickoff.
The Editorial Take: Stop Treating Shots on Target as the Whole Story
Shots on target deserves its popularity. It’s a far better proxy for goalkeeper pressure than total shots, and it strips out the harmless long-range efforts that make a box score look busier than the match actually was. But the conventional fan habit of treating SOT as a standalone verdict on “who deserved to win” doesn’t hold up. A team can post eight shots on target from low-value positions and still generate less actual danger than a team with five shots on target from point-blank range.
The real fix is cheap and simple: never read shots on target in isolation. Pair it with shot accuracy to judge finishing discipline, and pair it with xG or Big Chances to judge whether the chances themselves were worth having. Total shots, meanwhile, is worth tracking mainly as a pressure indicator, not a quality one. Fans who make that one adjustment, checking chance quality alongside chance volume, will read match stats more accurately than most pundits working off box scores alone.
— Aria
Sources
FAQ
What Is the Difference Between a Shot and a Shot on Target?
A shot is any attempt at goal, on target or not, while a shot on target is specifically an attempt that would have scored without a save or last-line block.
Are Shots on Goal the Same as Shots on Target?
Yes, “shots on goal” and “shots on target” refer to the same statistic; broadcasters and American commentators tend to use “on goal,” while data providers like Opta and Sportmonks use “on target.”
What Determines Whether a Shot Counts as On Target?
A shot counts as on target if it results in a goal, forces a goalkeeper save, or is stopped by a defender acting as the last line of defense on the goal line; shots blocked earlier are not counted as on target.
Does a Shot That Hits the Post Count as a Shot on Target?
Only if it goes in on the rebound or would clearly have gone in without the post; most post-and-out attempts are recorded as shots, not shots on target.
Why Do Different Websites Show Different Shot Counts for the Same Match?
Differences usually come from scorekeeper judgment calls on intent, such as whether a play was a shot or a cross, rather than a factual error in the data.