Domain Mapping- Just need clarification
-
The business I work for is looking forward to opening a blog. It’s a great fit for our business, everyone is excited, I’ve been running little “Blog 101” classes- we’re good to go. However, our web host wants to charge us a decidedly very, very expensive fee to host a WordPress blog. I balked, having done a WordPress installation before, but they wont let me near the server to do a self-install.
I realize this is a sign of a bad webhost, but for reasons I can’t really elaborate on, we’re stuck with them for the time being.
My concern is less with where the blog is hosted and more about brand identity. Having the address be “brand.wordpress.com” feels sort of unprofessional. I’d rather the address be “blog.branddomain.com” or “branddomain.com/blog”. We have our own domain, we do a fair amount of mail order from that point, so we’d like to have it look as if it’s in house.
Domain mapping seems to the way to go, but I just wanted to check in and make sure I understand the happenings here: The blog will be hosted on WordPress, but will appear as if it is coming from our own server (blog.ourdomain.com). 10 bucks a year. Any restrictions, caveats?
-
Correct. The blog will officially be hosted at WordPress.com (different than WordPress.org, which is the self-hosted solution, as you may be aware). However, please note that you can NOT map a sub-directory (http://www.example.com/blog), but you CAN map a sub-domain (http://blog.example.com). Get the entire scoop here –
And check out other related topics here –
http://faq.wordpress.com/category/domain-mapping/If you want any other type of specific functionality, please ask/research before purchasing the upgrade.
- The topic ‘Domain Mapping- Just need clarification’ is closed to new replies.