Skip to main content

Best team fits for 2016 NFL Draft's top wide receivers

Baylor's Corey Coleman, Ole Miss' Laquon Treadwell, TCU's Josh Doctson and Ohio State's Michael Thomas were ranked among the top wide receivers available in the 2016 NFL Draft by NFL Media analysts Daniel Jeremiah and Bucky Brooks on Monday, with Coleman and Treadwell as the consensus No. 1 and No. 2, respectively.

But where might those players land, and which NFL clubs have a need for their skills? Both analysts identified the best team fit for each prospect mentioned. Here are their fit picks:

"(I think) Chip Kelly would also like to have Corey Coleman with the San Francisco 49ers. They desperately need more speed on the perimeter. Corey Coleman can provide that, and the big-play ability."

"The Philadelphia Eagles, somebody to take that top off the defense, stretch things out. You've got your tight ends you can work in, you've got Jordan Matthews in the middle of the field."

Brooks: Los Angeles Rams

"I believe the L.A. Rams would be a nice fit for him. ... Tavon Austin can do some things in the slot. You have other playmakers like Kenny Britt who can stretch the field. Laquon Treadwell can be the anchor of that passing game. He can play the 'X' (receiver), you can build it around him and allow him to be the focal point of that passing game."

"Give Philip Rivers a true No. 1. He hasn't had that there in quite some time. They need some more weapons for him there to get that offense rolling again."

Brooks: Los Angeles Rams

"Tavon Austin is their No. 1. I don't necessarily like that, but down in the red zone, you need a taller guy, a guy that you can go to."

Jeremiah:Cleveland Browns

"Hue Jackson has mentioned the fact that they've got to get taller, they've got to get bigger. He came from Cincinnati where they had all those tall-tree wide receivers. Now he goes to Cleveland and they've got a bunch of little bushes. They need a tree. I think Michael Thomas would be a good fit there."

*Follow Chase Goodbread on Twitter **@ChaseGoodbread*.

This article has been reproduced in a new format and may be missing content or contain faulty links. Please use the Contact Us link in our site footer to report an issue.

Related Content