Corners and shots on target: understanding the differences
Both can reflect attacking activity, but they record different events. One should never be presented as a replacement for the other.
What a corner records
A common route to a corner is the defending team touching the ball last before it goes wholly over its goal line without a goal. The laws also provide corner sanctions in other circumstances. Possession and attacking intent do not themselves add a corner to a recorded total. Whether an operator counts awarded or taken corners belongs to its settlement rules.
What a shot on target records
A shot on target is a scoring attempt recorded as heading into the goal unless stopped by the goalkeeper or a defending player in circumstances counted by the data provider. A shot can be on target without producing a corner, and a corner can result without any shot on target.
Provider definitions and event corrections can affect recorded totals. The market and settlement source should therefore be checked rather than assuming every statistics provider will classify a marginal event identically.
Team and match totals are different
A match-total line combines both teams. A team section, when present, concerns only that side. DeePicks automatic free tips use only specifically supported match-total corner and shots-on-target lines; they do not manufacture a total from missing team sections or expose an unsupported line.
Coverage can differ
Corner data may be available for a fixture while shots-on-target data is missing, or the reverse. The engine marks a market unavailable when its required input or model output is absent. Missing data does not imply a low total, and it should not be interpreted as a zero-percent outcome.
Keep uncertainty attached
Match state can change event counts quickly: an early goal, red card, tactical shift, or game with little time remaining can alter how teams attack. Historical patterns inform an estimate but cannot guarantee the next match total. The displayed probability remains an estimate, not a promise or proof of profit.
Source definitions: a restart is not a shot
IFAB Law 17 explains corner restarts, including the usual last-touch/goal-line situation. IFAB's laws govern play; they are not a bookmaker settlement feed. Check the applicable season and competition rules rather than assuming the common situation is the only way a corner can be awarded.
In Opta's event definitions, goals and attempts stopped by the goalkeeper can be shots on target; a last-line defender preventing a goal can qualify too. Ordinary blocked attempts are a separate category. These definitions are a reference example, not a claim that every DeePicks input uses Opta or that Opta endorses this guide.
A goalkeeper tipping an on-target attempt behind can produce both an SOT and a corner. A defender diverting a cross behind can produce a corner without any SOT. Do not add corners to SOT to estimate attacking attempts: that double-counts some sequences while combining different events.
Worked example: pressure does not make the totals interchangeable
Hypothetical teaching example. The following invented counts are not real fixtures or predictions. Assume the counts have been confirmed under the relevant provider definitions for the full-match period.
| Example | Corners | SOT | Outcome |
|---|---|---|---|
| A | 9 | 3 | Over 8.5 corners: Yes. Over 6.5 SOT: No. |
| B | 4 | 8 | Over 8.5 corners: No. Over 6.5 SOT: Yes. |
For A, nine exceeds 8.5 while three does not exceed 6.5. For B, the answers reverse. Calling either side “attacking” does not tell us which threshold was crossed. Separate events need separate counts, and separate forecasts need their own estimates.
Worked example: missing is not a losing total
Hypothetical teaching example. Suppose a record contains home corners 5 and away corners 4, but home SOT is missing and away SOT is 3. The corner total is 5 + 4 = 9. The SOT total remains unknown; treating it as 0 + 3 would invent a home observation. Neither a complete corner total nor a partly known SOT total supplies the missing value.
The same distinction matters when reviewing a saved selection. Missing required settlement statistics need review rather than an automatic loss. A forecast's generation time is not a settlement observation, and an AVAILABLE prediction does not prove that a later result has been collected.
Check these interpretation errors
- Do not confuse a team line with a match total or a halftime count with a full-match count.
- Do not classify every blocked attempt as SOT or every corner as evidence of an on-target attempt.
- Do not use a complete goals record to fill missing corner or SOT history.
- Check the named settlement provider and correction window; a source may revise a marginal event.
Read the market-specific history gates and keep the statistic definition, exact line, period and timestamp together. No count or probability here establishes a favourable bookmaker price.