8

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;...


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

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 ...


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 IRI's ...


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

You can do this in nginx by using the reverse proxy option, something like this will work: server { listen 80; server_name exampleA.com www.exampleA.com; location / { proxy_pass http://exampleB.com; proxy_redirect off; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-...


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

My first thought when reading the question was that this is going to be a case for the web-spam team. Please don't create tons of sites that are essentially doorway pages. Also, using wildcard subdomains (assuming the idea is to map them to cities after DNS resolution) make it extremely hard to determine how those URLs should be crawled. Additionally, I ...


3

I do agree in the most part with the other answers, and I want to say "No; it doesn't matter", however, there are a couple of points I'm having trouble to shake in this instance that I can't help but feel will at least cause some confusion and worst lose some business... You both have the same company name and you both offer the same service in the same ...


3

The problem you're having is solved with CORS: The Cross-Origin Resource Sharing standard works by adding new HTTP headers that allow servers to describe the set of origins that are permitted to read that information using a web browser. Additionally, for HTTP request methods that can cause side-effects on user data (in particular, for HTTP ...


3

If you are on the same server, then set the document root for exampleA.com to the same document root as exampleB.com. Example: Point them both to /the/path/to/hosting/folder They should then show exactly the same content.


3

Apache supports this feature, its called a reverse proxy. It will work whether or not the sites are served from the same server or not. One way to do so would be to use mod_proxy with the Apache webserver. The configuration of the virtual host for public would look like this: <VirtualHost *:*> ServerName exampleA.com ProxyPass / http://...


3

There are four valid addresses...and they all show the same site; they are synonyms (no re-direction). Prior to considering your sitemap, which is not essential for Google to index your site, you should deal with all the duplicate content issues you have going on here. As covered in this Google Webmaster Tools help doc: Duplicate content generally ...


3

No actually- the other way 'round. If your domain name registration on these sites are similar or identical, having contact information on your sites that supports the domain name registration by being at least somewhat similar or identical will actually boost your domain trust scores. As part of two efforts; anti-spam and author identification/valuation, a ...


3

Edit based on Joao's comment* The domains in question are cctld, i.e .es, .it, .pt. Geotargeted subfolders on country specific domains don't work well, if the top level domain is generic (i.e. .com) this solution works. Otherwise, from a pure "best for ranking" perspective, keeping cctlds that only serve one country is best, but, like every solution, each ...


3

The best option would be to redirect those pages to respective pages on the new domain. And notify Google using the change of address tool: https://support.google.com/webmasters/answer/83106?hl=en Now, since you did the migration about a year ago and if you are happy with your current ranking then you may delete the old domain. I wouldn't recommend ...


3

It is quite common for a single business entity to have multiple websites. In your example having one website focused on the wedding photography and having the other dedicated to other generic photography will be fine as long as substantial content is unique and relevant to the specific focus of the site. As for removing addresses or abn numbers these are ...


3

How does this affect SEO? Foobars it. How to notify Google about this? You can't. This will likely create confusion to some users, what do you think? Absolutely! Should the site be redone again using just one domain only? given the fact that the company is just starting out in a competitive niche. Absolutely! TL;DNR Your developer is not only wrong ...


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