Web Hosting Talk : Web Hosting Main Forums : Web Hosting : Please solve this problem

[teper]

I have a shared hosting account with 5 add on domains

Let us suppose i have abc.com as the main domain and added xyz.com as the add on domain. Now in the file manager there will be a folder named xyz.com where i can upload my website files for xyz.com

But here is this little problem i am facing. I can access xyz.com from this url also abc.com/xyz.com Now this will create duplicate content issue. Is there any solution to this problem?

[teper]

and also after adding an add on domain, a sub domain xyzcom.abc.com is automatically created.How to remove this sub domain

[care4server]

you can try .htaccess rule to block access by url abc.com/xyz.com

[PlexHosted]

I would suggest to configure 301 redirect from xyz.com folder to xyz.com via .htaccess

[MikeDVB]

mod_rewrite is a solution or you could create the add-on domains outside of public_HTML if your provider allows it.

Realistically if you never site map those addresses or visit them then google won't know. But put a rewrite in the addon domain .htaccess that checks for the right domain and redirects if it's not right :-).

[teper]

Found a solution to the first problem

RewriteEngine On
      RewriteCond %{HTTP_HOST} ^(www.)?domain.com$ [NC]
      RewriteCond %{REQUEST_URI} ^/addonfolder/(.*)$
      RewriteRule ^(.*)$ - [L,R=404]

Can any body help me with the coding for the second problem of sub domain?

Originally Posted by MikeDVB

you could create the add-on domains outside of public_HTML if your provider allows it.

That's interesting. How to know if my host support this feature?

Originally Posted by MikeDVB

Realistically if you never site map those addresses or visit them then google won't know.

Just taking precautions because of panda update.

[UnderHost]

Originally Posted by teper

Found a solution to the first problem

RewriteEngine On
      RewriteCond %{HTTP_HOST} ^(www.)?domain.com$ [NC]
      RewriteCond %{REQUEST_URI} ^/addonfolder/(.*)$
      RewriteRule ^(.*)$ - [L,R=404]

Can any body help me with the coding for the second problem of sub domain?

You can just delete the subdomain created via cPanel without problem.

[teper]

Originally Posted by UnderHost

You can just delete the subdomain created via cPanel without problem.

That is the main problem. While adding an add on domain a sub domain is created automatically in cpanel and strangely it is not present in the sub domain section also. Must be a problem with cpanel.

[JamesOakley]

Try

RewriteCond %{HTTP_HOST} ^xyz\.abc\.com$ [NC]
RewriteRule ^(.*)$ http://www.abc.com/$1 [L,R=301]

[MikeDVB]

Put this in the directory with the add-on domain and no matter how it's loaded (be it addon.maindomain.com or maindomain.com/addon it will see that the http_host is not www.the-add-on.com and redirect there with a 301 (permanent) redirect so that search engines do not index the incorrect URL and only index the correct destination. You will want to add a new line for the HTTP_HOST for any subdomains you use on the add-on domain so they do not get redirected.

RewriteEngine On
RewriteCond %{HTTP_HOST} !^www.\the-add-on\.com$
RewriteRule ^(.*)$ https://www.the-add-on.com/$1 [R=301,L]

[008Rohit]

Originally Posted by MikeDVB

mod_rewrite is a solution or you could create the add-on domains outside of public_HTML if your provider allows it.

I want it badly. Can you set this up for me?

[MikeDVB]

Originally Posted by 008Rohit

I want it badly. Can you set this up for me?

Want what badly? You can already create a domain outside of your public_html, just when you go to create the domain edit out the "public_html/" part.

[008Rohit]

Originally Posted by MikeDVB

Want what badly? You can already create a domain outside of your public_html, just when you go to create the domain edit out the "public_html/" part.

Never really noticed it. Silly me!
Thanks a lot for helping.

[MikeDVB]

Originally Posted by 008Rohit

Never really noticed it. Silly me!
Thanks a lot for helping.

Sure thing.

[fshagan]

robots.txt would also work if you want to maintain access through the subdomain and don't want to use a rewrite rule. Just deny the subdomain and Google won't index it as a subdomain.