Url Rewriting has been known to make sites act strange, with broken image links, missing CSS files and javascrtipt not found errors.  Here's why it happens, how to fix it and how to avoid it in the first place.

Have you got two home pages indexed for your site?  I bet you have.  There are two home pages for most ASP.NET websites - www.domain.com and www.domain.com/default.aspx.  Read on for the final word on this.

If you're getting serious with your Google Adwords advertising, you should probably be trying out different types of page copy to see which works the best.  Here's a quick guide on how to setup Google Adwords testing in a DNN site.

If you've installed the Url Master module, and it's not working exactly as you want, here's some things to try to work out where you're going wrong.

This entry is the first in a series about building SEO modules for DotNetNuke.  It follows on from my earlier posts about building a module that is optimised for search engines, but in this series I am going to build a module and show the relevant steps and pieces of code that go into making it.

For us 'English as an only language' folks, it's easy to skim over globalization issues.  But with a global audience, sooner or later you'll run into problems.  Here's one of mine.

There are three main fields you should be concentrating on for each and every DNN page, and anyone who edits or maintains a DNN site should be doing this in their websites, each time they create or modify a new page.

If you're building or maintaing a DotNetNuke module, then you need to consider these factors to see if the module is Search Engine Optimised, or Search Engine Compromised.

Recently I've been requested by a number of people to explain the differences between the iFinity Friendly Url Provider, and the iFinity Url Master module. The obvious difference is one is free, and the other you have to purchase a licence. To help determine which one you need, I've done up a reference table of the features.

One of the things that has been bubbling away at the back of my thoughts for a while now is ‘DotNetNuke needs an API’.  Of course, DNN already has loads of API, what I mean by this is an open, extendable, web-service style API.  Lots of times I come across something I need to do, and I immediately think – ‘now this is where an API would be handy’.  So, with a concrete project that I needed to do that really was best done with an API, I turned thoughts into code, and the result is a very early stage DNN Web service API.