If you've been playing around with Linkscape a little, you've probably seen our attempts at creating a lot of new naming conventions for metrics and features that were previously the exclusive realm of web indexing researchers, information retrieval scientists and search engineers. Things like mozRank & mozTrust (mT) have seemed to work out fairly well so far, but our testers and members have struggled a bit more with mozRank (mR) vs. Domain mozRank (DmR) - one is for a page while the other applies to a domain - and been seriously confused about FQDs vs. PLDs. Let's address this issue.
As search engines scour the web, they identify four kinds of web structures on which to place metrics:
- Individual pages / URLs - these are the most basic elements of the web; file names, much like those we've had on computers for decades, that indicate a unique document. Search engines assign query-independent scores, most famously Google's PageRank, to URLs and judge them in their ranking algorithms. A typical URL might look something like https://moz.com/page.html
- Subfolders - the folder structures that websites use can also inherit or be assigned metrics by search engines (though there's very little information to suggest that they are used one way or another). Luckily, they're an easy structure to understand. In the URL https://moz.com/blog/post, "/blog/" is the subfolder.
- Subdomains / Fully-Qualified Domains (FQDs) / 3rd Level Domains - In the URL https://moz.com/page.html, there are three kinds of domain levels present. The top-level domain (also called the domain extension) is ".org," the 2nd level domain is "seomoz" and the third level domain is "www." These are sometimes referred to as "subdomains," although that nomenclature can also be intended to mean 3rd level domains that are not "www." Again, these structures can receive individual assignments of importance, trustworthiness and value from the engines, independent of their 2nd level domains, particularly on hosted publishing platforms like Wordpress, Blogspot, Wetpaint, etc.
- Complete Domains / Host Domain / Pay Level Domains (PLDs) / 2nd Level Domains - The domain name you need to register and pay for, and the one you point DNS settings towards, is the 2nd level domain (though some improperly call it the "top level" domain). In the URL https://moz.com/page.html, "seomoz.org" is the 2nd level domain.
You can see how we've tackled this in our Linkscape Help Center Concepts area:
However, to date, it's still one of the biggest puzzlers I see when folks are faced with the data, and while I love that we can be so robust and detailed, it's no fun dealing with information overload. There are all sorts of important metrics that can be applied to 2nd or 3rd level domains, but if even the savviest of SEOs struggle to understand/interpret/apply this information it's time for a change.
For example, according to a Linkscape report for SEOmoz:
- https://moz.com - the page/URL has 41,741 links from 3,281 FQDs
- www.seomoz.org - the Fully Qualified Domain (FQD) has 11,734 other FQDs linking to it
- *.seomoz.org - the Pay-Level Domain (PLD) has 10,039 other PLDs linking to it
Being able to quickly and easily understand these differences is important for comparisons, reporting and SEO implementation, but it's a challenge to explain, so I figured I'd put it to our community - what is the best way to describe 2nd vs. 3rd level domains? What should we be calling them and how can we explain it in an easily digestible but granular fashion?
Please use your thumbs to reward answers you like (I know I will, especially since it's nearly Christmas Eve!).
Hi Rand,
Top Level Domain : I refer to as the extension i.e. ".co.uk", ".com", ".org" (Most clients grasp this easily)
2nd Level Domain : I refer to as the actual web address i.e. "xyz.com" (Most clients grasp this easily and will have full access to the domain)
3rd Level Domain : I refer to as a sponsored domain.i.e. xyz.SomeDomainIDoNotOwn.com (Most clients require a visual example to grasp this easily)
A good example of all 3 uses is when using blogger.com or for sending emails using an email client like cheetah mail for example.
i.e.
.com is the TLD
bloger.com is the 2nd Level Domain
myname.blogger.com is the 3rd Level Domain or
myname.hostname.com for the techies.
Hope you all have a great christmas and happy new year.
Shahid :-)
p.s I as myself what am I doing on SEOmoz.org at 8.15 a.m. on Christmas Eve. Well if I'm going to be in the office, I'd rather being getting some thumbs up than checking my emails...
I'd say this break down:
Page/File Links
Subdomain Links
Root Domain Links
"Subdomain" leaves itself open to xyz.hostname.com or abc.xyz.hostname.com which helps catch all that sort of thing, while page/file attaches itself to the idea that the URL being inspected will only have one possible location. Finally, root domain is at the nuggety core of it all.
Good job of condensing the descriptions.
Once you get the clients to understand this, the tough job of getting them to understand how this affects the rankings of their site begins.
I just realized. I don't think your problem is your naming conventions. I think your problem is your UI.
1: You're wasting space. You're repeating information by providing a number and a bar. If you really felt having both of these things were important, I'd suggest putting the text inside the bar (bold white text, make the bar taller (wider).
2: No matter what you name the things, there will be people who don't get it. What you really need is for the bars to have click or hover actions that will reveal what they represent, and why the numbe ris important. The action could result in a new page, a pop up, or a user-tip bubble.
I hope this suggestionhelps reframe your problem, and reveals better answers!
I like a couple of the ideas presented above.
"Root domain" or "base domain" seems to make a lot of sense for what you call "Pay Level" now. I never understood that nomenclature as I think I've posted on some of the Linkscape threads before :).
Going from that as my own "base," for *.domain.com, how about "stemmed domains" or something along those lines?
Something such as Root Domain might work out nicely, since all forms of the domain stem out from the * (star).
I got the article and then you guys confused the heck out of me...LOL
domain name (abc.com)
root (www)
subdomain (sample.abc.com)
subfolder (abc.com/sample.htm)
To say that the sub-domain WWW is ‘root’ is misleading since the term ‘root’ is most often used to describe a DNS server.
Source: https://en.wikipedia.org/wiki/Domain_name
I'd say, calling www.seomoz.org "domain name" would be misleading. First, plenty of people choose not to use www at all, secondly, that's just too general.
For domain.com I vote for either "Root domain" or "base domain".
It seems like you're confusing domain name with hostname.
Isn't it technically referred to as a CNAME?
A CNAME is one way to create a 3rd Level Domain, but you can also accomplish this with an A record or ANAME, so 3rd Level Domain is probably the most technical term. Subdomain would be another.
There must already be names for these defined by IETF in some RFC or other.
I would use those.
Hostnames can have many forms and levels. I'm just looking at something in the form www.username.plantype.ispname.co.uk/ on a free site that comes with their DSL access. Their unique name is the fifth-from-right item.
Wildcard domain? Like wildcard SSL certificates...
I suggest using:
1) Home Page Links (HomeL)
2) Main Domain Links (MainL)
3) Sub Domain Links (SubL)
I won't explain what each would be, because the whole point is for them to be self explanatory, right? Does anyone else agree with the above?
for me,
catchall Domain
might fit. It resebles the catchall email box which most ppl might have heard of. It's not 100% correct, but it may point to another direction.
-m.