My site its done on DNN 3 (I think) and I notice that SE are indexing my page multiple times because DNN allow you to access the page with different URLs.
Example:

http://www.dnncreative.com/
http://www.dnncreative.com/Default.aspx?tabid=81

what can i do so SE only index the first url and no the second url?
Does 301 Redirection would work? and how can I accomplished that on a single page in DNN?

I know i can do a script so it refresh the page to a new page but that won't be that clean for SEO.

Help anybody please, a lot of my pages are like that and it's hurting my site. I don't want SE penalized my site for duplicate content.

Thanks in advanced.
LROD.

A product like URLMaster (ifinity.com.au) will do wonders.

Also, google around for "DotNetNuke SEO" and you will find lots of useful information. Look at Bruce Chapman's blog at the Ifinity site, too.

Finally, if you really are using DotNetNuke 3.x, please give serious consideration to upgrading to a modern version: either 5.6.5 or 6.1.2. Besides bug fixes, security fixes, and performance fixes you will find lots of new and improved features, some of which are related to SEO.

Thanks Joseph,
Since I have 3.X, I think i should go to 5.6.5, is 6.1.2 stable?
Do you know any steps on how to update and do you know any stuff that might not work properly with .NET, from the top of your head?
sorry for many questions but the site seems to be very fragile that if i do something, then something else brakes, so at times I consider that if it's working then why touch it, you know but i see that when it comes to SEO the site is getting a bunch of bugs that i think they are not compatible with new technology and stuff, of course its an updated version of DNN so no wonder, plus I know very little about DNN.
One more question, does the new versions have a module or a feature like URLMaster?

Thanks for your help.

Yes, 6.1.2 is quite stable. The biggest issues you may encounter going from 5.x to 6.x have to do with CSS issues. Older skins with older menu systems may need some reworking of the skins and containers.

Over the last month I have upgrade at least half a dozen sites, some from 4.x up to 6.1.2.

Just:
1. Make backups
2. Work on an local copy of the site
3. Make backups
4. Follow the "Suggested Upgrade Path" you'll find in the DotNetNuke Wiki at DotNetNuke.com
5. Make backups

and ...

6. Make backups

I make a backup after every successful step. That way, it is easy to fix and try again.

Never move ahead until you have gotten a clean upgrade at whatever step you are at.

You probably will have to upgrade some modules.

Ask questions if you get stuck.


and ...

MAKE BACKUPS!