WordPress.com vs WordPress.org

by Heather Jacobson

I do quite a few installations for WordPress.com blogs and often times, I’ve noticed that they pay for both domain mapping and the custom CSS ability. That amount adds up to $30 a year (roughly) and for that they can basically make it LOOK like their site is on it’s own domain and modify the look of thier blog.

What I don’t understand is WHY they would choose this platform and pay $30 a year when they could spend the same amount and have a self-hosted WordPress blog?

For me, it doesn’t make sense.  The backend of WordPress is the same whether you’re on self-hosted or WordPress.com, so it’s not like you would have to learn anything new.

You have more control over your blog with self-hosted than you do on the wordpress.com site in that you can make your blog function like you want to.

You can add Javascript to your blog.

The list is endless as to what you can do.

But what I did learn at BlogHer this year in talking to people is that they are worried about losing subscribers if they make the move and here’s what I want to say…

If they don’t notice that you’ve moved?  If they don’t read your blog regularly now in that they miss the annoucement that you’ve moved, do you really care if you lose them?

If you’re a wordpress.com user, take some time to think about what you want to do with your blog.  Are there things that you wish that you could do, but haven’t figured out how?  Are there tweaks that you would like to make but can’t?

If you’re paying $30 a year for more functionality on your wordpress.com blog, why not pay $30 a year for a self-hosted blog and have comeplete control over your blog?

Of course, if you are happy with wordpress.com and it does everything you want it to do, then by all means stick with it.  WordPress.com is not a bad service unless you want a little more control… like me.

::stepping down off my soap box::

Similar Posts


Leave a Reply

Your email address will not be published. Required fields are marked *