Domain authority and sub-domains

nitinsy

Regular Member
Joined
May 9, 2013
Messages
349
Reaction score
97
The last time I did SEO (long time back), sub-domains were considered to have their own authority. Meaning root domain and sub-domains were treated as separate entities.

I see sites getting links from sub-domains. Even Ahref shows the root domain DR in the root domains report. The root domain has high authority but the sub-domain itself doesn't have much authority or links.

Is it worthwhile getting such links?
 
The backlinks from sub domains still useful as it will gain authority over time and google knows that the sub domain is from authority domain.
 
The backlinks from sub domains still useful as it will gain authority over time and google knows that the sub domain is from authority domain.
Hi friend,
I have an expired domain, almost the backlinks point back sub-domain (http://www.domain.com). My current website is https://domain.com(non-www) So How I can use 100% "POWER" of backlinks.
Should I have create a new sub-domain(https://www.domain.com) after that make a 301 to the current website?
Any advice for me!
Thanks
 
What do you want? www or non-www as your primary site?

If you are not particular then create a site with www and do redirect for https (http -> https). That will probably be the least loss of link juice.

If you want non-www as primary site. You have two options:
1) Redirect from www to non-www (along with http -> https)
2) Let your site render in both www and non-www urls (it is technical possible). Then use rel="canonical". Google respects that and will not loose link juice

There is no perfect answer. Choose what makes sense to you and works for you.
 
What do you want? www or non-www as your primary site?

If you are not particular then create a site with www and do redirect for https (http -> https). That will probably be the least loss of link juice.

If you want non-www as primary site. You have two options:
1) Redirect from www to non-www (along with http -> https)
2) Let your site render in both www and non-www urls (it is technical possible). Then use rel="canonical". Google respects that and will not loose link juice

There is no perfect answer. Choose what makes sense to you and works for you.
Exactly I want my current website is NON-WWW. and HTTPS and it's working well now. I'm having about 10 Posts and 6 Pages.
So as you said. I should change my current site from (non-www) to (www) then using the plugin to redirect from http://www.domain.com --> https://www.domain.com
Is it right?
So the current posts and pages: Will it be affected?
 
Exactly I want my current website is NON-WWW. and HTTPS and it's working well now. I'm having about 10 Posts and 6 Pages.
So as you said. I should change my current site from (non-www) to (www) then using the plugin to redirect from http://www.domain.com --> https://www.domain.com
Is it right?
So the current posts and pages: Will it be affected?

Keep you site on non-www
Use redirection plugin or your host's redirection option to redirect www to non-www

Ideally set up the following re redirections:
1) http://www.site.com -> https://site.com
2) https://www.site.com -> https://site.com
3) http://site.com -> https://site.com
 
Keep you site on non-www
Use redirection plugin or your host's redirection option to redirect www to non-www

Ideally set up the following re redirections:
1) http://www.site.com -> https://site.com
2) https://www.site.com -> https://site.com
3) http://site.com -> https://site.com
Hi friend,
So if I want to recover some old pages like: http://www.domain.com/page1 -> https://domain.com/page1 . So I just need to use the plugin and manually redirect the Pages I want . Right?
 
try this .
.http file in the root of the project put this at the top of the http file.
Code:
<IfModule mod_rewrite.c> RewriteEngine On RewriteCond %{HTTPS} !=on RewriteRule ^(.*)$ https://%{HTTP_HOST}/$1 [R=301,L] </IfModule>
 
try this .
.http file in the root of the project put this at the top of the http file.
Code:
<IfModule mod_rewrite.c> RewriteEngine On RewriteCond %{HTTPS} !=on RewriteRule ^(.*)$ https://%{HTTP_HOST}/$1 [R=301,L] </IfModule>
I totally recommend this less resources and make sure add canonical tag so that google recongnize it
 
No, I just want to recover some pages - not all. I just change my current website from https://domain.com to https://www.domain.com because I see, all my backlinks are pointing back (www). So I have decided to change to www.
All pages and posts are working well.
I have a question, please help me

What should I do now?
1. all my backlinks are pointing back http://www.domain.com (Non-s). So I have used the plugin: " Really Simple SSL" to automatic redirect from HTTP to HTTPS. Right? Or do I need to contact the hosting provider and ask them for help to redirect?
1. Make a redirect 301: https://domain.com -> https://www.domain.com?
So Do I need to do anything else?
Thanks for your help
 
try this .
.http file in the root of the project put this at the top of the http file.
Code:
<IfModule mod_rewrite.c> RewriteEngine On RewriteCond %{HTTPS} !=on RewriteRule ^(.*)$ https://%{HTTP_HOST}/$1 [R=301,L] </IfModule>
Thanks guy
This will help my website redirect from http -> https?. that means: all my backlinks are pointing back http://www.domain.com will redirect to https://www.domain.com and retains all the power from the backlink. Right?
 
No, I just want to recover some pages - not all. I just change my current website from https://domain.com to https://www.domain.com because I see, all my backlinks are pointing back (www). So I have decided to change to www.
All pages and posts are working well.
I have a question, please help me

What should I do now?
1. all my backlinks are pointing back http://www.domain.com (Non-s). So I have used the plugin: " Really Simple SSL" to automatic redirect from HTTP to HTTPS. Right? Or do I need to contact the hosting provider and ask them for help to redirect?
1. Make a redirect 301: https://domain.com -> https://www.domain.com?
So Do I need to do anything else?
Thanks for your help

Both the things above. If you want to use SSL then the first one is required (which can be done by plugins as you mentioned or via .htaccess as @redarrow mentioned

The second one is also required since some users might type domain without www and you don't want to loose that traffic.
 
The last time I did SEO (long time back), sub-domains were considered to have their own authority. Meaning root domain and sub-domains were treated as separate entities.

I see sites getting links from sub-domains. Even Ahref shows the root domain DR in the root domains report. The root domain has high authority but the sub-domain itself doesn't have much authority or links.

Is it worthwhile getting such links?
Why not? :-) I can help you out if you want to boost those metrics fast & safe
 
Back
Top