Liverpool have been dealt another injury blow with the news that centre-back Joel Matip is expected to be sidelined for longer than previously expected.

The Lowdown: Matip absent for Liverpool

The 31-year-old was a regular presence for the Reds last season, starting 31 Premier League matches and avoiding the injury problems which have so often plagued him.

Unfortunately, Matip has been absent since featuring in the 2-2 draw away to Fulham on the opening weekend of the campaign, with a groin issue keeping him out of last week's clash against Crystal Palace.

The hope was that the Cameroonian could return for tonight's trip to Manchester United, but a negative update has emerged prior to the Old Trafford encounter.

The Latest: Injury worse than first feared

Speaking to reporters [via This Is Anfield], Jurgen Klopp has confirmed that Matip's absence is expected to be prolonged, due to what the Liverpool manager has described as a 'strange' injury which could rule the defender out for up to four weeks, having initially been expected to miss just two.

The German outlined:

"Joel now, that was strange as well. How it happened, didn’t feel anything in training, walked in then said ‘yeah, there is something’ and then out for, I don’t know, three weeks, four weeks, whatever."

[freshpress-quiz id=“398089"]

The Verdict: Another big blow

Injuries have really hurt Liverpool already this season, with the likes of Diogo Jota, Ibrahima Konate and Thiago currently missing, among others, and this update is another blow for the Reds.

It means that Joe Gomez will probably start against United after Nat Phillips struggled at home to Palace last Monday, but Klopp's centre-back options are certainly limited.

[freshpress-poll id=“399042"]

History suggests that Matip can often be out for longer than initially feared, and if he doesn't return sooner rather than later, it could have a detrimental impact on Liverpool's Premier League title chances, especially considering that he was the Reds' fourth-best performer last term according to WhoScored.