Welcome to the Q&A Forum

See what Google thinks with the site:yourdomain.com search. This will give you all the data they have on your site. Look for errors, missing content and duplicate content. I think that would be a good start. Also use Google Search Console to check for index issues, crawl issues and any manual actions. If a site is offline for a while it will be delisted, a big site is delisted after a few minutes, in my experience the traffic returns after 1 or 2 weeks. To make it more complex there seems to have been a few changes to Google results over the past weeks, may be due to the 'mobile first' index.

If you compare your scores with others sites when tracking a keyword and you or someone else has implemented AMP the score is a 1. It would be better to get the PA from the canonical reference. See screen shot for an example.

Does anyone else agree? Can this be developed?

cJp9J

I have been a MOZ subscriber for a few years now. I don't think MOZ works for .dating and .chat domain extensions. I have 2 sites that have authority 1 despite back links. Here are the details:

https://oooo.dating > DA = 1

https://talk.chat > DA = 1

oooo has 221 links (Google search console)

talk has 1317 links (Google search console)

May be a MOZ staff member can look into this. If you are customer and use some of the newer domain extensions please share your details if you have the same problem.

After 1 month of mixed caches it fixed itself.

I posted the first reply about how similar my problem was to yours. Mine resolved over a month ago. I'm very sure this is a duplicate content issue. It doesn't matter if they are different servers, markets etc. When you "look" at the sites they "look" the same. Google was taking a default PLESK server page for my domain and showing other sites (3 in total) that also had the same default page. Different servers, different owners and different industries.

I think if you continue to ignore this advice you will have this issue forever. You either need to make the sites different (or at least the home pages) or combine them into a single site and map your existing link juice from one to the other with redirects. You then need to serve the different data based on geolocation.

Depending on your web site, servers, support team etc this could be a very difficult job.

Hello,

I just noticed your question, it's very similar to mine:

https://moz.com/community/q/google-cache-is-for-a-3rd-parties-site-for-http-version-and-correct-for-https

My best guess at the moment it's duplicate content. I think Google has updated how it sees duplicate material and then it's picking one of them as the main source. Your two sites are "Similar". Take a look at my question as it has the steps I have looked at so far. In my situation its picking a site that I don't own and very different IP addresses. I'm at the stage now where I'm trying to track down a real life Google engineer to get the question directly in front of them.

David

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