Yankees news: Aaron Judge continues to get closer to return

Judge's imminent return reshapes Yankees lineup construction and game-stack strategy across the slate. With his .908 OPS and 53 hits in 214 at-bats this season, Judge represents the kind of high-ceiling contributor that changes implied totals and salary allocation in GPP builds. His absence has forced sharps into secondary stacks and pivot points; his return collapses those alternatives back into the primary Yankees core. The timing matters: if Judge is active, the optimizer immediately reweights Yankees exposure upward, especially in tournaments where ownership on the supporting cast (Volpe, Grisham, role players) has been artificially inflated during his injury.

The specific matchup shapes his play rate. V12's model assigns roughly a 17% homer probability for Judge in his next contest versus Michael King, which is below his season implied rate but meaningful enough to anchor a stack. He's gone six games without a homer and just one in his last fifteen at-bats, which could depress ownership among casual players who chase recent performance. That's a contrarian opening for lineup architects: Judge carries legitimate power equity (17 HR on the year) but may be faded or underowned relative to his salary because of the recent cold streak. Sharps will layer him into two-three-man stacks with the next Yankees hitter, depending on lineup construction and the rest of the slate.

The return also pulls salary away from Volpe and other mid-tier Yankees. If Judge slots back into the cleanup or lead role, those secondary contributors' usage and RBI opportunities compress—a late-swap adjustment worth monitoring as lineups lock. When building Yankees exposure on the mlb dfs optimizer, verify Judge's actual lineup placement and rest status closer to game time; a Judge return changes the shape of your stack ceiling and floor significantly enough that prebuilt constructs need re-checking.