SEO.NET

Graffiti Cms by Telligent

There are a fair few CMS solutions floating around in .NET at the moment, a good general comparison tool can be found at CmsMatrix.org. Cuyahoga In the past, the Cuyahoga Website Framework has looked always fairly interesting, it is also built on NHibernate which to me is a plus. Most things I've done with NHibernate have generally "just worked", maybe it's because NHibernate development is pounded with unit tests, whatever it is, it works. I haven't had any experience developing any extensions for Cuyahoga, so I don't know exactly how extensible it is yet. In terms of usability, I did find the interface...

posted @ Thursday, February 21, 2008 10:16 PM | Feedback (1)

A Free, FreeTextBox Alternative

I don't know why but FreeTextBox has just never cut it for me. It's wonderful and easy to install and it comes as a nice control in a .NET assembly. But it doesn't give you the nicest HTML back, in fact I'd go as far as to say, it mutates GOOD HTML you put in there yourself, this is bad. Luckily there are some other free alternatives such as TinyMCE, which is a nice little editor. The only catch is it's pure javascript and requires a little manual intervention to work with your serverside code. On a...

posted @ Wednesday, February 21, 2007 9:57 AM | Feedback (6)

Search Engine Optimization for .NET

Search Engine Bot Detection So after I first noticed a large build up of strange session Urls in Google searches for my domain I've then done a little bit of research into the issue and discovered it was .NET not detecting that the search engine spider was Mozilla/5.0 compliant and inserting some rubbish session id into the url. It's been nearly a week since my changes to correct this and there's already a small indication of the 'healing' process. The pages are not out of the index yet, (and yes I do know that I 'could' remove them manually) but there...

posted @ Sunday, December 17, 2006 1:42 AM | Feedback (2)

Cleaning Up ASP.NET Sessions in Google

ASP.NET and Dirty Urls There are two things that have been bothering me about pages that are getting indexed in Google from an ASP.NET application. The first is somehow there are ASP.NET Session Urls ending up in the Google index. This is bad because searchers that actually do click these links are likely to get a 500 error (internal server error) because they will be trying to access a page of an expired session. How is Google finding all these 'bad' urls? Well apparently there is no browser definition in ASP.NET 2.0 for the Googlebot's useragent string, so when the spider...

posted @ Wednesday, December 06, 2006 11:49 PM | Feedback (3)