Here's a nice little tip for startups & mISV's who want to increase their search engine traffic in minutes.
One of the monthly marketing tasks performed regularly at Jitbit is what we call "Lazy SEO".
"Lazy SEO" is finding keywords that already bring you some visitors from search engines, and further optimizing the website for these keywords. If your website is already ranked by some keyword, why not improve the rankings even more?
You can easily locate those keywords in Google Analytics or any other analytics software. When picking a keyword - make sure there's room for improvement. So, first, look at the sites higher in the SERP - can you beat them? Second, it should not be the keyword you're already ranked #1 for.
Example: to promote our Jitbit Helpdesk product, we initially tried to optimize the page for the "helpdesk software" query. Which is almost impossible, since the competition is huge here. But there are a couple of less frequent queries like "help desk ticket software" or "asp.net helpdesk" that already bring some traffic. And adding a couple of sentences to the product description, writing a couple of articles and creating a couple of internal links with the desired anchors does the job: the traffic stream slightly increases.
Lazy SEO (tm) Dec 31, 2008
Christmas Sale 2008 Dec 9, 2008
We are happy to announce the launch of our XMAS Sale 2008 campaign. Get a discount.
VS 2008 "A required privilege is not held by the client" Dec 2, 2008
A small tip for web developers.
If your ASP.NET application uses impersonation and explicitly sets up a user account in the "web.config" - you wont be able to debug this app in Visual Studio 2008 under Vista. You will get the "a required privilege is not held by the client" error message.
Solution: run VS2008 "as administrator".
If your ASP.NET application uses impersonation and explicitly sets up a user account in the "web.config" - you wont be able to debug this app in Visual Studio 2008 under Vista. You will get the "a required privilege is not held by the client" error message.
Solution: run VS2008 "as administrator".