.COM vs newer domain extensions
I have a website with a new TLD. I am not trying to advertise here, but listing the domain names is the only way I know how to articulate this question.
I have both, theboss.host and thebosshost.com registered. I chose to use the former, the shorter version for my website.
I am wondering if potential visitors have an aversion to the newer TLDs. Should I just go with the .com even though it is much longer? Are there any SEO implication to using the more obscure domain extenstions?
I think my question is more anthropological/physocological than technical. I would love to hear from anyone with experience or has a solid opinion on the matter.
domains top-level-domains
New contributor
add a comment |
I have a website with a new TLD. I am not trying to advertise here, but listing the domain names is the only way I know how to articulate this question.
I have both, theboss.host and thebosshost.com registered. I chose to use the former, the shorter version for my website.
I am wondering if potential visitors have an aversion to the newer TLDs. Should I just go with the .com even though it is much longer? Are there any SEO implication to using the more obscure domain extenstions?
I think my question is more anthropological/physocological than technical. I would love to hear from anyone with experience or has a solid opinion on the matter.
domains top-level-domains
New contributor
add a comment |
I have a website with a new TLD. I am not trying to advertise here, but listing the domain names is the only way I know how to articulate this question.
I have both, theboss.host and thebosshost.com registered. I chose to use the former, the shorter version for my website.
I am wondering if potential visitors have an aversion to the newer TLDs. Should I just go with the .com even though it is much longer? Are there any SEO implication to using the more obscure domain extenstions?
I think my question is more anthropological/physocological than technical. I would love to hear from anyone with experience or has a solid opinion on the matter.
domains top-level-domains
New contributor
I have a website with a new TLD. I am not trying to advertise here, but listing the domain names is the only way I know how to articulate this question.
I have both, theboss.host and thebosshost.com registered. I chose to use the former, the shorter version for my website.
I am wondering if potential visitors have an aversion to the newer TLDs. Should I just go with the .com even though it is much longer? Are there any SEO implication to using the more obscure domain extenstions?
I think my question is more anthropological/physocological than technical. I would love to hear from anyone with experience or has a solid opinion on the matter.
domains top-level-domains
domains top-level-domains
New contributor
New contributor
New contributor
asked 5 hours ago
K TysingerK Tysinger
62
62
New contributor
New contributor
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
If we're to go by this 2016 survey, general consumers do not trust the new gTLD domain extensions:
We found that roughly half of consumers are uncomfortable visiting
websites ending in new domains, and only 9% of consumers feel
comfortable doing so.
In terms of their overall security, almost half of respondents report feeling less secure online thanks to the
introduction of the new gTLDs. This figure is slightly higher than last year too, showing that the wider domain
industry hasn’t yet done a good enough job to educate the public and organisations about the benfits on offer.
Trust in the new Internet survey 2016 discussion paper - nccgroup
However if your website is targeting more savvy or technical users, it stands to reason that they will be more familiar with the new extensions, understand how they work, and know that they usually don't imply any reduction in trust.
The .io
domain is a great example of a "gTLD" that is often used to target tech-savvy users. While technically not really a gTLD it does function like one in practice - standing for "input/output" - and it is popular among the tech startup community.
Of course it's 2019 now so people may be more familiar with the new gTLDs than they were three years ago. But they likely haven't yet attained the same level of perceived trust as .com
, .net
, etc.
add a comment |
Explaining to someone that your site is at anything(hyphen/dash/minus)youwant.com became a nightmare (for me, personally). Avoid using anything that will put you in a position where you have to explain your DNS to a potential site visitor. It negatively affects traffic flow. Telling people your website is at domain.com requires no further information. Everyone understands it, it's comfortable. .net, .org, and some others are commonplace as well. Use the most logical domain name (preferrably with a more familiar extension).
Using .host makes sense to you. But there's a good chance that seeing it on your marketing materials will make everyone do a double take. Tell some of your friends what your domain will be... do they need an explanation for a site called mydomain.host (with no .com)?
That should tell you all you need to know.
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "45"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
K Tysinger is a new contributor. Be nice, and check out our Code of Conduct.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e) {
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom)) {
StackExchange.using('gps', function() { StackExchange.gps.track('embedded_signup_form.view', { location: 'question_page' }); });
$window.unbind('scroll', onScroll);
}
};
$window.on('scroll', onScroll);
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fwebmasters.stackexchange.com%2fquestions%2f120339%2fcom-vs-newer-domain-extensions%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
If we're to go by this 2016 survey, general consumers do not trust the new gTLD domain extensions:
We found that roughly half of consumers are uncomfortable visiting
websites ending in new domains, and only 9% of consumers feel
comfortable doing so.
In terms of their overall security, almost half of respondents report feeling less secure online thanks to the
introduction of the new gTLDs. This figure is slightly higher than last year too, showing that the wider domain
industry hasn’t yet done a good enough job to educate the public and organisations about the benfits on offer.
Trust in the new Internet survey 2016 discussion paper - nccgroup
However if your website is targeting more savvy or technical users, it stands to reason that they will be more familiar with the new extensions, understand how they work, and know that they usually don't imply any reduction in trust.
The .io
domain is a great example of a "gTLD" that is often used to target tech-savvy users. While technically not really a gTLD it does function like one in practice - standing for "input/output" - and it is popular among the tech startup community.
Of course it's 2019 now so people may be more familiar with the new gTLDs than they were three years ago. But they likely haven't yet attained the same level of perceived trust as .com
, .net
, etc.
add a comment |
If we're to go by this 2016 survey, general consumers do not trust the new gTLD domain extensions:
We found that roughly half of consumers are uncomfortable visiting
websites ending in new domains, and only 9% of consumers feel
comfortable doing so.
In terms of their overall security, almost half of respondents report feeling less secure online thanks to the
introduction of the new gTLDs. This figure is slightly higher than last year too, showing that the wider domain
industry hasn’t yet done a good enough job to educate the public and organisations about the benfits on offer.
Trust in the new Internet survey 2016 discussion paper - nccgroup
However if your website is targeting more savvy or technical users, it stands to reason that they will be more familiar with the new extensions, understand how they work, and know that they usually don't imply any reduction in trust.
The .io
domain is a great example of a "gTLD" that is often used to target tech-savvy users. While technically not really a gTLD it does function like one in practice - standing for "input/output" - and it is popular among the tech startup community.
Of course it's 2019 now so people may be more familiar with the new gTLDs than they were three years ago. But they likely haven't yet attained the same level of perceived trust as .com
, .net
, etc.
add a comment |
If we're to go by this 2016 survey, general consumers do not trust the new gTLD domain extensions:
We found that roughly half of consumers are uncomfortable visiting
websites ending in new domains, and only 9% of consumers feel
comfortable doing so.
In terms of their overall security, almost half of respondents report feeling less secure online thanks to the
introduction of the new gTLDs. This figure is slightly higher than last year too, showing that the wider domain
industry hasn’t yet done a good enough job to educate the public and organisations about the benfits on offer.
Trust in the new Internet survey 2016 discussion paper - nccgroup
However if your website is targeting more savvy or technical users, it stands to reason that they will be more familiar with the new extensions, understand how they work, and know that they usually don't imply any reduction in trust.
The .io
domain is a great example of a "gTLD" that is often used to target tech-savvy users. While technically not really a gTLD it does function like one in practice - standing for "input/output" - and it is popular among the tech startup community.
Of course it's 2019 now so people may be more familiar with the new gTLDs than they were three years ago. But they likely haven't yet attained the same level of perceived trust as .com
, .net
, etc.
If we're to go by this 2016 survey, general consumers do not trust the new gTLD domain extensions:
We found that roughly half of consumers are uncomfortable visiting
websites ending in new domains, and only 9% of consumers feel
comfortable doing so.
In terms of their overall security, almost half of respondents report feeling less secure online thanks to the
introduction of the new gTLDs. This figure is slightly higher than last year too, showing that the wider domain
industry hasn’t yet done a good enough job to educate the public and organisations about the benfits on offer.
Trust in the new Internet survey 2016 discussion paper - nccgroup
However if your website is targeting more savvy or technical users, it stands to reason that they will be more familiar with the new extensions, understand how they work, and know that they usually don't imply any reduction in trust.
The .io
domain is a great example of a "gTLD" that is often used to target tech-savvy users. While technically not really a gTLD it does function like one in practice - standing for "input/output" - and it is popular among the tech startup community.
Of course it's 2019 now so people may be more familiar with the new gTLDs than they were three years ago. But they likely haven't yet attained the same level of perceived trust as .com
, .net
, etc.
answered 54 mins ago
Maximillian LaumeisterMaximillian Laumeister
3,3101727
3,3101727
add a comment |
add a comment |
Explaining to someone that your site is at anything(hyphen/dash/minus)youwant.com became a nightmare (for me, personally). Avoid using anything that will put you in a position where you have to explain your DNS to a potential site visitor. It negatively affects traffic flow. Telling people your website is at domain.com requires no further information. Everyone understands it, it's comfortable. .net, .org, and some others are commonplace as well. Use the most logical domain name (preferrably with a more familiar extension).
Using .host makes sense to you. But there's a good chance that seeing it on your marketing materials will make everyone do a double take. Tell some of your friends what your domain will be... do they need an explanation for a site called mydomain.host (with no .com)?
That should tell you all you need to know.
add a comment |
Explaining to someone that your site is at anything(hyphen/dash/minus)youwant.com became a nightmare (for me, personally). Avoid using anything that will put you in a position where you have to explain your DNS to a potential site visitor. It negatively affects traffic flow. Telling people your website is at domain.com requires no further information. Everyone understands it, it's comfortable. .net, .org, and some others are commonplace as well. Use the most logical domain name (preferrably with a more familiar extension).
Using .host makes sense to you. But there's a good chance that seeing it on your marketing materials will make everyone do a double take. Tell some of your friends what your domain will be... do they need an explanation for a site called mydomain.host (with no .com)?
That should tell you all you need to know.
add a comment |
Explaining to someone that your site is at anything(hyphen/dash/minus)youwant.com became a nightmare (for me, personally). Avoid using anything that will put you in a position where you have to explain your DNS to a potential site visitor. It negatively affects traffic flow. Telling people your website is at domain.com requires no further information. Everyone understands it, it's comfortable. .net, .org, and some others are commonplace as well. Use the most logical domain name (preferrably with a more familiar extension).
Using .host makes sense to you. But there's a good chance that seeing it on your marketing materials will make everyone do a double take. Tell some of your friends what your domain will be... do they need an explanation for a site called mydomain.host (with no .com)?
That should tell you all you need to know.
Explaining to someone that your site is at anything(hyphen/dash/minus)youwant.com became a nightmare (for me, personally). Avoid using anything that will put you in a position where you have to explain your DNS to a potential site visitor. It negatively affects traffic flow. Telling people your website is at domain.com requires no further information. Everyone understands it, it's comfortable. .net, .org, and some others are commonplace as well. Use the most logical domain name (preferrably with a more familiar extension).
Using .host makes sense to you. But there's a good chance that seeing it on your marketing materials will make everyone do a double take. Tell some of your friends what your domain will be... do they need an explanation for a site called mydomain.host (with no .com)?
That should tell you all you need to know.
answered 45 mins ago
elbrantelbrant
43119
43119
add a comment |
add a comment |
K Tysinger is a new contributor. Be nice, and check out our Code of Conduct.
K Tysinger is a new contributor. Be nice, and check out our Code of Conduct.
K Tysinger is a new contributor. Be nice, and check out our Code of Conduct.
K Tysinger is a new contributor. Be nice, and check out our Code of Conduct.
Thanks for contributing an answer to Webmasters Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e) {
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom)) {
StackExchange.using('gps', function() { StackExchange.gps.track('embedded_signup_form.view', { location: 'question_page' }); });
$window.unbind('scroll', onScroll);
}
};
$window.on('scroll', onScroll);
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fwebmasters.stackexchange.com%2fquestions%2f120339%2fcom-vs-newer-domain-extensions%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e) {
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom)) {
StackExchange.using('gps', function() { StackExchange.gps.track('embedded_signup_form.view', { location: 'question_page' }); });
$window.unbind('scroll', onScroll);
}
};
$window.on('scroll', onScroll);
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e) {
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom)) {
StackExchange.using('gps', function() { StackExchange.gps.track('embedded_signup_form.view', { location: 'question_page' }); });
$window.unbind('scroll', onScroll);
}
};
$window.on('scroll', onScroll);
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e) {
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom)) {
StackExchange.using('gps', function() { StackExchange.gps.track('embedded_signup_form.view', { location: 'question_page' }); });
$window.unbind('scroll', onScroll);
}
};
$window.on('scroll', onScroll);
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown