The developer(s) of this may really want to rethink the name.
Not only is it pretty un-googleable due to other, older results likely taking priority, it's also likely that a potential customer accidentally lands on a website full of malvertising. That aside, the word "keygen" is probably morally negative to many people.
> Not only is it pretty un-googleable due to other, older results likely taking priority
Is there a name for this phenomenon? The creators of Angular fell victim to this effect. They changed around the naming so that "Angular" is supposed to refer to versions 2.X+ and "AngularJS" refers to versions 1.X, but unfortunately the search engines are all poisoned such that "Angular" searches lead you to 1.X results, etc...
Founder here--appreciate the feedback! The name is both tongue-and-cheek as well as an attempt to redeem the word. Years from now, you might search ”keygen for X” and be shown pages of results related to this product instead of pirated software. And since the product is primarily geared towards developers, I think it works (and also invokes a little curiosity). Also, I haven't seen any SEO issues thus far, especially since I'm not really trying to rank for searches that contain ‘keygen’ right now.
Actually, this gave me an idea. The founder of keygen.sh can generate landing pages advertising cracks/serials/keygens for download on tons and tons of different software.
When the search engines index these landing pages, whoever has an alert setup to monitor their products will get a notification about your website. Let google automate your marketing.
The other benefit is that you can use your logs as a sales tool when pitching your product to developers. "Hey Developer, 38 people came to <<url>> today looking for a crack/serial to your <<software name>>." Hopefully those developers will then visit your page for more information which turns into a sale.
One way to solve that is to track "scene releases" [0] and download the releases for software you think could become keygen.sh customers. Then reverse engineer the cracks or patches and document the process. Next, show how keygen.sh would have prevented this cracking technique. Now you have original content that will help you sell keygen.sh.
A byproduct of this will continuously give you ideas on how to improve keygen.sh.
It is very important to note that keygen.sh or any licensing platform will ever be uncrackable but if you can delay the time software gets cracked by a week or two then it could possibly translate into more sales for the keygen.sh customer.
At the end of the day, it is on the keygen.sh customer to sell their product and keygen.sh to delay the release of a crack for it.
Not really... but what's the point of starting a business if you don't believe in it? I wasn't stating it as fact; it was more of a 'wouldn't this be cool' statement--sorry if I came off wrong.
If that's the case, integrating Keygen server-side using a custom domain e.g. licensing.example.com would get around that, but so far this hasn't been an issue at all.
Not only is it pretty un-googleable due to other, older results likely taking priority, it's also likely that a potential customer accidentally lands on a website full of malvertising. That aside, the word "keygen" is probably morally negative to many people.
The technology looks fascinating, however.