Mobile app version of vmapp.org
Login or Join
Harper822

: Toxic links between sites inside my server Recently one of my web sites shows in Google results but the url connected with the Google result is from another website in my server. so i have

@Harper822

Posted in: #Google #Links

Recently one of my web sites shows in Google results but the url connected with the Google result is from another website in my server. so i have url-A and url-B

So when i hit url-A in google , I would expect my Google result to be url-A/some-page-from-site-A and instead i get:

url-B/some-page-from-site-A

This is happening for url-A with 3 more web sites
url-C/some-page-from-site-A
url-D/some-page-from-site-A
url-E/some-page-from-site-A

When i hit the link i get a

"Your connection is not private Attackers might be trying to steal your information from url-B (for example, passwords, messages or credit cards). NET::ERR_CERT_COMMON_NAME_INVALID"

I submitted the links to Google and waiting for removal but i'd like to know what has happened and how can i avoid such incidents.

All web sites are mine and under the same server

10.01% popularity Vote Up Vote Down


Login to follow query

More posts by @Harper822

1 Comments

Sorted by latest first Latest Oldest Best

 

@Miguel251

There's a few things that can cause indexing issues with Google that could be in play here:


If you're running more than one site with SSL/TLS enabled on a single IP Googlebot can get confused when attempting to connect on port 443. It may be your server is returning just the HTTPS enabled site, despite hostname requests for others coming in via SNI in the handshake. To test this, try connecting on port 443 for the other domains and see what happens. Check host config and make sure it's issuing certs for other domains based on the request (so visit another-domain.com/ and check it's not just the same cert for yours).
There are occasionally index issues with same IP pages if you're using relative links. Use absolute links on your page, so Google isn't picking up href '/some-page' instead it sees 'http://your-domain.com/some-page'. Check your HTML and host configuration to make sure requests on 443 aren't being resolved to the wrong page. To fix this, it appears when your pages have enough backlinks Google seems to correct itself then. I assume because it can later verify links using external sources.

10% popularity Vote Up Vote Down


Back to top | Use Dark Theme