Call Us 203.687.6053

Blog with a focus on DotNetNuke news, tips and tricks, DNN SEO, and insights and opinions about the DNN community at large.

DNN SEO Quickstart Guide

Posted by Tom on Monday, July 09, 2007 to DotNetNuke, SEO, SEM, DNN Tips and Tricks

This post is meant as a springboard for consultants, designers, programmers and end-users who are well-versed in DNN, but who may have some catching up to do when it comes to search engine optimization and search marketing. While I make some DNN-specific recommendations, most tips given here are applicable to any website, build on DotNetNuke or not. So here are my top ten SEO tips in order of priority. Actually, forget the order, it's not worth the fight. Just try to implement as many of these suggestions as you can.


  1. Take care of your meta tags, especially the page title and description. Include your most important keywords, but limit your titles to 65 characters including spaces. Choose modules with SEO in mind, such as Ventrian's News Articles, which writes the article title into the page title for you. Furthermore, write unique page descriptions for all your pages.

  2. Start attracting relevant links to your website. Note the word "relevant", meaning that some links are more valuable that others. If you are running a business around DNN as we do, then one link from dotnetnuke.com is much more beneficial than all the links in footers of client sites. As attractive links are hard to come by, consider submitting your URL to industry specific directories.

  3. Don't skimp on quality copy and content. That's what search engines live off. Use a free tool to do some basic keyword research and then sprinkle them around your copy. Don't forget the spell and grammar check, you are targeting (mainly) people after all. In my opinion, a professional copywriter is the most overlooked member of most web teams.

  4. Create an XML sitemap of your website and submit it to all major search engines. I prefer a tool such as xml-sitemaps.com to build my sitemaps over DNNs dynamically created sitemap file. Don't confuse this with a sitemap page, listing links to all of your pages, which is beneficial as well.

  5. Place a robots.txt file into the root of your site to guide search engine spiders. Take a look at the robots.txt file of the mothership for a DNN-centric example.

  6. Get into the game of local search if your websites promotes a "brick and mortar" business. Many searchers include some kind of local identifier such as the town, city or zip code, which catapults you to the top of the organic search results with minimal effort.

  7. Write well-formed, standard compliant HTML to improve accessibility and "crawlability." Consider excessive in-page JavaScript, HTML layout tables and frames junk food for search engines spiders. I'm well aware that strict XHTML remains a challenge with DNN, but let's make an effort to move away from quirks mode by adhering at least to XHTML transitional.

  8. Seek an alternative to DNN's default solpart menu and lead spiders deeper into and around your site with well-formed internal links (don't use tracking or logging with the announcement module and pay attention to how your editor of choice "builds" links.)

  9. Make DNNs friendly URls even friendlier with 3rd party URL rewrite providers such as this one or that one. These providers do have their limitations though, which is why I recommend them only for small to mid-size websites.

  10. Cut down on duplicate content by implementing a 301 redirect from non-www to www or vice versa. I also recommend going as far as hard-coding your login and register links into your skin to further minimize duplicate content created by the "returnurl" querystring parameter.

So there you have it, a high-level overview of search engine optimization techniques geared towards DotNetNuke based websites. Don't be fooled though, SEO and SEM have grown into vast fields with search engines constantly refining and tweaking their ranking algorithms. Another important point I would like you to carry close to your heart is that you are designing and building websites primarily for people and not for search engines. As long as you strive to serve your visitors well, search engines will follow.


Permalink Permalink      Comments 21 Comments      RSS feeds RSS feeds      Email updates Email updates

 

Comments

Comment By Mitchel Sellers on Monday, July 09, 2007 at 1:31 PM

Tom,

This is a great article, I have one more item that might be good for you to include, and that is to hard code the Terms of Use and Privay Policy pages as static HTML with static links to resolve the issues with spiders grabbing the content multiple times.

Comment By Tom Kraak on Monday, July 09, 2007 at 1:37 PM

Thanks Mitchel, very good point, which goes along with # 10.

Comment By Dave Bush on Wednesday, August 01, 2007 at 5:45 PM

The rel=nofollow tag is the best way to deal with the login page, terms of service, etc.

It doesn't mean they won't get indexed, but they won't count even if they do.

The other thing you could do is javascript the links in. Both nofollow and javascript are generic solutions that allow the skin to be used on multiple portals.

Comment By Tom Kraak on Wednesday, August 01, 2007 at 5:56 PM

Thanks Dave. I'm not a friend of your rel=nofollow approach.

The core team did javascript the register and login links starting with 4.5.3 I believe (correct me if I'm wrong.)

And the terms and privacy links are now "home tab based" no matter what page you are on. Well done.

Comment By John Studdard on Tuesday, August 28, 2007 at 12:06 PM

Great article, very helpfull. Thanks for taking the time.

Comment By Tom Kraak on Tuesday, August 28, 2007 at 4:59 PM

Thanks John, I'm glad you found it helpful.

Comment By xcentric on Saturday, September 08, 2007 at 3:56 PM

Hi Tom,
Can you recommend a menu that will closely duplicate solpart's look and feel (dynamic). I am looking at the snapsis CSS Nav Menu solution. Or something better.

Comment By Tom Kraak on Saturday, September 08, 2007 at 5:47 PM

I can't comment on Snapsis' CSS Nav Menu since we have not used it.

We like Telerik's menu around here and use it for most of our cusotm skins. It's feature-rich, emits clean code, and is very SEO friendly.

See http://dnn.telerik.com.

Comment By Boris on Tuesday, October 16, 2007 at 9:13 AM

wow thanks for sharing this!

Comment By Tom Kraak on Tuesday, October 16, 2007 at 9:19 AM

You are very welcome Boris ... thanks for stopping by.

Comment By Website Marketing on Monday, October 29, 2007 at 4:03 PM

Thanks for the information. It really has a wealth of information for me to sift through and absorb.

Comment By Tom Kraak on Monday, October 29, 2007 at 7:45 PM

Feel free to ask questions as you go thru the post.

Comment By David on Tuesday, March 18, 2008 at 2:44 PM

We were using an seo friendly menu but when we analyzed the pages, the menu caused each page to have 150 to 200 links per page. We went back to the old javascript menus because of this. I'm not quite sure if that was the best idea but I don't want the search engines to consider the site a link farm as it is for a non-profit.

Comment By Tom Kraak on Tuesday, March 18, 2008 at 2:50 PM

David - what particular "seo friendly menu" menu were you using if I may ask?

Comment By Dave Green on Thursday, April 17, 2008 at 11:07 AM

Great article, thanks! I have a quick question that I'm sure I should know the answer to but...

I can't seem to figure out how to turn off the linkclick stuff. How do I make the editor not track the link and therefore write the full path to the page instead of the linkclick.asp.

Comment By Mitchel Sellers on Thursday, April 17, 2008 at 11:27 AM

Dave,

To remove the link click portion of the URL in a location that uses the URL control you must be sure that NONE of the tracking options are selected and that the file isn't in a secured folder.

DO you have a specific module you are concerned about?

Comment By Tom Kraak on Thursday, April 17, 2008 at 11:27 AM

Thanks Dave.

You can't turn "linkclick" off. What you can and should do is type or paste in the URL "manually" instead of using the editor to browse to the page. Not as convenient, but worth the effort in favor of SEO.

Comment By Dave Green on Thursday, May 15, 2008 at 5:09 PM

Thanks for the help guys. I don't have a specific module in mind. I know how to prevent it when using the links module, but I'm using the included FCKEditor and I can't keep it from linking through the linkclick.aspx.

Tom, your suggestion about pasting in the correct url works for me, but I'm prettty sure my client's not going to like that answer...

Thanks again!

Comment By Tom Kraak on Thursday, May 15, 2008 at 6:45 PM

Dave - you may want to follow the "Minimize Duplicate Content by Avoiding DNN's LinkClick.aspx" post ... maybe we can figure out the editor :)-

Comment By Ken Florian on Friday, May 23, 2008 at 3:51 PM

How / where does one hard-code a link into a DNN skin?

Comment By Tom Kraak on Friday, May 23, 2008 at 3:57 PM

Ken - just open your skin.ascx and place your link into the appropriate section.

Add a comment
Add to Technorati Favorites

Email Updates

Enter your email address below and find our blog updates in your inbox.