KCKingdom
Fansided

Kansas City Chiefs: Pros and cons of cutting Jeremy Maclin

Dec 27, 2015; Kansas City, MO, USA; Kansas City Chiefs wide receiver Jeremy Maclin (19) celebrates after catching a touchdown pass against the Cleveland Browns in the first half at Arrowhead Stadium. Mandatory Credit: John Rieger-USA TODAY Sports
Dec 27, 2015; Kansas City, MO, USA; Kansas City Chiefs wide receiver Jeremy Maclin (19) celebrates after catching a touchdown pass against the Cleveland Browns in the first half at Arrowhead Stadium. Mandatory Credit: John Rieger-USA TODAY Sports /
facebooktwitterreddit
Prev
3 of 6
Next
Kansas City Chiefs wide receiver Jeremy Maclin (19) – Mandatory Credit: Cary Edmondson-USA TODAY Sports
Kansas City Chiefs wide receiver Jeremy Maclin (19) – Mandatory Credit: Cary Edmondson-USA TODAY Sports /

CON: UM… WHO IS GOING TO PLAY RECEIVER?

The biggest head scratcher to all of this is that the Kansas City Chiefs have no viable receiver options, a problem stemming back to… Well, forever. The Chiefs have never been a team known for their receiver depth and now they have almost no one to play the position.

You’ll hear a lot of people talking about how Demarcus Robinson is going to be the next guy to step up or that Chris Conley is going to shine in 2017, but let’s be real here. Neither of those guys are number one receivers. Conley has had two years to show his worth and he’s been bad. Yeah, and Robinson did nothing last season.

Maclin might not have been a true number one wideout, but the Chiefs don’t have anyone even close to filling that role.

Tyreek Hill was fun to watch, but his size is going to limit him. Plus, if he’s the number one option, it’s probably not wise to have him return kicks and punts, which is where he excels at.

At the end of the day, Maclin might not have been a true number one wideout, but the Chiefs don’t have anyone even close to filling that role.

This upcoming season could be like 2014 all over again.