Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...DotNetNuke SEO weaknessesDotNetNuke SEO weaknesses
Previous
 
Next
New Post
11/25/2008 10:57 PM
 

i find the google webmaster blog also quite useful to read. For example, this great article about the "duplicate content penalty": http://googlewebmastercentral.blogspot.com/2008/09/demystifying-duplicate-content-penalty.html


Erik van Ballegoij, Former DNN Corp. Employee and DNN Expert

DNN Blog | Twitter: @erikvb | LinkedIn: Erik van Ballegoij on LinkedIn

 
New Post
11/25/2008 11:02 PM
 

Hector Minaya wrote
 

I'm researching material for a couple of blog posts about what if any weaknesses the DotNetNuke platform has and what can we do about it, if you raise a good point I'll me more than happy to mention you on my blog when I write about it.

I'd be interested to hear your thoughts on the matter..... Please comment...

 


to answer the original poster: even though the core might have some weak points, you should realize that DNN is very extensible, and almost any "weakness" can be solved by custom modules or custom providers...

The thing is.. we can't just start using a different url rewriting scheme, as that might brake a lot of existing sites. Also: a lot of DNN sites have quite respectable page ranks, and do not seem to suffer too much from any "weaknesses".


Erik van Ballegoij, Former DNN Corp. Employee and DNN Expert

DNN Blog | Twitter: @erikvb | LinkedIn: Erik van Ballegoij on LinkedIn

 
New Post
11/26/2008 12:18 AM
 

IFinity's free module is all I ever use anymore.

Well I better make sure I send you any beta versions first before releasing them, Chris.

Not sure if the ifinity provider is better supported that way than the core provider...

The iFinity Friendly Url Provider uses all of the core API's and integrates directly into the framework as the specified Friendly Url Provider.  In this way, it always works with other modules, unless the module uses some sort of after-the-fact replacement of the Url from the Core API (and, admittedly, the core RSS feed function).  Generally the only problems I need to sort out for people are the occasional obscure bug and configuration for more advanced setups, such as running sites with no extensions along with modules that use different handlers and their own rewriting schemes.    It's true that some modules have shown to be incompatible, but the provider allows for page-by-page human friendly exclusion, whereas the standard HumanFriendly mode is either on or off for the whole install.

As for the OP : the biggest weakness has been the standard skins and layout, and the standard Solpart menu.  IMO these have far more detrimental effect than a couple of Tab Id's in the URL.  Other weaknesses include the lack of a 'preferred' portal alias (all aliases are considered equal) and the myriad of 'accepted' url formats that lead to duplicate content for many.

However, I always finish a post like this with : remember that not all websites are SEO focused.  Some are intranets, some are private sites, some people just don't care.  It's good to keep SEO in mind in terms of options when building core functionality, but it shouldn't be the only factor taken into consideration.  If people are focused on SEO the tools and knowledge are there to help them.

 
New Post
11/26/2008 8:08 AM
 

Thanks for all of the material, anyone else care to weigh in....

 


 


Hector Minaya
Microsoft Visual Basic MVP | Speaker INETA - Latam
MCSD | MCT | MCTS : SQL Server
blogs: Hector Minaya | DotNetNuke SEO | Blogger SEO | facebook junkie | SEO Tools

 
New Post
11/26/2008 8:30 AM
 

Bruce Chapman wrote
 

 ... and the standard Solpart menu ...

the old solpart menu has decent support for the main search engines (they see downlevel rendering), which at least makes sure that the search engine can reach all pages...

Also.. the main weakness of the old default skin (dnn-blue) was that every skin-kiddie uses that to start his skin. Which might have been not so bad 3 years ago, but now....


Erik van Ballegoij, Former DNN Corp. Employee and DNN Expert

DNN Blog | Twitter: @erikvb | LinkedIn: Erik van Ballegoij on LinkedIn

 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...DotNetNuke SEO weaknessesDotNetNuke SEO weaknesses


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out