53

@toomanyairmiles is partially correct - the purpose of this technique is to allow parallel connections from the web-browser to the server. Web browsers should allow a minimum of two simultaneous connections to a single host, but many new browsers can manage up to 60. Regardless, concurrent simultaneous connections between browser and web-server(s) is a major ...


13

In the past, Web browsers were only able to download two items at once (now 6 or more), so downloading resources from various domains is faster than a single domain. This applies to everything from images to javascripts. Many companies also use a CDN, a tool which ensures the end user gets their data from a server that is geographically close to them, ...


8

I'm going to try and answer all three questions at once: If you really want to "optimize" your domains then have each domain live, accessible (non-directed), hosted in their own counties, with their own carefully translated content based on the language of that country. Costly. If you want to keep things as simple as possible (like Apple), then pick the ....


7

If they're really pointing their DNS records to your IP address (and your webserver is configured so that this actually shows your site's content on their domain; see Lazy Badger's answer), then you can stop this sort of "DNS hotlinking" with a simple mod_rewrite rule: RewriteCond %{HTTP_HOST} otherdomain\.st$ [NC] RewriteRule ^ - [F] This will return a ...


7

This means that every page on my website is actually accessible from another domain. Any owner of domain can add in managed domain IN A|IN CNAME record, which will point to any IP in the Net, but if you're using name-based virtual hosts, then your site will likely¹ only be accessible via the hostname specified in the ServerName and ServerAlias directives. ...


7

Large sites move their static content (images, JS & CSS files) to a Content Delivery Network or CDN as deploying your content across multiple, geographically dispersed servers will make your pages load faster from the user's perspective. As the CDN has a different domain name, it also provides domain sharding benefits.


7

As long as all the secondary domains simply do a 301 Permanent Redirect to the primary domain, this will not negatively affect SEO at all. It probably wont have any positive effects either, but if you value owning those domains (even if just to ensure noone else uses them) then that may be immaterial. Replicating the content on all the different domains ...


7

SEO and Webmaster Tools You have a couple options. Either of these can work from an SEO perspective. Pick one of them and use that as the "canonical" domain. Use 301 redirects to make sure that visitors all get to the one you choose. OR use the rel canonical meta tag to tell Google which domain is the preferred domain (while letting users access ...


7

The simplest solution is to just return a 403 or 410 response for any traffic on the unwanted domain. In .htaccess on Apache you could do something like: RewriteEngine On RewriteCond %{HTTP_HOST} ^(www\.)?domain\.com$ [NC] RewriteRule ^ - [L,R=410] In Nginx you could do something like: server { listen 80; server_name domain.com www.domain.com;...


5

If you are using a 301 redirect on each of these misspelled sites it does not cause a problem with duplicate content. For all intents and purposes, there is only 1 website when you 301 redirect the other sites to your main site. Here is a google forum question on the topic


5

There are lots of websites with similar domains out there so this won't be an issue. You will only run into issues if you use duplicate content on these two sites (which the domains suggest is probable). If you plan on the second site being a clone, or a slightly different version of the first, you will have duplicate content issue which will hurt the second ...


5

Search engines care about content of the web site and not IP addresses. Period. End of story. Now, if your IP address or domain name is a known spammer; different story.


5

If you can create high quality sites, provide great user experience, and take care not to violate any of Google's webmaster guidelines, there is no problem with having multiple sites on a shared host. With that being said, your sites sound like they could be spammy. You sound like you are at risk of violating the policy against doorway pages. The example ...


5

In most cases the canonical link type could be used in place of 301 redirects, but 301 redirects are almost always preferable. From the canonical RFC (bold emphasis mine): Before adding the canonical link relation, verification of the following is RECOMMENDED: […] For HTTP, permanent HTTP redirects ([…]), the traditional strong indicator that a ...


4

You don't need to buy an additional hosting account. All you need is a 301 from the old URL to your new URL. Having the new URL on a separate IP OR separate host gives you no additional value. All it will create is an additional headache for managing your accounts because you will never want to shut down your old URL (it will always do a 301 redirect). ...


4

Yes it's possible to use unlimited hosting companies to manage your client's websites and still provide them basic FTP, MySQL, and Email access. Once you have added your clients domain to your account as an addon domain. You can create FTP accounts in your control panel, even if you must use your primary domain to generate the accounts such as client@...


4

If the goal of the satellite sites is to drive traffic to the main site, which is about the same/similar topic, then there's really no difference between these satellite sites and having landing pages on your main website. They do the same exact thing except now you have additional websites you have to maintain. If you're trying to establish a brand why ...


4

In short, register all of the domains that you feel/think you need for your specific brands. If you don't it's much harder to get back the brand/domain because your competition has squatted on them. Don't register extra domains like TheBestProductEver.com because you will be penalized. There are a few different reasons for things to keep in mind when we're ...


4

Is there a way to set up the second site side by side on the same hosting service so that Google sees it as ONE site but the end user of each site would not see the other one. You might be able to pull it off with subdomains but that's probably not separate enough given your description. Any other tricks to show Google one thing and the users another gets ...


4

You need to understand what subdomains are. When you purchase a domain, you purchase something like example.com. If you see something like www.example.com or aboutus.example.com, aboutus is just a subdomain of example.com. When you see something like www.aboutus.example.com, www is a subdomain of aboutus.example.com. When you insert a dot (.), you create a ...


4

Do a 301 redirect from the parked domain to the new domain. That will tell the search engines that the existing domain is the main one and will eliminate potential duplicate content issues. It will also be less confusing for your users as they will see a consistent domain when accessing your site. If you are using Apache you can do this easily with a ...


4

example1 and example2 are subdomains of mysite.com. Multi-domain just means a site can be accessed by more than one domain name. Ie.e. two domains pull up the same website.


4

This definitely can't be done with DNS. I think the real question you want to solve is "How do I allow cross-domain PHP and fonts?" To enable cross-domain PHP and font files (this is probably all you need) you would add the 'Access-Control-Allow-Origin' header to domain2's configuration, like so Apache: Header add Access-Control-Allow-Origin "http://...


4

Presumably you don't have a CNAME record for the www subdomain - so the DNS does not resolve? As you suggest in comments, in such cases, some mobile operators (or in fact some 3rd party DNS servers) intercept the response and serve their own content. Very annoying as it makes it difficult to test for invalid requests - the real response code is often masked.


4

It does not. They're seen as entirely different sites as their domain names are different. Domain names only tend to affect SEO when the name itself contains a keyword. Being similar or the same as another site would allow me to register bbc.consulting and gain a boost from being related to bbc.co.uk


4

The rule for indexing is to ask 'Where is the content?' and 'What's the fastest route to it?' Cross domain canonicalisation is treated like a soft redirect. You state that content is served from webapp.com/page but the URI remains domain.com/page. If you're using an iFrame pointing to webapp.com/page, Google will see it as a link and index the linked ...


4

You can use something like this code in your DOCUMENT_ROOT/.htaccess file: RewriteEngine On RewriteCond %{HTTP_HOST} ^(?:www\.)?subdomain\.com$ [NC] RewriteCond ${ipmap:%{REMOTE_ADDR}} !^(127\.0\.0\.1|192\.168\.|10\.|1\.2\.3\.4)$ RewriteRule ^ - [F] Source: answer from anubhava on Stack Overflow You can also allow specific IP addresses and deny the rest ...


3

The 2-item restriction is not an issue any more. While it's a recommendation of the HTTP spec, all modern browsers allow at least 6 concurrent connections.


3

To not waste all your effort about off-page SEO, you should make a Permanent Redirect (code 301) from your old domain to your new domain. But this will be not enough. Infact if you have many links to your website and especially to different pages, I suggest you to do a sort of map. I mean, using the technique you like the most as .htaccess, a plugin if your ...


3

On most LAMP shared hosts you can get this feature by purchasing reseller hosting rather than the standard shared hosting. You typically use a tool called WHM to manage the multiple domain (or a custom in-house tool) and each domain account has it's own login and file structure. They also have separate file and bandwidth levels that you'll have to monitor.


Only top voted, non community-wiki answers of a minimum length are eligible