This website uses cookies

Read our Privacy policy and Terms of use for more information.

We start our title defence without William Saliba, and the club has told us as much. Arsenal confirmed on July 22 that the back injury he carried through the World Cup has finally forced a stop, that he will not need surgery, and that he faces an extended spell of rehabilitation with no fixed return date. The reaction among most supporters has been to reach for the depth chart and reassure ourselves that the squad is big enough to cope. It is a bigger squad than the ones that failed us before, and that is genuine. But the specific hole Saliba leaves is not one our current numbers fill cleanly, and the sensible response is to spend before the window shuts rather than talk ourselves into believing we do not need to.

The diagnosis: we ran him into the ground, and this is the bill

It is worth being honest about how we got here, because it explains why the injury is serious rather than routine. Saliba was close to ever-present through a title-winning league campaign, then played every round of a Champions League run to the final in Budapest, then went straight into a World Cup with France and started four games to the semi-final on a back that, by the reporting around the French camp, was already troubling him before the tournament began. That is close to fourteen months of football with no meaningful rest, and it ended with his back giving out in the thirtieth minute against Spain.

The club statement is careful and the medical steer is actually reassuring: no surgery, a managed recovery, continual management of the problem over the months ahead. A controlled rehabilitation is the right call over a knife that might have cost him a year. But the same statement tells us this is a structural issue that has to be handled patiently, which is another way of saying he is not walking back into the side in September. The diagnosis is simple. We overused our most important defender, and now we begin the season without him. This is the same lesson the run of international breaks kept teaching us last season, when Timber's groin injury cost him the World Cup and player after player came back in pieces.

Why the hole is real: we have seen exactly this before

Saliba is not a good player we will miss around the edges. He is the defender the whole structure is built on. Ours was the meanest defence in the division last season, and the Saliba and Gabriel partnership is why. Saliba covers the space in behind, steps out to kill a counter before it becomes a chance, and lets us defend with a high line because his recovery pace makes that line safe. Remove him and it is not one player you replace, it is the balance of the entire back four.

We know precisely what that looks like, because we have lived it. In March 2023 Saliba limped off against Sporting with a back problem and did not play again that season. We were five points clear at the top when he went down. We did not win the title. Rob Holding deputised, the high line stopped holding, we conceded nine goals across three league games at the worst possible moment, and City strolled past us. The point is not that the 2023 squad lacked a name to throw in. It is that the name we threw in could not do the job. That is the difference a real replacement makes, and it is the whole argument for getting this right now.

The fix: what we actually need, and what we should refuse to do

So what solves this going into the new season? Start with what we have. Cristhian Mosquera is the obvious answer, the young right-sided centre-back we signed from Valencia last summer precisely to sit behind Saliba and Gabriel. If he is ready to start a title defence, this problem shrinks. But he is one man, and behind him the picture thins fast. Piero Hincapie, now signed permanently, is excellent but did his best work for us at left-back and as left-sided cover for Gabriel, not as a right-sided partner. Ben White can step inside, though he is only just back from the knee injury that ended his last season in May. Jurrien Timber can play centrally but is most valuable at right-back and is himself returning from injury. Jakub Kiwior, who might have helped, spent last season on loan at Porto. That is one genuine replacement and a collection of fill-ins. It is too thin for a squad expected to compete on four fronts with its best defender out for months.

Which is why the reporting linking us to a new defender is not noise, and why it should be acted on. The name doing the rounds is John Stones, a free agent since his City deal expired, who Arteta knows well and who impressed at the World Cup. On paper it is tidy: no fee, Premier League and high-line experience, a profile Arteta trusts. My view is that it is the wrong signing, and the supporters raising the objection are right. Stones is 32 and has spent large stretches of recent seasons injured. Signing a player with that record specifically to cover for an injury is a strange gamble, and a free transfer is only cheap if the player is actually available when you need him. Ezri Konsa has been floated as an alternative, but at a fee said to be north of £60 million he is a lot of money for temporary cover.

Here is the fix I would back. Sign a fourth centre-back, but make it a durable, younger option we can rely on across a long season, and pay a sensible fee to get one rather than reaching for the no-cost name because it flatters the accounts. This is exactly the kind of decisive recruitment we called for when Berta's rebuild was taking shape earlier this summer, and it matters more now than it did then, because the margin for getting it wrong just narrowed. Mosquera can be trusted to start. What we need behind him is insurance that does not spend its own life on the treatment table.

The good news is real: no surgery, and Saliba will be back. But we open the season without the best defender at the club, carrying an injury we helped cause, with cover that is one signing short of comfortable. Berta has until the window closes to fix the last part. That is the job. He should do it.

Reply

Avatar

or to participate

Keep Reading