What stats matter for NFL receiving yards props?

Read targets and the player’s role before relying on a receiving yards average. Then separate the depth of the opportunities from the catches and yards they actually produced.

Start with opportunity

Targets count passes directed at the player. Target share puts that count in the context of the team’s passing opportunities. Five targets in a small passing game and five in a busy one describe different shares of the offence.

Offensive snap share adds another check. Being on the field creates the possibility of a target, but it does not say the player ran a route on every snap. Route participation, where a reliable source supplies it, answers that narrower question. We do not fill in a missing route count with snap share.

Read the rows around a change in personnel or quarterback. A season average can mix roles that no longer exist.

A four-game example from our own log

Drake London’s completed 2026 games in the October 9 export show why the yardage average needs those other columns.

26 targets, 20 catches, 370 yards. Per game, 6.5 targets, five catches and 92.5 yards.

The 194-yard game contributed 52.4% of all the yards in that window. The other three averaged 58.7 yards. We keep that big game in the record; isolating it explains how the average was formed rather than deciding which games count.

The two five-target games also produced different results: two catches for 29 yards and four for 51. A target count is opportunity, not a yardage outcome.

Read depth and conversion separately

Air yards and average depth of target describe where passes are being sent. Receiving yards describe what was gained on completed catches, including yards after the catch. Incomplete targets can contribute air yards without contributing receiving yards.

A deeper role and a short-pass role can arrive at a similar receiving total through different routes. Read depth alongside target volume and catches. Where after-catch data is available, it helps explain the remaining yardage; where it is missing, keep that gap visible.

Provider coverage matters here. Our usage fields include play-by-play inputs, and a target total from one feed may not cover exactly the same plays as an air-yard total from another. Check the denominator before calculating an average depth yourself.

Compare the relevant role against the defence

On the player’s Head to Head tab, the Same role vs block for that opponent shows the comparable receivers who faced that defence, with their targets and catches beside their yards. A large total on a large workload is different from the same total on a few catches.

Read the role label and season. WR1 is a comparison role chosen by the pipeline, not a claim that the player lined up in a particular spot on every play or faced one cornerback throughout the game.

For the defence’s season so far by position, NFL Defense vs Position shows the targets, receptions and receiving yards each team has allowed to wide receivers and tight ends, with the game count behind each figure.

Keep the sample visible

The early-season NFL hit-rate page explains how a recent window can reach into last season. The L5 and L10 trends page explains why a visible streak does not establish a good bet.

This example has four games. It shows how to read the inputs; it does not test their value beyond a posted receiving line, estimate a fair price or predict London’s next total.

Source: Steezanomics’ October 9, 2026 NFL export. London example covers September 13 through October 5, 2026, with every completed row in that window retained.

Open Drake London’s receiving yards page in the Lab on a day his next game is on the board. The Game Log tab lists each game’s receiving yards against the line, and the Head to Head tab’s Same role vs block shows the comparable receivers’ targets and catches beside their yards. Between games his page keeps the game log without a line. For another receiver, use the Lab board and select NFL, then REC YDS.