3 ms·
Very nice. Congrats on shipping. Why the subdomain blog.mocktailsapp.in? You're building a product which is already established as a thing people need. You ca
by dgunn 14y ago
Very nice. Congrats on shipping.
Why the subdomain blog.mocktailsapp.in?
You're building a product which is already established as a thing people need. You can almost be sure people are searching, right now, for 'mockups with version control' (or some other benefit which differentiates your software from the competition). Your competitors pages are too established for a newer domain like yours to easily out rank them on terms like 'mockups', but since they have little to no reason to talk about things like version control, you can easily out rank them for something like 'mockups'+'version control' or 'collaborative mockups', etc. You should try your best to concentrate your page rank (and links) into a single domain as early as possible to give yourself the maximum advantage.
Search isn't great for the discovery of many apps out there. Since it could be for yours, take advantage of it!
I'm really looking forward to seeing this go forward. Again, great job!
- chaosprophet 14y agoThanks for the kind words and for using Mocktails. As for your question: I subscribe to the belief that if a company has a product page at 'www' subdomain or at the root domain, then it's blog should be located at the 'blog' subdomain. That was literally the only reason for putting the blog there. You are correct in that we dont rank very well for mockups, and your points on SEO are quite apt. However, I do not know much about SEO, so I wonder if the benefits accrued by moving the blog to the 'www' subdomain would be outweighed by placing enough links to the 'www' subdomain in the blog posts. Also, for now, I would like to focus on just building the product, especially since the much-vaunted version control doesn't actually exist yet. This would prevent a ton of support tickets from people who came in searching for 'version controlled mockups' and then dont find the feature anywhere.
- dgunn 14y agoI don't think you should focus on learning the many facets of SEO while trying to deliver a product but there are some quick, actionable pieces of advice which are undisputed enough that you can pretty much blindly implement them. A great place to learn about seo (especially as it pertains to software products and marketing them) is patio11's blog. A particularly relevant, however short, article is http://www.kalzumeus.com/2006/10/02/object-lesson-on-blogging-for-your-business/ http://www.kalzumeus.com/2006/10/02/object-lesson-on-bloggin... which speaks specifically to this point. Also, I would recommend getting as many support tickets as possible. Not only are they feedback from users about what the product needs (you're probably aware of how important this is considering it's the mantra of every notable writer in the startup/saas domain) but they represent people who a.) are interested enough in your product to complain that they can't use it yet and b.) have implicitly given you permission to contact them. A simple, "This will be implemented soon. I'll email you when it's ready." makes the immediate problem disappear while creating a list of users primed and ready to start breaking your software for you when it hit beta and beyond.
- chaosprophet 14y agoHmmm... Again you're pretty much spot on. I guess while we should primarily focus on building the product for now, there is no real reason why we cannot make some simple changes to capture more mindshare and search engine ranking. I'll look into some basic SEO tonight and make some changes ASAP. Once again, thanks a lot for your advice, especially since it's in an area I don't know much of.