Ask HN: What is better: artist.domain.com or domain.com/artist?

9 points·northband··10 comments

I'm putting together a simple web app that profiles artists. I'm curious which is better for search engines - having the artist at the beginning of the domain or after?

View on HN

If you want to build strong domain authority and have the artist profiles take advantage of the positive metrics & ranking ability of the domain then use: domain.com/artist (the sub-domains do not always inherit all of the positive metrics and ranking ability of domain.com)

domain.com/artist for seo and easier handling. If you are allowing user generated content and logins, than go for artist.domain.com because it is the only way to isolate cookies.

Cookies have a Path attribute, right? A cookie can be defined to go only to domain.com/artist1 and not domain.com/artist2 .

Thanks everyone - domain.com/artist is what it will be. Look forward to a Show HN: soon once I get this put up.

If the artist focuses on the art, and the art is good, then why would it matter if it's artist.domain.com or domain.com/artist?

I have one word for you: pushState. Eventually you will want to use it, and you're screwed if you used subdomains.

Subdomains can be a little confusing for nontechnical people. Go with domain.com/artist.

DOMAIN.COM/ARTIST

Giving people directories vs. their own subdomains is much easier/simpler to manage.

artistdomain.com

(not artist.domain.com, not domain.com/artist)

keyword ('artist') within the name part (www.name.com) <= 15 characters for the main part, no - or _ in the name part

It sounds as if he/she's starting a website for artists to join, purchasing a new domain for each artist is hardly reasonable.

Reply on news.ycombinator.com