Which one is better for blog? domain.com/blog or blog.domain.com

15 replies
hi warriors,

Like the title says,

Which one is better for blog, domain.com/blog or blog.domain.com

I would like to create a new wordpress install on my domain. Which one I should go for? Where should I install on?

domain.com/blog

or

blog.domain.com

If you are in my situation, which one is you prefer?
This is just a simple question. Hope anyone would drop some answers.

Thanks
#blog #blogdomaincom #domaincom or blog
  • Profile picture of the author inxie
    "Since search engines keep different metrics for domains than they do subdomains, it is recommended that webmasters place link-worthy content like blogs in subfolders rather than subdomains. (i.e. www.example.com/blog/ rather than blog.example.com) The notable exceptions to this are language-specific websites. (i.e., en.example.com for the English version of the website)."

    Moz's official stance on Subdomain vs Subfolder - does it need updating? | Moz Q&A
    {{ DiscussionBoard.errors[9664017].message }}
    • Profile picture of the author mattyseo
      domain.com/ blog always. Dont create a subdomain, its too risky and looks spammy.
      {{ DiscussionBoard.errors[9664829].message }}
      • Profile picture of the author masterqif
        Originally Posted by inxie View Post

        "Since search engines keep different metrics for domains than they do subdomains, it is recommended that webmasters place link-worthy content like blogs in subfolders rather than subdomains. (i.e. www.example.com/blog/ rather than blog.example.com) The notable exceptions to this are language-specific websites. (i.e., en.example.com for the English version of the website)."

        Moz's official stance on Subdomain vs Subfolder - does it need updating? | Moz Q&A
        Originally Posted by Kelvin Chan View Post

        Folder or directory. No doubt about it.

        Avoid subdomains unless it makes the url really pretty.

        Like http://ice.cream.com for example v.s. http://cream.com/ice
        Originally Posted by mattyseo View Post

        domain.com/ blog always. Dont create a subdomain, its too risky and looks spammy.
        Thanks for the reply, well I guess I need to install a new wordpress on the folder right?
        {{ DiscussionBoard.errors[9665461].message }}
        • Profile picture of the author kilgore
          Originally Posted by masterqif View Post

          Thanks for the reply, well I guess I need to install a new wordpress on the folder right?
          That's probably the easiest solution, but it's far from the only solution. You can use Apache aliases for instance or if you're running something like Varnish Cache, you could write a rule that would send all traffic to /blog/ to a completely different server. Personally, I like to keep my software separate in order to have tighter deployments and to minimize potential security vulnerabilities, so I'd probably go with the separate server option, but my requirements and your requirements are likely different.
          {{ DiscussionBoard.errors[9665501].message }}
          • Profile picture of the author Michael Shook
            Domain.com/blog is simplest, requires less tech knowledge to keep up and running well, and truthfully looks easy to people who want to read what you have to say. Most people will (even unconsciously) understand what /blog is. Not so much with blog.domain.com
            Signature


            {{ DiscussionBoard.errors[9665511].message }}
            • Profile picture of the author nik0
              Banned
              A sub domain gets treated as an individual entity so it doesn't strengthen your main domain and doesn't benefit from the main domain either. That's why it's better to go for a folder / directory setup. Do make sure if you add /blog/ that it has a decent structure with categories and such, that seems to be more and more important these days. Google loves well structured sites so don't turn it into a content farm type of thing.
              {{ DiscussionBoard.errors[9665524].message }}
          • Profile picture of the author masterqif
            Originally Posted by kilgore View Post

            That's probably the easiest solution, but it's far from the only solution. You can use Apache aliases for instance or if you're running something like Varnish Cache, you could write a rule that would send all traffic to /blog/ to a completely different server. Personally, I like to keep my software separate in order to have tighter deployments and to minimize potential security vulnerabilities, so I'd probably go with the separate server option, but my requirements and your requirements are likely different.
            I would probably don't do that because I don't anything about varnish cache and such..

            btw, thank you everyone for respond to this question. It is really helpful

            Thanks
            {{ DiscussionBoard.errors[9665860].message }}
  • {{ DiscussionBoard.errors[9664061].message }}
  • Profile picture of the author Kelvin Chan
    Folder or directory. No doubt about it.

    Avoid subdomains unless it makes the url really pretty.

    Like http://ice.cream.com for example v.s. http://cream.com/ice
    Signature

    {{ DiscussionBoard.errors[9664395].message }}
  • Profile picture of the author iAmNameLess
    In my opinion, the only time you should be using sub domains is when your brand or your domain gets a lot of searches itself... OR if you're doing reputation management.

    This gives your website more search engine real estate for those keywords.
    {{ DiscussionBoard.errors[9664746].message }}
  • Profile picture of the author DubDubDubDot
    If the blog is going to have the same type of content meant for the same viewers of the rest of the site, there is never going to be any question how Google handles example.com/blog. That is the safe choice if you don't want to risk choosing sides between SEO "experts" arguing over the sub-domain matter.

    Originally Posted by mattyseo View Post

    domain.com/ blog always.
    something.example.com makes sense in exotic use cases where the content and/or viewers are different than those on example.com.

    Beyond that, using it for aesthetics because you don't like the looks of example.com/blog, nobody can really say for sure.
    {{ DiscussionBoard.errors[9664949].message }}
  • Profile picture of the author tyronne78
    Here is another good post on the Moz blog regarding the subject of root domains,subdomains,and subfolders:

    Root Domains, Subdomains vs. Subfolders and The Microsite Debate - Moz
    {{ DiscussionBoard.errors[9665555].message }}
  • Profile picture of the author ChrisBa
    I also agree to use the subfolder over new domain..
    {{ DiscussionBoard.errors[9665561].message }}

Trending Topics