3 possible replacements if 49ers lose Richard Sherman to injury

Cornerback Richard Sherman #25 of the San Francisco 49ers. (Photo by Kevin C. Cox/Getty Images)
Cornerback Richard Sherman #25 of the San Francisco 49ers. (Photo by Kevin C. Cox/Getty Images) /
facebooktwitterreddit
Prev
3 of 4
Next
Jalen Ramsey, Los Angeles Rams
Cornerback Jalen Ramsey #20 of the Los Angeles Rams. (Photo by Lachlan Cunningham/Getty Images) /

No. 2: He may be an expensive rental, but if the 49ers are top of the NFC and Jalen Ramsey’s team isn’t there’s a chance a trade could happen

Los Angeles Rams cornerback Jalen Ramsey could be an interesting acquisition for Lynch and the 49ers front office. With the signing of Sherman a few years ago, the team showed they aren’t afraid to sign big-controversial personalities.

Would they be afraid to trade for one?

Trades within the division are relatively rare. No team wants to give the upper hand to their opponent. But what if one team is on the bottom of the NFC West and the other is making their second push for a deep playoff run?

Ramsey is a solid corner and would make a great replacement for an injured Sherman if the possibility arises. In his short four-year career he has 10 interceptions with 213 solo tackles.

The Rams would be hard-pressed to re-sign Ramsey when the season comes to an end. He’ll be expecting a lot of cash, and with the cap situation, the Rams might want to get something out of nothing.

Ramsey would be a rental player, but if the 49ers feel their window to win it all is right now, Lynch could pull the trigger on another blockbuster deal. And we all found out this offseason, the former Super Bowl champion with Tampa Bay isn’t afraid to trade who he wants.

To add unnecessary fuel to the fire, 49ers tight end George Kittle along with Sherman followed Ramsey on Twitter.

Now, in the grand scheme of things, this means absolutely nothing. Players follow each other on social media all the time. But with a personality like Ramsey has, we could be looking back at the small details like this somewhere down the line.