Ask: OK, I've got my Web 2.0 website. How do I promote it?
This is really two questions. The first is: How does one promote a website in general? The second is: How do I promote this particular website? The first question is interesting to a broader audience than just me, but if anyone has any suggestions for the second, I'd certainly be appreciative.
The website is called Golimojo (http://www.golimojo.com) and the service it provides is Wikipedia "autolinking". Basically you can take a webpage and have Golimojo examine it for noun phrases that can be linked to Wikipedia articles whose titles match those phrases. Golimojo is smart enough (I'm using "smart" loosely) to autolink nouns like say "Iraq" or "Iran" but not common words like "page" or "men". It works better on some pages than others. I did most of my testing on political blogs (lots of name dropping) and the online versions of newspaper and print magazine articles (poorly linked even today, fifteen years after the World Wide Web was invented).
Now out of the billion-odd Internet users out there, probably only a tiny fraction of them would find Wikipedia autolinking really useful. Still that could be thousands or even tens of thousands of users. The question for me, is how do I find them? In particular, how do I find them without putting a lot of effort and money into the process?
One obvious target market is Wikipedia editors who might like a tool to help them identify missing links in Wikipedia articles. But there seem to be dozens of Wikipedia mailing lists, and I'm not sure how a service that looks like it might be commercial would be received (I have no commercial expectations at this point).
Any ideas?
36 comments
[ 3.6 ms ] story [ 82.1 ms ] threadI want to shake your hand. This is probably the best example of utilizing Web 2.0 that isn't ambiguously superficial, no obscenely huge banners, flashing colors of "beta" texts. You're attacking the technology at the core. I congratulate you heartily, sir.
I would promote this service personally by NOT making it social (yet), for one thing. There are lots of possibilities in socializing this type of software, which is truly unique and very helpful for research endeavors; all of them good. This may kill some of the buzz you might get from TechCrunch or Mashable on the blogosphere, as it is a great app but I wouldn't rush to make it social just yet. Find the user incentive to socialize it, understand the needs and demands, then bring in the sheep.
Great job by developing a bookmarklet: you see many blogs out there with autolinking, those double underlined links that popup little hover boxes and kill usability by displaying a screenshot of what they're going to see. Maybe even develop your bookmarklet so that it will bring up a smaller, unobtrusive hoverbox with the page title of where you're going (eg. Wikipedia: Tibet) for the end user.
You are correct in estimating that not very many people would find this useful. You may target it at education based blogs, or even yes, wikipedia editors. I know one guy who was just elected to an editor position and I'll be more than willing to ask him if he'd find any use in it.
Finally, commercialization really should be your last thought. 37Signals put it best, solve your problems first and the rest will fall into place. Build to solve problems, not create new ones with financing.
Just my two cents. Awesome application overall, I'm very impressed overall, most notably at your method of attack; sticking with the core technologies and solving a problem from a different angle. Color me surprised if your work goes unnoticed by the big wigs out there.
I'm not even sure how to make it social, so that's certainly not high on my list of things that need to be done. A lot of the design is such as it is because I was scratching my own itch, and I have no love of in-your-face UIs (I didn't fully succeed here, but I can't justify a lot more work unless I get some actual traffic.)
Something to consider: instead of embedding direct links, use redirection so you get a record of every time a link is clicked on.
http://innovation.freedomblogging.com/2008/03/19/top-13-ways...
Right now websites could use the existing service to manually add links to new content. Certain features might make such usage quite a bit easier, for example the ability to take text markup (MediaWiki markup, MarkDown, etc.) and spit it out with links added in the appropriate syntax. This would still be manual, but it would be pretty easy to use.
A fully automatic API could be something as simple as "include this .js file". That's simple, but not very efficient (caching would help of course), and doesn't present the best user experience (there would generally be a delay where the text is visible in the browser, but links haven't been added yet.) A server-side API would certainly be better, but then you have a whole bunch of different server types to support: PHP, Python, Ruby, Java, ASP.NET, or even application specific like WordPress or Drupal, etc.
I could probably roll a client-side JavaScript inclusion API in a weekend, but it would probably take another couple of weekends to implement decent caching.
A server-side solution is ultimately the right way to go, but is there a way to get maximum bang for the buck? Just expose an XML API and let other people do the server-side integration?
The only question with an XML api is how do you benefit from it?
As long as the load doesn't blow out my hosted server, then just some branding on the client might be worth it.
I'm not sure if I see the utility in this... maybe I just don't look things up on wikipedia enough, but Firefox already has a "look <selection> up on Google" in the right-click menu, and most "important" nouns will have a wikipedia link on the front page of Google anyway.
As for promotion, in the "level of connectedness" we now have, word-of-mouth seems to promote products really well. Make something impressive, and people will tell their friends about it. At this point, I won't tell my friends about your site, I probably won't remember it in 15 minutes (unless something on-topic comes up). Do change my mind ;)
So I'd say ... keep working on the idea/implementation until it wows people, at which point users will find you.
Another thing you might want to add is to build a wikipedia based spell checker for the plugin for misspelled names etc.
I see you have a firefox extension - does it do something similar to the above?
As for promotion, ironically this post here on Y News is a great place to start! Its a highly trafficked site with a demo that ranges from the tech influential to the next Sergey/Brin!
http://en.wikipedia.org/wiki/Wikipedia:WikiProject_Wikify - internal Wikipedia project for wikifying more articles.
I might also be cool to make an API so developers could call your service on single words or sections of text from their applications. I might not want whole pages autowikied, but it could be cool to have sections of articles or something. Offering a simple and easy to use webservice can drive adoption of your service in ways that you could never even begin to imagine.
I would also try to find some high profile bloggers in your target audience (in your case politics maybe), and write personal emails to them about how the service could be good for their readers and ask if any would be interested in trying it out, or if there were any features they would really need before the service would be useful for them (such as which wiki links were click through, showing what their readers don't know enough about or are most interested in)
anyways just some thoughts off the top of my head.
I was thinking that this should be turned into a firefox extension, but I see that you already did it.
So people who have to read about difficult concepts in varied areas may find this useful. This could be anyone from students to professional consultants. So finding forums where students are trying to get help with various topics could be a good place to start.
We work with Australian Web 2.0 startups to help them grow traffic, conversions and customers.
It seems in most scenarios the skillset needed to build a great web service, and the skillset required to market, promote and sell that service are be totally different.
Something to be wary of tho, the majority of PR/Marketing/Advertising companies really dont get startups at all, and can be a very fast way to drain your scare capital without offering measurable results.
Any questions, happy to help out.
http://www.ShiftedPixels.com.au