To configure Chrome to show the warning as it will appear in January 2017, open If your site overlays an HTTPS login frame over HTTP pages...
..will need to change the site to either use HTTPS for the entire site (ideal) or redirect the browser window to an HTTPS page containing the login form: Eventually, Chrome will show a Not Secure warning for pages served over HTTP, regardless of whether or not the page contains sensitive input fields.
Search engines can score regularly updated content for freshness differently from "Also, a document having a relatively large amount of its content updated over time might be scored differently than a document having a relatively small amount of its content updated over time." In fact, Google may choose to ignore small changes completely.
That’s one reason why when I update a link on a page, I typically also.
This way, Google may be less likely to ignore the change.