Skip to main content
Formatting
Source Link
Zistoloen
  • 10k
  • 6
  • 36
  • 59

If your site can be accessed both by domain urlURL and ipIP address then you will have such issues. That That IP corresponds to sulekha.comsulekha.com - obvously antoher one of your domains for the same business.

You have to 301 redirect accesses from the wrong ipIP-based urlURL to the correct domain-based urlURL, at the server level. Since Since you are hosted on an IIS server this is something you may need to take up with your hoster if you don't know where to do it. It It may be done through the IIS console or through scripting.

Using fully qualified urlsURLs in navigation would help diminish the incidence of finding more ipIP-based urlsURLs during navigation.

If your site can be accessed both by domain url and ip address then you will have such issues. That IP corresponds to sulekha.com - obvously antoher one of your domains for the same business.

You have to 301 redirect accesses from the wrong ip-based url to the correct domain-based url, at the server level. Since you are hosted on an IIS server this is something you may need to take up with your hoster if you don't know where to do it. It may be done through the IIS console or through scripting.

Using fully qualified urls in navigation would help diminish the incidence of finding more ip-based urls during navigation.

If your site can be accessed both by domain URL and IP address then you will have such issues. That IP corresponds to sulekha.com - obvously antoher one of your domains for the same business.

You have to 301 redirect accesses from the wrong IP-based URL to the correct domain-based URL, at the server level. Since you are hosted on an IIS server this is something you may need to take up with your hoster if you don't know where to do it. It may be done through the IIS console or through scripting.

Using fully qualified URLs in navigation would help diminish the incidence of finding more IP-based URLs during navigation.

Source Link
Anz Joy
  • 220
  • 1
  • 4

If your site can be accessed both by domain url and ip address then you will have such issues. That IP corresponds to sulekha.com - obvously antoher one of your domains for the same business.

You have to 301 redirect accesses from the wrong ip-based url to the correct domain-based url, at the server level. Since you are hosted on an IIS server this is something you may need to take up with your hoster if you don't know where to do it. It may be done through the IIS console or through scripting.

Using fully qualified urls in navigation would help diminish the incidence of finding more ip-based urls during navigation.