With The First Pick
Fansided

Kansas City Chiefs: Why they released top WR Jeremy Maclin

By Maurice Barksdale

Dec 6, 2015; Oakland, CA, USA; Kansas City Chiefs wide receiver Jeremy Maclin (19) runs with the ball before the start of the game against the Oakland Raiders at O.co Coliseum. Mandatory Credit: Cary Edmondson-USA TODAY Sports
Dec 6, 2015; Oakland, CA, USA; Kansas City Chiefs wide receiver Jeremy Maclin (19) runs with the ball before the start of the game against the Oakland Raiders at O.co Coliseum. Mandatory Credit: Cary Edmondson-USA TODAY Sports /
facebooktwitterreddit

The Kansas City Chiefs shockingly released their top receiver Jeremy Maclin.  But why would they release him when they have no one proven to take his place?

When the Kansas City Chiefs signed wide receiver Jeremy Maclin in 2015 it made a lot of sense on so many levels.  For one, head coach Andy Reid had coached Maclin when they were both with the Philadelphia Eagles.  So he knew what he could do and what to expect.

Secondly, before Maclin arrived the Kansas City Chiefs had no number one wide receiver.  So the signing of Maclin was a move long over due.  But the Chiefs saw enough and even with Andy Reid’s closeness with Maclin, he decided to let him go.

Must Read: Seattle Seahawks have forgotten what made them champions

Now with the release of Maclin, the Chiefs seem to have come full circle to where they were before they signed him.  They don’t have a number one receiver.  At least they don’t at the wide receiver position that is.

Their top pass catcher is a tight end in Travis Kelce.  It’s obvious now that the Kansas City Chiefs see Travis Kelce as their top receiver now and they seem fine with that.  No one else they have at wide receiver is the proven commodity Travis Kelce is.

There’s talent there with Chris Conley and the speedy Tyreek Hill.  However, neither has proven the consistent threat that Maclin was.  So why did the Chiefs feel they could to roll the dice and release Jeremy Maclin?

Because they didn’t think he was worth what they were paying him.  Yes, the move gives them some salary cap relief ($10 million).  But if the Andy Reid thought Macklin was worth the money, he would have never released him.

Also, Maclin missed four games down the stretch last season and the Chiefs went 3-1.  They saw what life is like without Jeremy Maclin and knew they could win without him.  The Kansas City Chiefs are not a heavy passing team and Reid feels he can get similar production from the receivers he has but for a cheaper price.

Next: NFC South: Top 4 Impact Free Agent Signings

Jeremy Maclin will make a very good number two receiver for some team out there and perhaps a number one.  However, the Chiefs were paying Jeremy Maclin as their number one receiver but it was tight end Travis Kelce who was their top receiving threat.

Home/NFL News