Products

Evoq Content Overview Content Creation Workflow Asset Management Mobile Responsive Personalization Content Analytics SEO Integrations Security Website PerformanceEvoq Engage Overview Community Management  Dashboard  Analytics  Member Profile Gamification Advocate Marketing Community Engagement  Ideas  Answers  Discussions  Groups  Wikis  Events Mobile ReadyDNN Support PackagesEvoq: CMS FeaturesEvoq OnDemandCompare DNN's CMS Products

Solutions

Content Management SystemMulti-Channel PublishingDigital MarketingOnline Community ManagementIntranet Software SolutionOur CustomersPrime

Resources

Test DrivesSchedule A DemoDocumentation CenterWebinarsWhite PapersProduct ManualsRequest PricingData SheetsCase StudiesEvoq Preferred Products Content Management Ecommerce Forms Identity Management and Authentication Site Management Social Themes

Partners

DNN Partners Partner Directory Become a DNN Partner Partner Program Overview  Hosting  Implementation  ISV  Training  Competencies

Community

Participate Ask a Question Forums Community Showcase DNN MVP  Program Overview  Lifetime MVPs  Honorary MVPs Subscribe to DNN Digest Advisory Groups  Awareness Advisory Group  Developer Advisory Group  Partner Advisory Group  Technology Advisory GroupLearn Documentation Wiki Community Blog Video Library Project History Development RoadmapDownload DNN Store Language Packs Manuals Nightly BuildsSecurity Policies Security Center

Blog

About

News Press Releases News Coverage Press KitCareersContact DNN

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
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Search Engine Frirndly ViewstateSearch Engine Frirndly Viewstate
Previous
 
Next
New Post
3/6/2008 7:32 PM
 
Tareq Mahmud


www.fowara.com
Joined: 12/16/2007
Posts: 210

According to this book Professional Search Engine Optimization with ASP.NET: A Developer's Guide to SEO
by Cristian Darie, Jaimie Sirovich viewstate position does matter. There is no evidence to proof. Well known sites such as dnn, asp.net, ms are all very well know sites with thousands of visitors every hour. They are bound to be indexed by Google constantly. I belive the viewstate positioning is big help to new sites or sites that are not popular yet. I helps getting ranks faster. It  may not make any difference for dnn or asp.net. I don't think upgrading to 4.8 will lower ranking unless the page structure, keyword for the pages have changed. But I am no guru and that is just my opinion.

There are many factors for ranking. One factor is how fast the page loads and how fast a robot can crawl thru the page. Having viewstate on the top could increase time for robots crawling. Some says it may stop indexing a page. Ofcourse that will not aafect the well known sites.

I think for small sites and new sites viewstate at bottom is a big help and hope the DNN developers will take that into consideration for small site like mine.

Tareq Mahmud
Fowara
 
New Post
3/6/2008 11:27 PM
 
odove


Joined: 3/21/2004
Posts: 111

Joe Brinkman wrote

There are lots of items which affect search engine ranking.  In fact when we researched this issue prior to 4.8 we could not find a single Asp.Net app other than DNN that moved viewstate.  Nor could we find any documentation that showed that the position of viewstate impacts SEO.  Given that sites like PageFlakes, ASP.Net, MSDN, MySpace and many others don't alter viewstate, then what evidence is there that viewstate has any impact whatsoever?  For every site whose page rank dropped after upgrading to 4.8, I can show you another site where pagerank was unnaffected (including DotNetNuke.com).

When I said my site's search engine ranking dropped I was talking about key words placement on search engines, NOT google pagerank. My site's google pagerank stays the same. And I don't care about that google pagerank.

I do not want to explain much about SEO here. The interesting thing is when I realized this issue I never thought about checking sites like asp.net or msdn.com. I checked some other sites instead, the sites that are striving to succeed and they are big as well. Obviously lots of them realized this is an issue and they did something to avoid the negative effects.

I understand it might not be easy to  make a balance between the performance and SEO. It might be nice for dnn users to have an option as to whether it should be on top or bottom?

 
 
New Post
3/7/2008 9:25 AM
 
Joe Brinkman


Joe Brinkman's Avatar

blog.theaccidentalgeek.com
Joined: 5/18/2003
Posts: 2356

Everything we do is a balancing act.  When discussing performance issues with Microsoft, they pointed out that moving the viewstate using our code had serious performance impacts.  After getting this feedback and researching the issue, we found that most of the advocates for moving viewstate pointed to articles that based their conclusion on the fact that DotNetNuke moved viewstate.  This becomes a catch 22.  Viewstate should be moved because some SEO guru says you should move viewstate based on the fact that DotNetNuke moves the viewstate.

So, rather than going around in an endless loop, lets try something different.  Go to the Host settings page.  Scroll down to the Performance Settings and change Page State Persistence from Page to Memory.  Now we are left with this dainty little viewstate code at the top of our page:

<input type="hidden" name="__VIEWSTATE_CACHEKEY" id="__VIEWSTATE_CACHEKEY" value="VS_keosrs45tdwuow55zem0hk25_633404779931050000" />
<input type="hidden" name="__VIEWSTATE" id="__VIEWSTATE" value="" />

So now we get a twofer - no viewstate block at the top of the page and we have a much smaller page payload.  Our pages load faster and we can stop arguing over unprovable facts about the dark arts of SEO.

Joe Brinkman
DNN Corp.
 
New Post
3/7/2008 9:59 AM
 
Bradley Molzen

www.vinocellar.com
Joined: 9/29/2003
Posts: 59

Joe Brinkman wrote

Everything we do is a balancing act.  When discussing performance issues with Microsoft, they pointed out that moving the viewstate using our code had serious performance impacts.  After getting this feedback and researching the issue, we found that most of the advocates for moving viewstate pointed to articles that based their conclusion on the fact that DotNetNuke moved viewstate.  This becomes a catch 22.  Viewstate should be moved because some SEO guru says you should move viewstate based on the fact that DotNetNuke moves the viewstate.

So, rather than going around in an endless loop, lets try something different.  Go to the Host settings page.  Scroll down to the Performance Settings and change Page State Persistence from Page to Memory.  Now we are left with this dainty little viewstate code at the top of our page:




So now we get a twofer - no viewstate block at the top of the page and we have a much smaller page payload.  Our pages load faster and we can stop arguing over unprovable facts about the dark arts of SEO.

Wow... great information like this would do very well in a Wiki or some other "Tips and Tricks" page...  Is there one and I just don't know it?

Thanks for the Info Joe about exactly what that option does.  I hadn't realized. 
 
New Post
3/7/2008 11:21 AM
 
Mitchel Sellers


Mitchel Sellers's Avatar

Mitchel Sellers's Avatar

Mitchel Sellers's Avatar

Mitchel Sellers's Avatar

Mitchel Sellers's Avatar

Mitchel Sellers's Avatar

www.mitchelsellers.com
Joined: 1/24/2007
Posts: 7846

Joe Brinkman wrote

Everything we do is a balancing act.  When discussing performance issues with Microsoft, they pointed out that moving the viewstate using our code had serious performance impacts.  After getting this feedback and researching the issue, we found that most of the advocates for moving viewstate pointed to articles that based their conclusion on the fact that DotNetNuke moved viewstate.  This becomes a catch 22.  Viewstate should be moved because some SEO guru says you should move viewstate based on the fact that DotNetNuke moves the viewstate.

So, rather than going around in an endless loop, lets try something different.  Go to the Host settings page.  Scroll down to the Performance Settings and change Page State Persistence from Page to Memory.  Now we are left with this dainty little viewstate code at the top of our page:




So now we get a twofer - no viewstate block at the top of the page and we have a much smaller page payload.  Our pages load faster and we can stop arguing over unprovable facts about the dark arts of SEO.

Joe,

I think a VERY strong word of caution is needed with this setting.  There have been MANY reports in the past of issues with this setting and various modules.  I have yet to have a site that I can safely use this configuration option on.

Just my $0.02 anyway.

-Mitchel Sellers
Microsoft MVP, ASPInsider, DNN MVP
CEO/Director of Development - IowaComputerGurus Inc.
LinkedIn Profile

Visit mitchelsellers.com for my mostly DNN Blog and support forum.

Visit IowaComputerGurus.com for free DNN Modules, DNN Performance Tips, DNN Consulting Quotes, and DNN Technical Support Services
 
 Page 2 of 2
Previous12 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Search Engine Frirndly ViewstateSearch Engine Frirndly Viewstate


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