Portal Home > Knowledgebase > cPanel > Does Google work with addon domains?
Does Google work with addon domains?
A typical issue when developing addon websites is, what about the corresponding subdomain and the likelihood of seeing my website as http://primarydomain.com/subfolder ? I don't want my website to be seen those methods and I don't want to threat having copy material on the internet. Well, never worry.
The subdomain name and the primarydomain/subfolder name will not be seen by the Google, unless you weblink to it.
EXAMPLE: Let's say you own mynewworld.com and choose to create it an addon sector. If you post any hyperlinks, intentionally or unintentionally, that factor to http://primarydomain.com/myworld.com/ , then the Google will understand of this name and create it aspect of their Google look for.
EXAMPLE: Let's say you own mynewworld.com and choose to create it an addon sector. If you post any hyperlinks, intentionally or unintentionally, that factor to http://myworld.primarydomain.com/ , then the Google will understand of this name and create it aspect of their Google look for.
If you create no hyperlinks to those titles, the Google won't discover them.
It's simple to create sure you don't intentionally weblink to those titles, but what could cause someone to unintentionally weblink to these names?
If your public_html has no catalog web page available AND record has not been impaired, then you need to examine what your main domain's web page looks like. If it has a listing record, also known as an "Index of page", then you are unintentionally creating each computer file and listing name into a openly available weblink. As soon as Search engines looks at your main sector, it has all of those hyperlinks.
EXAMPLE: Let's say you own myworld.com and choose to create it an addon sector. If you don't have any web page on your main sector, you may get the main domain's web page looks like this:
Index of primarydomain.com
Apache/2.2.10 (Unix) mod_ssl/2.2.10 OpenSSL/0.9.8i DAV/2 mod_auth_passthrough/2.1 mod_bwlimited/1.4 FrontPage/18.104.22.16835 Server at primarydomain.com Port 80
What if Google already got those bad links?
First, be sure to do everything described above.
Second, you need to turn off the primarydomain.com/subfolder and subdomain.primarydomain.com titles on your server. There are a several methods to achieve this.
You only need to select one of these options:
Do you have enough cash to sign-up a new domain name? Modify your main domain name; this is the easiest remedy as it repairs all hyperlinks in Look for engines relating to the bad titles. (Do not add the old main domain returning to the server.) This creates the undesirable titles go away. If you have any programming that uses the old main domain, you must upgrade it. Are you an professional coder? Make redirect or reword guidelines to turn the bad titles to the add-on domain address. This can be challenging, as you need to be sure the transformation performs for all the hyperlinks discovered by Look for engines. Search "site:primarydomain.com" in Look for engines to see all the hyperlinks they have (replace primarydomain.com with your real domain).
Add to Favourites Print this Article