Analysing the Importance of Improving Edin Dzeko to Manchester City

When Manuel Pellegrini walked through the door at Manchester City’s training ground complex 15 months ago, Edin Dzeko was a forlorn figure. He had just finished another season at City where he had been in and out the starting line-up, struggling for form, fitness and, perhaps more importantly, happiness. It seemed likely he could leave.

Fast-forward a year and things have u-turned dramatically. Dzeko’s form has improved significantly and for the first time since his arrival at City in 2011, he probably has the right to feel he’s a first-choice striker. Maintaining that status won’t be easy given the forward options available to Pellegrini, but there’s little doubt he’s more established at City now than he’s ever been.

He cuts a much more positive figure these days. The player who would often look sulky and disinterested now fights for every ball, both in the air and on the ground. The impudent backheel to assist David Silva for the opening goal at Newcastle was indicative of the improving Dzeko.

He looks fitter and sharper, capable now of a turn of pace that can trouble defenders. He’s no Theo Walcott, but Dzeko is definitely a yard quicker these days.

And then there’s his injury record which, in comparison to his rivals in the City squad, leaves him in pole position to start. With Alvaro Negredo gone, his main rivals for a starting berth are Sergio Aguero and Stevan Jovetic, both of whom have a less-than-reliable recent injury record.

Hannah Foslien/Getty Images

Aguero spent much of the second half of last season struggling for fitness. In fact, after hitting 26 goals in his first 25 games, an injury in City’s win away at Tottenham at the end of January saw his form falter, and he managed just two more goals before the end of the campaign.

His World Cup saw the pattern extended. He looked distinctly unfit and unable to impact games with any significance. It represented a worrying new trend for a player so vital to City’s ambitions of silverware this season. However, his three appearances so far this season, which have included two very brief cameos, have brought two goals and a return to his old sharpness, and Pellegrini will be desperately hoping his injury problems are now a thing of the past.

Jovetic, though, remains more of a concern. He has appeared somewhat brittle since he moved to City last summer and missed the majority of the last campaign with a mix of hamstring and calf injuries. A solid pre-season and involvement in City’s first three matches of this season looked to represent something of a turning point, but this week’s news that he returned from international duty with Montenegro early because of a hamstring injury has seen doubts over his ability to be involved consistently resurface (via Jamie Jackson at The Guardian).

It’s a situation which means Dzeko’s importance is heightened. City desperately need the same player who finished last season so strongly, scoring vital goals and contributing to City’s play far more than he had done before. It’s been a fairly dramatic turnaround, one which has seen Dzeko move from the periphery to a central role. He will be acutely aware, though, that only by maintaining his current level will he keep his place.

Negredo’s exit was rubber-stamped by Pellegrini because of the flexibility of his other attacking players. Yaya Toure and David Silva’s ability to play in a central role just off a main striker means the Chilean felt his options were plentiful enough to allow Negredo a move back to La Liga. Any dip in Dzeko’s form will see a reshuffle that jeopardises his place.

Mike Stobe/Getty Images

It's clear, though, that while he remains dominant in the air, strong with his back to goal, unselfish, motivated and with a touch of quality—combined with his ability to stay fit—his position in City's first team seems safe.

Rob Pollard is Bleacher Report's lead Manchester City correspondent and will be following the club from a Manchester base throughout the 2014-15 season. Follow him on Twitter here: @RobPollard_