Josh Gordon wasn't supposed to start Week 1, but Browns screwed up

The Cleveland Browns may not have lost Week 1, but the team still has a few things to sort out. Remember when Hue Jackson was adamant that Josh Gordon would not start the contest against the Pittsburgh Steelers? Well, Gordon was on the field for the Browns’ first play from scrimmage.

Was it all a smokescreen from Jackson in an attempt to fool the Steelers? Nope. It was a mistake. Jackson confirmed that Gordon was not supposed to start the game.

In the weeks leading up to the game, Jackson told reporters that Gordon would play, but that he would not start.

The 27-year-old Gordon missed a large portion of training camp as part of his “overall health and treatment plan.” Gordon missed both the 2015 and 2016 seasons due to a drug-related suspension.

Who is to blame for Josh Gordon starting for Browns?

The majority of the blame falls on Jackson, who repeatedly said Gordon would not start. And while Jackson’s “personnel grouping” line could cast some blame on offensive coordinator Todd Haley, that still doesn’t reflect well on Jackson.

Gordon made his only catch of the day count. In the fourth quarter, he hauled in a 17-yard touchdown to tie the game at 21. The contest ended in a 21-21 tie.

What happens to Josh Gordon and the Browns in Week 2?

Gordon was on a pitch count Week 1 after missing time during training camp and dealing with a hamstring injury. If Gordon can practice in full all week, it’s possible Jackson will let Gordon start on purpose in Week 2.

Josh Gordon got a start for the Browns, but that wasn’t supposed to happen. (AP Photo)
Josh Gordon got a start for the Browns, but that wasn’t supposed to happen. (AP Photo)

– – – – – – –

Chris Cwik is a writer for Yahoo Sports. Have a tip? Email him at or follow him on Twitter!

More from Yahoo Sports:
5 things to know about U.S. Open winner Naomi Osaka
How the NFL’s fittest QB stays healthy
10 takeaways from a stunning college football weekend
Serena defends referee confrontation