First time here? You may want to check out the blog archive, subscribe to the RSS feed, sign up for free email updates, or follow me on Twitter. Thanks for visiting!

DNN SEO Quickstart Guide 

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.

    Update: Url Master has overcome the majority of the limitations mentioned above and is now the de facto standart for DNN Url rewriting.
  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.




Comments

Mitchel Sellers Mitchel Sellers says:

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.

Tom Kraak Tom Kraak says:

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

Dave Bush Dave Bush says:

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.

Tom Kraak Tom Kraak says:

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.

John Studdard John Studdard says:

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

Tom Kraak Tom Kraak says:

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

xcentric xcentric says:

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.

Tom Kraak Tom Kraak says:

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.

Boris Boris says:

wow thanks for sharing this!

Tom Kraak Tom Kraak says:

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

Website Marketing Website Marketing says:

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

Tom Kraak Tom Kraak says:

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

David David says:

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.

Tom Kraak Tom Kraak says:

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

Dave Green Dave Green says:

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.

Mitchel Sellers Mitchel Sellers says:

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?

Tom Kraak Tom Kraak says:

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.

Dave Green Dave Green says:

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!

Tom Kraak Tom Kraak says:

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

Ken Florian Ken Florian says:

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

Tom Kraak Tom Kraak says:

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

MJ MJ says:

I have few tabs on my website menu that are forwarded to hidden pages using DNN link to external source (the reason whay I did that since I wanted the tab to look diffrent from the address of the page) would that affect the ranking of these pages?

Tom Kraak Tom Kraak says:

MJ - as long as it's a well-formed link (no JavaScript, no tricky redirects) it will be fine. Can I take a look at your site?

MJ MJ says:

Tom - Thank you, I also have a lot of tabs on my website menu and links that are forwarded to pages using link to"page on your site" (no JavaScript, no tricky redirects), is this safe for SEO. Also what is better to use underscores or dashes to seperate the words in the page address?

Tom Kraak Tom Kraak says:

I recommend dashes, and dashes only, to separate words in Urls.

MJ MJ says:

Tom, have you looked at the website, what do you think about using links.
One more think I am looking to use Ifinity Url Master, is it a good module?

SEO SEO says:

Wow Great, very helpfull article.

Thank you

Sona Sona says:

Hi Tom
Really liked your site. Could you tell us what is the skin and menu that you have used in this site

Thanks
Sona

Tom Kraak Tom Kraak says:

Thanks Sona.

The main menu is driven by Telerik, see dnn.telerik.com.

And the skin and all module templates were developed in-house by Vasilis Terzopoulos of thinkofdesign.com.

Let me know if you have further questions.

Sona Sona says:

Wow the Telerik menu sure looks expensive. Its part of the package of controls and it costs $1299.
Thats pretty steep for a menu.
:(

Tom Kraak Tom Kraak says:

As far as I can see it's $799 for the RadControls for ASP.NET AJAX Developer License without source. That includes a number of controls, not just the menu.

Sona Sona says:

Hi Tom
What is your opinion about about House of Nuke menu v/s Snapsis CSS Navigation Menu

Thanks
Sona

Tom Kraak Tom Kraak says:

Sona - SEO-wise, both menus are excellent solutions.

However, overall, the Snapsis Nav menu is much more flexible and feature-rich than House of Nuke.

Stan Kitson Stan Kitson says:

Great article Tom. I appreciate the way you prioritized your points. Sometimes it gets muddled as to what is most important.

You mentioned DNNMasters and Ifinity Url Master. In your opinion, are they about the same when it comes to creating better formed URLs?

Tom Kraak Tom Kraak says:

Thanks Stan. I mentioned DNNMasters? Where?

In my opinion, iFinity Url Master is far superior to DNNMasters SEO Pack.

David Pavlicko David Pavlicko says:

You can also avoid the duplicate content issues by excluding linkclick in your robots.txt file. Also, I agree that the iFinitity Url Master is much better than the DNNMasters, except for the fact that it doesn't allow a 404 page - non-existent or dead pages get 301 redirected to another page on your site (usually the home page) that return a status code of 200.

This could create serious issues over time, as many search engine spiders generate bogus urls when scanning a site. If you're using that module, make sure you've got an xml sitemap up for your site.

Mitchel Sellers Mitchel Sellers says:

David,

For what it is worth, current versions of UrlMaster give you the option for 404 OR a redirect.

Tom Kraak Tom Kraak says:

Mitch is correct. So now you could Url Master's 404 option and then show a "friendly" 404 page via asp.net or IIS.

Dee Dee says:

Tom - thanks for a great article. I just downloaded your "Cheat Sheet" from the Capitol UG presentation in Feb. Thanks for all the previous posts about menus and link formation as well. I try to keep up with you on Twitter as much as possible.

Tom Kraak Tom Kraak says:

@ Dee - Thanks for stopping by, I'm glad you find our resources useful. Feel free to ask questions in the comments of any blog post.

Lav Lav says:

Thank you for a very useful article. We were looking for an SEO module to re-write our DNN URLS, and we'll definitely give URL Master a shot.

Tom Kraak Tom Kraak says:

Thanks Lav. Let me know if you have any Url Master installation / configuration questions.

alan alan says:

Good article, thanks. A couple of questions/comments:

1) We ran into trouble with URL Master crashing with the Content Rotator Module so ended up using DNNMasters'. Had some trouble with that properly rewriting our Ventrian News Articles, but Chris created an add on that works nicely.

2) For those of us still on 4.9.4, is there a way to look at all of the pages in a table format at one time so we can see what page title, keywords etc are being used. I think it would help to have a global view of that.

Tom Kraak Tom Kraak says:

@ Alan

1. I'll pass that on to Bruce Chapman, author of Url Master.

2. There is nothing build into DNN for that, but you could use the reports module or similar and write a fairly simple SQL statement to pull page titles, keywords etc out of the database.

alan alan says:

Thanks Tom. I appreciate that.

I'm a user, maybe even a power user. I was able to install RM and add it to a page, but report writers have always given me a fit.

I don't see any Step by step guide to DNN RM. Is there a resource you'd suggest for "a fairly simple SQL statement to pull page titles, keywords etc out of the database. "

Eric Eric says:

This is helpful. One of the SEO issues with our site is that DNN is that it has created a www.oursite.com; www.oursite.com/home.aspx, www.oursite.com/default.aspx...how do I fix it?

Tom Kraak Tom Kraak says:

Thanks Eric. There is a number of things you can do to "canonicalize" your home. Are you on shared hosting or do you have control over your web server and IIS?

Eric Eric says:

Thanks. We have control over the web server.

Eric Eric says:

We corrected the http://www.oursite.com vs. http://oursite.com --- but I haven't figured out /home.aspx and /default.aspx

Tom Kraak Tom Kraak says:

What approach did you use to redirect non-www to www or vice versa?

Eric Eric says:

sorry for the late reply, we used a 301 redirect. Would blocking those directories with robots.txt be appropriate you think?

Tom Kraak Tom Kraak says:

301 is the way to go, but I meant did you implement the redirect on the IIS level or DNN / module level?

Eric Eric says:

Honestly, I didn't do the redirect personally, our head developer did, I'll try to ask him when I get a chance.

I'm just the SEO/PPC guy crying over a redesign (that was already in place as I started my this job) that saw us drop page rank 5 to 4, lose our site links, and our indented listing. I'm trying to make recommendations to the developers to clean up the mess, but I had never heard of DNN until I started this job a few months ago, and doing my best to get up to speed.

Tom Kraak Tom Kraak says:

So your devs should be able to 301 redirect /home.aspx and /default.aspx to / the same way.

But you might run into issues when working in DNN admin mode as DNN sometimes looks for default.aspx.

Personally I think that Google and other major SE have gotten smart enough and "know" by now that /home.aspx and /default.aspx and / are the same page.

Name (required)

Email (will not be published) (required)

Website

Enter the code shown above in the box below

Subscribe to our Feeds Follow on Twitter