Kansas City Was 5–0. Seattle Held Mahomes to Three Points and Never Let Him Breathe.

I have a real question for anybody who watched Kansas City walk into Seattle at 5–0 and assumed Patrick Mahomes would figure it out by the fourth quarter: figure out WHAT? The Seahawks beat the Chiefs 20–3 on October 25, and I don't think the final score even does the defense justice. Kansas City never reached the red zone. Not once. That's the first time in 153 Mahomes starts, including the playoffs, that his offense failed to get there. There are ugly offensive games, and then there are nights where the other team takes away practically everything you normally do to survive. Seattle delivered the second one.

The Chiefs had been averaging 414 yards and 28 points coming into the game. They were unbeaten, with Andy Reid's offense and Mahomes doing what everybody has been trained to expect: keep putting pressure on a defense until somebody makes a mistake. And yes, Kenneth Walker III was returning to Seattle as the back in Kansas City's offense. The story practically wrote itself before kickoff. Old running back, unbeaten Chiefs, national television, and an opposing Seahawks team trying to halt a two-game losing streak. Except Seattle's defense wasn't interested in being the background to somebody else's highlight package.

The Numbers Aren't Normal for a Mahomes Offense

The Chiefs finished with 213 total yards and eleven first downs. Mahomes went 19-for-33 for 165 passing yards, no touchdowns and an interception. Walker had 36 yards on fourteen carries. Travis Kelce caught four passes for 44 yards, and Noah Gray matched his 44. Those aren't production numbers that a coaching staff can dress up as an unlucky bounce. When your quarterback is completing short passes but the offense cannot sustain drives or threaten the goal line, the whole structure is struggling. The problem is not one dropped ball. It's that the defense is choosing where the ball is allowed to go.

Seattle's pressure didn't have to look like six sacks to matter. Mahomes was sacked only once, by Derick Hall, but the Seahawks compressed the throwing windows and forced their opponent to play without the explosive answers it usually finds. Safety Ty Okada intercepted Mahomes. Seattle's coverage kept the field feeling longer than it was. Even the Chiefs' one scoring drive ended with a 50-yard Harrison Butker field goal late in the third. They'd already missed earlier opportunities, and Butker finished one-for-three on field goals. Three points. That is a whole lot of football for almost nothing on the scoreboard.

The part I want people to actually study is how Seattle handled the gap between creating pressure and losing defensive discipline. We see it all the time: a defense gets excited about chasing a quarterback, loses contain, and Mahomes makes one ridiculous throw outside the pocket. The Seahawks weren't giving him that escape route nearly often enough. Mike Macdonald didn't need his defense to create a turnover on every series. He needed his defenders to understand their assignments, tackle, win on early downs, and force a quarterback who thrives in broken plays to live in crowded, ordinary football. That's what execution looks like.

Jaxon Smith-Njigba Made Sure the Defense's Work Counted

You still have to score, though, and Seattle had its own answer. Jaxon Smith-Njigba caught nine passes for 150 yards and a touchdown. Sam Darnold completed twenty of twenty-eight for 257 yards, one score and one interception. Smith-Njigba's 28-yard touchdown catch with 1:44 left before halftime gave Seattle a 10–0 lead and was the first moment the Chiefs really looked like they might not be able to turn this around with one good drive. That throw was part of a broader night where Seattle kept finding one receiver capable of beating his coverage rather than pretending the entire offense needed to put on a circus.

Smith-Njigba's postgame explanation matters. He talked about attacking man and press looks, using motion and the middle of the field, and the line-of-scrimmage adjustment Darnold made on the touchdown. That's specific football, not some vague confidence story. If your opponent wants to make you win one-on-one, somebody has to actually win. Smith-Njigba did, repeatedly. And he didn't just have a big fantasy stat line. His catches kept the Seahawks' offense ahead of the problems Mahomes was dealing with on the other side.

Emanuel Wilson ran twenty-four times for 100 yards and scored on a 21-yard fourth-quarter carry. That touchdown came with 3:47 left and put the score at 20–3. I like what that says about how Seattle finished. They didn't need Darnold to force a spectacular throw into coverage just to prove he could hang with Mahomes. They had a lead, stayed physical, and found the running play that ended any realistic comeback. If you want to talk about coaching, tell me why that restraint matters. When your defense owns the game, the offense should be trying to finish the win, not win a popularity contest.

The Injuries Are Part of the Real Story, Too

Not everything went Seattle's way. Rashid Shaheed left with a knee issue and did not play in the second half. Charles Cross exited late with an ankle injury. Macdonald said neither could finish, and the staff had to adjust personnel while preserving the lead. Backup quarterback Drew Lock was also dealing with an elbow problem, although he was available in an emergency. This is why I want more than the final score in a review. You can win by seventeen and still leave with questions about what your offense looks like the next week, particularly when an explosive receiver and your left tackle have to be checked.

For Kansas City, I wouldn't jump straight to declaring the entire offense finished. One terrible night doesn't erase five wins. But you should absolutely stop using the 5–0 start as an answer to what just happened. How did Seattle keep Walker bottled up? Why couldn't the Chiefs use Kelce or the backs to generate enough down-to-down efficiency? Where was the adjustment when Mahomes couldn't push the ball where he wanted? If the only reply is 'he's Patrick Mahomes,' you're not analyzing the game. You're just praying the brand name fixes the film.

6ixTake: Stop Calling This an Upset Like Seattle Got Lucky

People love the word upset because it makes the favorite's loss sound like some freak event. Nah. The Seahawks didn't need a miracle bounce, a tipped Hail Mary, or fifteen Kansas City turnovers. They held Mahomes out of the red zone for an entire night and made an elite offense look like it had nowhere useful to go. Nigga, 213 yards and eleven first downs are not an accident. That's a defensive plan getting executed from the opening drive to the final whistle. Give Seattle the credit instead of spending every minute asking what was wrong with Kansas City.

Macdonald talked afterward about his defense's physicality and the willingness of players like Byron Murphy II, Leonard Williams and Devon Witherspoon to do the work that doesn't always become a highlight. That's the point. A great defense has stars, but it also has people who understand when not to chase a sack or bite on a route. The Seahawks showed that discipline, and their offense did enough to stay out of the way of its own victory. That sounds less glamorous than beating Mahomes in a shootout, but it's a much more sustainable identity.

Play video

6IXTV · ORIGINAL EMBED

Seattle left 4–3 and Kansas City took its first loss, falling to 5–1. That won't settle the entire AFC or NFC discussion, and it shouldn't. What it settles is whether this game was close. It wasn't. Smith-Njigba gave the Seahawks a passing-game centerpiece, Wilson gave them a way to finish, and the defense delivered one of the more complete answers anybody has given Mahomes. There's a difference between surviving the Chiefs and making them look ordinary. Seattle made them look ordinary.