Welcome to WebmasterWorld Guest from 18.104.22.168
I changed my entire site over to HTTPS from HTTP. I have my HTTP site setup in G webmaster Tools. I have just fed that a new sitemap with all my https urls and it seems to be taking them.
Should I "add a new site" to my webmaster tool profiles specifying https?
Currently it is: http://www.example.com/sitemap
Is it worth deleting this site from my webmaster tools profile and adding a new site with the proper HTTPS ?
[edited by: Robert_Charlton at 10:58 pm (utc) on Feb. 2, 2009]
[edit reason] changed to example.com - it can never be owned [/edit]
I switched my site to HTTPS because I was having issues with my cart dropping items so why not give my customers security the whole time?
Once I add this new site to G webmaster tools, should I delete the old site(non https version) from my profile?
Do I need to create this new profile for my HTTPS website or can I keep my existing profile for HTTP?
Add to the httpd.ini
RewriteRule ^/robots.txt$ /robots.aspx [NC,O]
make 2 robots files one robots.txt and one robots.aspx add the code below after you have changed the httd to dissalow all and the https to allow all or disallow what you dont wwant spidered.
<%If Request.ServerVariables("HTTPS") = "off" Then 'if not secure%>User-agent: *
be sure and test it as well
http://www.example.com robots.txt should show disallow all
[example.com...] should show to allow all or your folders you dont want spidered.
I had a customer wants call and ask me why my whole site wasnt not secure because when he goes to his banking site everything is secure. Makes sense for a bank.
I already have robots.txt points to my https sitemap, it seems google is also indexing my https. I have a 301 redirect in place for all old http urls
Is there a specific command I can place in my robots.txt to make it where http wont get indexed and https will.
In my experience, robots.txt is useless in fixing sitewide http/https canonical issues. The only fix I've seen work is mod_rewrite.
Do you guys think I need to add a new profile in webmaster tools for HTTPS or can I just continue to use my HTTP profile I have been using?