Tag Info

New answers tagged

0

It is highly likely that Google reduces the linkjuice passed from one site to another if it is on the same IP address because Google makes the logical and reasonable assumption that the link isn't an unbiased link. Google uses links as 'votes' for how important a site is - the more links it gets from other sites the higher it's 'authority'. The more links ...


0

If your customer is not doing anything shady or does not break any search engine recommendation, then using different IP addresses will not improve SEO. It is a waste of time and money. If your customer is doing something shady, using different IP address may delay a little the moment search engines found about it, but not by long, and once they penalize ...


0

That approach should work fine so long as your Apache config is setup so your application is listening on both ports 80 and 443 However, the original requests will show a warning about not have a valid SSL certificate. See the answer E Carter Young linked to in his comment if you need to avoid that.


3

There are a few smart ways, so in theory it is sometimes possible, but only with a bad admin configuration. In practice it's about impossible. For example, try getting the IP address of a site's DNS records like: cpanel.domain, webmail.domain, etc... Maybe they'll point to the real IP address if they're not proxied through CloudFlare. CloudFlare wasn't ...


5

Both answers are right to a point. I used to be a web host and a registered ISP. I was a presenter at the first ISPCon known as ISPOne for USRobotics and represented well over 1 billion dollars in sales in just the first quarter. I have been out of the industry for quite a while, but not too much has changed except for some of the offerings and some of the ...


3

At least indirectly the number can actually affect the performance of your website: On a shared host the actual performance risk is to have resource hungry neighbours like shops and forums etc. on the same (shared) server. The more neighbours, the more likely you'll have one (or more) neighbour using the shared server's CPU power and bandwidth. But it's just ...


4

You shouldn't worry as it doesn't mean anything. Shared IP addresses are common and the norm. Having a large number of sites sharing and IP address doesn't indicate much. If the host has a beefy server they can fit thousands of sites on it and not have a hiccup. Unless they use SSL there is no need for them to have different IP addresses. And there is ...


1

I believe this practice is known as a Link Wheel in SEO terms. The idea is to have a bunch of different sites (known as spokes) each generating content to point to your main "target" domain (where he sells stuff). Each spoke site will generally link to one of the other spoke sites, and also to the target site. Thus passing half the link juice to the other ...


0

I just answered a similar question here: Website opening both on domain name and IP. Is that a problem? You may need to redirect any IP address based requests to your domain name.


3

You may run into issues with duplicate content. You probably do not want to create canonical tags when they are not necessary. Too much work. You can try a redirect: RewriteCond %{REMOTE_ADDR} ^123\.321\.123\.32$ [NC] RewriteRule ^(.*)$ http://site.com/$1 [R=301,L] Of course you can adjust this to suit your needs. Insert this into your .htaccess file. ...


0

It doesn't make any problems. You can prevent it by adding another virtual host for the same IP in your apache or nginx web server. This will attract ip-based access without a hostname and your main site will only be accessible by host name.


0

You can put this script into you're .htaccess file on root directory of you're website: ## block IP access ## order allow,deny deny from 81.17.31.162 deny from 81.17.31.164 allow from all ## block IP access ## In this case make all IP Address unless 81.17.31.162 and 81.17.31.164 to access you're website


3

the rule to activate in mosecurity can be found in base_rules/modsecurity_crs_21_protocol_anomalies.conf That would block access to the website when accessed through server IP.


2

Here is an .htaccess option for you: RewriteEngine On RewriteCond %{HTTP_HOST} ^10\.0\.11\.101$ [NC] RewriteRule ^(.*)$ http://www.example.com/$1 [R,L] ...to redirect and... RewriteEngine On RewriteCond %{HTTP_HOST} ^10\.0\.11\.101$ [NC] RewriteRule .* - [F,L] ...to block. Obviously, you will need to change the IP address and domain name to suit your ...



Top 50 recent answers are included