Mobile app version of vmapp.org
Login or Join
Correia994

: Wrong domain in google results Google search results show wrong domain (that is on the same web server), i.e. site:rose.spb.ru shows pages from site:xn--h1adaodgdoce7g.xn--p1ai which result in 404

@Correia994

Posted in: #CrawlErrors #Domains #Google

Google search results show wrong domain (that is on the same web server), i.e.
site:rose.spb.ru shows pages from site:xn--h1adaodgdoce7g.xn--p1ai which result in 404 when clicked.
Any help is appreciated
Edit
Sorry if it is not clear. Google search results show pages from domain xn--h1adaodgdoce7g.xn--p1ai as if they are under domain rose.spb.ru. Both domains are on the same server and are accessible through https only.
Here is an example, if you type site:rose.spb.ru in Google (google.ru, google.co.uk) you get a bunch of pages that are actually on xn--h1adaodgdoce7g.xn--p1ai (if you send appropriate Host header) and so when one clicks on them sending wrong Host header one gets 404 Not found and people do click on them.



Edit
I now set up a redirection to the correct domain for most of the urls, so you won't see a 404 for them.
It seems that Google used to send the IP address as the value of the Host header when indexing and was redirected to the default domain. Does anyone know about Google using IP address as Host and why would this happen ?
Also if you click on 'Cached' in the results, for some of them you get one domain for the others you get a different one.
Edit
Both virtual hosts had ServerName set accordingly so I don't think it was possible to access them with wrong Host header:

<VirtualHost *:443>
ServerName rose.spb.ru
ServerAlias rose.spb.ru DocumentRoot /rose.spb.ru
...
</VirtualHost>
<VirtualHost *:443>
ServerName xn--h1adaodgdoce7g.xn--p1ai
ServerAlias xn--h1adaodgdoce7g.xn--p1ai DocumentRoot /xn--h1adaodgdoce7g.xn--p1ai
...
</VirtualHost>
<VirtualHost *:80>
ServerName rose.spb.ru
ServerAlias rose.spb.ru DocumentRoot /rose.spb.ru
...
</VirtualHost>
<VirtualHost *:80>
ServerName xn--h1adaodgdoce7g.xn--p1ai
ServerAlias xn--h1adaodgdoce7g.xn--p1ai DocumentRoot /xn--h1adaodgdoce7g.xn--p1ai
...
</VirtualHost>


Edit
I think it has to do with the previous owner of the IP address. If you type site:188.120.225.32 (which is the IP address of xn--h1adaodgdoce7g.xn--p1ai) in google.co.uk you get a bunch of indexed pages that were on the this IP address before:


I think for some reason Google tried to index the new website on that IP using IP address as the Host header, it was redirected 301 to a default domain rose.spb.ru where it should have gotten 404 Not found just like the users who clicked on the links, but somehow it did include these pages in the index.

10% popularity Vote Up Vote Down


Login to follow query

More posts by @Correia994

0 Comments

Sorted by latest first Latest Oldest Best

Back to top | Use Dark Theme