Have you used Google's new search console https report?

[MichaelCorfman]

Today (14 September 2022) Google announced a new https report available in search console. You can read the announcement in the Google Search Central Blog here:

The new HTTPS report in Search Console

In part, the announcement states:

"Last year, we released the Page Experience report in Search Console to help site owners understand and fix issues affecting how Google evaluates the page experience for their site. One of the common requests we heard from you was to provide more information regarding the HTTPS status of the site and make it easier to understand which pages are not served over HTTPS, and why not.

"To address this request, we’re gradually rolling out the HTTPS report in Search Console over the next few months. Use this report to get insights about your HTTPS pages served on Search. The report also lists the issues that prevent pages from being served as HTTPS, along with sample URLs."

My initial reaction was to think this report might not be that useful, since all the sites I operate have been converted to use https some time ago. However, I did form a slightly different opinion after looking at the report for a few sites.

For the GPWA.org website, the report identified 4 urls for which https was not evaluated. And, for each of those urls Google reported a last crawled dated of N/A. And Google, as is standard practice for errors reported by search console, allows one to say the issue is fixed and request that the fix be verified. So, I've done that for the GPWA.org website, and also for a number of other websites of mine. I figure it can't hurt to ask Google to crawl pages on a site when it thinks the pages might be http and not https pages.

So, for this week's poll, I ask if you have seen the new report, and if you have used it, or expect you will use it, to let Google know all of your pages are served using https.

Michael

[universal4]

I predict we will soon quickly see a handful of "new websites" and "tools" to help webmaster "find" and "fix" the errors. And each one of these will be written or operated by "ex-google" engineers etc, just like the cls fixer sites, core web vital fixer sites, etc etc etc.

I have already seen pages reports as not being delivered by https and yet they are, because google's job is to mark stuff as bad before they actually check isn't it?

Rick
Universal4

[LetsGamble]

Didn’t even know it was added. We’re all good. But I could see this being usual for anyone who set up HTTPS without a proper redirect in place for HTTP pages.

[MJM]

This tool should have been released a couple years ago, Google is playing catchup here IMO.

[Grand_RexAffiliates]

Quite frankly if someone is doing content online then it is actually a good idea to know the user experience and also how does the page load and is viewed by the user on a smartphone as well. However, the age old strategy when people in sales and marketing used to say KEEP IT SIMPLE in my opinion still works best and is practical as well HTTPS certainly is something a lot of people actually look for as well.
The safety and the security is also a concern which people have to keep in mind always and all the time
I personally do prefer HTTPS myself and use it a lot