Fix HTTPS is invalid and might prevent it from being indexed

"HTTPS is invalid and might prevent it from being indexed"

"HTTPS is invalid and might prevent it from being indexed." This error has occurred on Google webmaster tool from the last few days.

So, in this article, I will tell you what is exactly and why it is occurring.

From time to time, Google releases new updates to secure its algorithm. If Google Search Engine does not improve its crawler, compititor will beat it.

And also, Google search always tries to provide the accurate information to the end users. That is why they always tries improve their search crawler.

Recently Google released a new update. After this update "HTTPS is invalid and might prevent it from being indexed" error has occurred on the search console.

Now it has became a hot topic everywhere. Everyone is asking about it. 

But many people have no idea that it is an universal problem. They thinks it is showing only on their site.

But this error has occurred on all websites and blogs. It could be a Blogspot blogger blog or WordPress website.

"HTTPS is invalid and might prevent it from being indexed." Why should you not worry about it?

When webmaster tool expert raised their concern about it, Jhon Muller from the Google developer team stated that-

HTTPS would not prevent a page from being indexed. It might prevent it from being indexed as HTTPS, but we'd still index it as HTTP. We just don't index all pages on sites, that's expected, and independent of HTTPS status.

He clearly mentioned that it won't affect your website ranking factor because they will index as HTTP. You will get the more appropriate answer when we decode their tweets one to one. Just maintain your patience and continue reading.

When another user asked again,

Anyone else getting a bunch of false positive “HTTPS is invalid and might prevent it from being indexed?

A webmaster tool expert Andrej replied- 

I have noticed it too. Its on new links, in the stage when it is "crawled, not yet indexed". Once its indexed, it properly shows that https is valid.

I noticed it twice so far, both times when the link was crawled but not yet indexed. A false positive.

To support Andrej, Jhon Mullar replied-

Thanks! We dug through a bunch of these reports, and we'll work on improving the UI to make this look less scary. When a page is not indexed, we don't evaluate the HTTPS (it's not blocking). For very new pages, it's similar. We'll make this more of a "FYI" and not an error.

On the same tweet thread, WP-Tweaks tweeted- 

Yup. It looks like a bug and it should fix itself eventually. Your page still gets indexed and will appear in the SERPs.

To appreciate his tweet, John Mullar replied, 

Yes. This can show up for unindexed or freshly indexed pages. We'll work on improving the UI to make it less scary. It's not blocking indexing here, HTTPS is just not properly evaluated there yet.


From all the above conversations, we have a cleard overview that it is not a major bug. It will solve eventually. And it might not occur on every single page. So you don't need to worry about it.

Next Post Previous Post
No Comment
Add Comment
comment url