How to change http to https in Google Search console?

[born2run]

Hi so I've a site property in Google Search Console (GWT) as http://www.example.com.

Now I've installed https (TLS) on my site. How do I change the site property to https url (https://www.example.com)?

The reason for this change is that the "Fetch as Google" section shows http not https in the url.

Please advise. Thanks!

[not2easy]

First fix the cause of seeing the http response, then add a new property. If your rewrite was done correctly it should be returning https for any http requests. Until you make sure that is happening, it is a mistake to tell Google about the new URLs.

Do not delete the old http version from GSC when you add the new one because it will allow you to see the crawls and help you find and correct any errors.

[lucy24]

the "Fetch as Google" section shows http not https in the url

Do you mean, for new fetches that they can only have received as HTTPS, since you've got a global redirect in place? If so, it’s their glitch and can safely be ignored.

Edit: I went back and checked, in case I'd remembered wrong about how it works. I don't find a list with http or https at all; you have to select a specific property (typically one of four for any https site) before you can do the fetch. And then the status shows up as “redirected” if I started out with http.

[born2run]

Yes lucy24 the status does show "redirected" that's the problem! Should I submit this to the index? Or delete this http property and add https://www.example.com ?

[keyplyr]

Read again what not2easy said.

[born2run]

Yes I read carefully keyplyr but the old property was with http and now the "fetch as google" already has http://www.example.com/FILL IN THE BLANK box in the fetch page. So I type some url and it says it's been redirected.

The header response for that url says: "HTTP/1.1 301 Moved Permanently"

The redirect is working fine and I checked with many other tools and browsers.

[edited by: born2run at 8:31 pm (utc) on Apr 19, 2018]

[lucy24]

Look again at the “fetch as googlebot” dialog. You’ll notice that the protocol and host are hard-coded and cannot be edited by you. So depending on which property you’re currently viewing, it will be one of four:
http://example.com/ {part-you-fill-in-here}
http://www.example.com/
https://example.com/
https://www.example.com/
Three of the four should lead to a “Redirected” response, since that is what your server sends out if you’ve coded it properly. What would be the point of submitting something to the index when it receives a 301 Moved Permanently response? Only submit the version that does not receive a redirect.

[born2run]

So lucy24 I can't submit https url as http is hardcoded you are absolutely correct. That means that I'd have to add a https property of the same url www.example.com ?

[keyplyr]

Ignore all that.

Create the new property as not2easy said and use that from now on. It may take a few days for all the fields to populate. The https property is the only one you'll use going forward.

[born2run]

Great thanks, I also came across this site which says the same thing:

[searchengineland.com...]

Also, can I delete the http property once all the fields are populated? Or let it remain?

[born2run]

Yep google itself says in their search console page that all four (http, https, www and non-www) have to be added. Thanks guys! :-)

[born2run]

Quick question do i have to submit for indexing both desktop and mobile?

[keyplyr]

Leave the old http property (as not2easy already said.) Do not delete it.

You do not need to submit anything to indexing. Googlebot will get directed to the new pages. Just let things happen the way they are set up to happen.

All this has been discussed before. Instead of asking the same questions, please use the Site Search (upper-right corner)

[lucy24]

delete the http property once all the fields are populated?

NO.

Keep it, in the same way and for the same reason that you keep both with and without www even though you only use one.

[born2run]

Thanks so much guys! :-)