What Leeds United did with Burnley Left back during the summer window

Transfer journalist Ben Jacobs has told Give Me Sport that Leeds United moved “aggressively” for both Burnley left-back Charlie Taylor and Sheffield United signing Luke Thomas during the summer window.

Leeds have ended the window with nine new signings and a completely new look to the squad – Daniel Farke and the transfer team working wonders, given the obstacles they have had to face this summer.

But, two areas remain lacking in a top-quality player that is naturally suited to that role. The first is the 10 role – with Leeds making moves for both Nadiem Amiri and Matt O’Riley in the final couple of weeks.

The other is left-back. Taylor, 29, and Leicester City’s Thomas were both on our radar. Jacobs says that Leeds made moves for both in an “aggressive” manner – but neither Burnley or Leicester were keen.

Sheffield United v Everton FC - Premier League

“Luke Thomas at Leicester – multiple approaches were made but Leicester had no desire to loan to a Championship rival, so he ended up going to Sheffield United. Charlie Taylor at Burnley,” Jacobs said.

“He could have returned to Leeds, but there was no appetite on the Burnley part either. So Leeds tried, they were quite aggressive particularly for Thomas. But, they just couldn’t get that deal over the line.”

Jacobs says Leeds moved aggressively for Taylor and Thomas

Both players would have been amazing additions. Taylor – well, Leeds have not really replaced him since he left in 2017 for £5m. He knows the club and despite some ill-feeling, he would have been brilliant.

Thomas is a talent. A left-back that has shown he can shine in the Premier League. But Leicester are well within their rights not to loan him to us – and Taylor, like many others, chose the lure of the top tier.

If we were in Leicester’s shoes, would we want to loan a player to a direct rival? Would Thomas want to have come to Leeds – given it would be fighting his boyhood side to go up, before a possible return?

Be the first to comment

Leave a Reply

Your email address will not be published.


*