: Mix up of two domains in search result I would like to know why my two domains are mixed up in the search result. The two domains are https://vym.io and https://remotebase.io. When I search

@Caterina187

Posted in: #GoogleAnalytics #GoogleSearch #GoogleSearchConsole

I would like to know why my two domains are mixed up in the search result. The two domains are vym.io and remotebase.io.
When I search 'remotebase', I see the title, and description of remotebase.io in the result, but it links to vym.io.

This is very strange because nowhere in the codebase of vym.io can I find any mention about remotebase. I also did a global search for 'vym' in remotebase.io's code and could not find anything.

In the Google Wwebmasters Tool's Search Analytics page for vym.io, I see all kinds of keywords related to remotebase.io but has nothing to do with vym.io. Also, in Google Analytics for RemoteBase, I can see links to vym.io showing up in the referrals.

Thing I have tried:


Three days ago, I removed DNS settings for vym.io so that it does not resolve. This did not work and I restored the DNS.
I compared <meta name="google-site-verification" ...> tag for both websites, and they are using different keys.


Additional info:


The websites are associated with different properties on google analytics.


I am out of ideas and this is very frustrating. Please help.

Edit

When I google site:vym.io, I get all the pages that belong to remotebase.io.



But when I click on them I go to vym.io and there is nothing on the page because the routes belong to remotebase.io.

Edit 2

These are nginx configs for each websites, hosted on separate servers.

remotebase.conf

map $http_upgrade $connection_upgrade {
default upgrade;
'' close;
}

server {
listen 80;

server_name remotebase.io;
return 301 remotebase.io$request_uri; access_log /var/log/nginx/remotebase-access.log;
error_log /var/log/nginx/remoteabse-error.log;

location / {
proxy_pass 127.0.0.1:3000; proxy_set_header X-Forwarded-For $remote_addr;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection $connection_upgrade;
}

server_name remotebase.io; return 301 $scheme://remotebase.io$request_uri;
}


vym.conf

map $http_upgrade $connection_upgrade {
default upgrade;
'' close;
}

server {
listen 80;

server_name vym.io;
access_log /var/log/nginx/vym.access.log;
error_log /var/log/nginx/vym.error.log;

location / {
proxy_pass 127.0.0.1:5001; proxy_set_header X-Forwarded-For $remote_addr;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection $connection_upgrade;
}

server_name vym.io; return 301 $scheme://vym.io$request_uri;
}

Vote Up Vote Down

Login to post a comment!