Google posted on Twitter on the Google Webmaster account that Chrome is making changes to how it handles mixed content and you should be on top of it for your users. Also mixed content can break your HTTPS security, but as we know, the HTTPS ranking boost is not dependent on HTTPS being valid right now and neither is rendering said Google.
Google wrote "The Chrome mixed content change, does it affect your site's Googlebot rendering? Probably not!" Then Google went on to share a bunch of things you should be concerned about and tips to address it for your web site. The indexing and ranking bit we knew for some time anyway.
Here are those tweets:
If you moved to HTTPS and Chrome doesn't show a gray lock icon, there's mixed content. Mixed content is when a HTTPS page includes HTTP content, like an image or a video loading from HTTP. Upcoming changes may break the page for users & Googlebot.
— Google Webmasters (@googlewmc) November 15, 2019
(https://t.co/U7TDl28lSF)
If you host images or videos that other sites use, make sure to host them on HTTPS, ideally 301 redirecting from HTTP to HTTPS. This enables Chrome to auto-upgrade them when they're embedded, and keeps your great content visible everywhere, including on HTTPS pages.
— Google Webmasters (@googlewmc) November 15, 2019
Large old sites probably have the most work here but it is probably something everyone should have a plan on addressing by now.
Forum discussion at Twitter.
