Finally I can tell you about a great new service from Cligs called Cligs Verticals.

It works like this: Cligs offers to host a landing page right here on cli.gs that is co-branded with your company’s brands. The landing page promotes your product and has a customized URL shortening box. The end result is a portal for your users to easily shorten links to your website.

What does this look like? Our launch partner is FreePatentsOnline.com, the net’s best patent database (I use them every day!) and their landing page is at cli.gs/fpo. You can see their branding, their patent search box, and the URL shortening form.

As with the Cligs White Label product, we can customize this landing page quite a bit. We can modify the template, the actual text is worked on by both of us, the actual URL shortening function can be customized (e.g. the shortenings can be associated with your Cligs account), and much more.

For more info and to get your own co-branded landing page, please contact me and we can have you up and running in no time.

Today Twitter introduced some new changes today that break Cligs and other Twitter functions. This post details the problem and I’m about to file a bug report.

So as of a few hours ago some users are seeing the following problems:

• In Cligs, if you click the Twitter bird to post your clig to Twitter, it will not populate the tweet composition box.
• If you search for anything on search.twitter.com and click the reply link to any tweet, the composition box is also empty.

From my testing and various reports, this seems to be related to Twitter’s current test with their search integration into the Twitter interface. In all cases I’ve seen, the functionality breaks because Twitter introduced an extra redirect that always ends up at http://twitter.com/timeline/home instead of the usual http://twitter.com/home.

According to Twitter’s blog post about the test, only a small subset of users are part of this test. The @cligs account is part of the test but my personal account is not. With @cligs, I see the above problems but not with @pierrefar.