Google cache is for a 3rd parties site for HTTP version and correct for HTTPS

[dmcubed]

If I search Google for my cache I get the following:

• cache:http://www.saucydates.com -> Returns the cache of netball.org (HTTPS page with Plesk default page)
• cache:https://www.saucydates.com -> Displays the correct page

Prior to this my http cache was the Central Bank of Afghanistan. For most searches at present my index page is not returned and when it is, it’s the Net Ball Plesk page. This is, of course hurting my search traffic considerably.

** I have tried many things, here is the current list:**

1. If I fetch as Google in webmaster tools the HTTPS fetch and render is correct.
2. If I fetch the HTTP version I get a redirect (which is correct as I have a 301 HTTP to HTTPS redirect).
3. If I turn off HTTPS on my server and remove the redirect the fetch and render for HTTP version is correct.
4. The 301 redirect is controlled with the 301 Safe redirect option in Plesk 12.x
5. The SSL cert is valid and with COMODO
6. I have ensured the IP address (which is shared with a few other domains that form my sites network / functions) has a default site
7. I have placed a site on my PTR record and ensured the HTTPS version goes back to HTTP as it doesn’t need SSL
8. I have checked my site in Waybackwhen for 1 year and there are no hacked redirects
9. I have checked the Netball site in Waybackwhen for 1 year, mid last year there is an odd firewall alert page.
10. If you check the cache for the https version of the netball site you get another sites default plesk page.
11. This happened at the same time I implemented SSL

Points 6 and 7 have been done to stop the server showing a Plesk Default page as I think this could be the issue (duplicate content)

** Ideas:**

1. Is this a 302 redirect hi-jack?
2. Is this a Google bug?
3. Is this an issue with duplicate content as both servers can have a default Plesk page (like millions of others!)
4. A network of 3 sites mixed up that have plesk could be a clue?

Over to the experts at MOZ, can you help?

Thanks,

David

[dmcubed]

After 1 month of mixed caches it fixed itself.

[BlueprintMarketing]

PS was your hosting company? If there managed host I would suggest you have them look into the issue requesting force HTTPS

[BlueprintMarketing]

Please verify everything is in Google Webmaster tools for HTTPS

so there are four versions of your site in Webmaster tools pick the version you wish to index in your case will be www. or non-www. HTTPS then fetch as a Googlebot. look for errors.

• http://
• http://www
• https://
• https://www

https://varvy.com/tools/redirects/

screaming frog SEO spider free for The first 500 URLs it will show if there is a problem most likely be very helpful.

https://www.screamingfrog.co.uk/seo-spider/

or https://deepcrawl.com To figure out rather or not it's duplicated content and find possibly broken redirects or missing HSTS

this will confirm you do not have any and redirects.

After doing so if you do have bad redirects you will have to speak to your hosting company or at least share info with us about your server configuration sure that it is set to force HTTPS

See the guides below to make sure you don't have an error somewhere.

• https://www.keycdn.com/blog/http-to-https/
• https://moz.com/blog/seo-tips-https-ssl
• http://searchengineland.com/http-https-seos-guide-securing-website-246940
• https://support.google.com/webmasters/answer/6073543?hl=en

If you would like to force the redirect to HTTPS there are three third-party tools that will allow you to do this for any site

• https://www.incapsula.com/
• https://www.stackpath.com/
• https://www.cloudflare.com/

You still will want to use deep crawl or screaming frog to check your set up.

I hope this is of help, and the last URL is a free tool.

Tom