Go Back

Search-Engine Friendly Blog Post Paging

In the past, I've not liked that Javascript, ViewState and a full PostBack is required to page through the posts on this blog:

 Sitefinity Unfriendly Postback Navigation

The bots search engines use to “crawl” web sites have difficulty interacting with navigation that requires complex client-side behavior (Javascript, Flash, Silverlight, completing a form, etc).  Here is a quote from Google's Webmaster Central Blog:

Googlebot is great at following and understanding the structure of HTML links, [but] it can have a difficult time finding its way around sites which use JavaScript for navigation. While we are working to better understand JavaScript, your best bet for creating a site that's crawlable by Google and other search engines is to provide HTML links to your content.

Even aside from the search-engine concerns, navigating to page 2 simply should not require Javascript, Postbacks, ViewState, server-side events, etc, etc.  The same results could be accomplished with the following simple URL:

http://www.sitefinitywatch.com/blog.aspx?page=2

Using URL-based Sitefinity Blog Post Paging

Thankfully it's easy to change this behavior in Sitefinity.  Use the steps below to enable URL/querystring-based paging to Sitefinity's BlogPosts control.

1.  Within Sitefinity, locate and edit the page that contains the BlogPosts control. 

2.  Click Edit to modify the BlogPosts control.

3.  Click the Advanced tab to view additional BlogPosts control options.

Sitefinity Blog Post Control Designer

4. Expand the Paging options and change the RenderPageAsLink option to True.

Sitefinity Paging RenderPagerAsLink

5. Click I’m done to save these changes and then Publish the Sitefinity page.

That's it; you're done!  Refresh the page to see the new paging URLs in action.

Sitefinity URL Paging

Comments  2

  • Tony Archer 26 Mar

    Good info, thanks Gabe!
  • Tony Archer 04 Apr

    Excellent, Gabe! Just used it on a major project, thanks!
Post a comment!
  1. Formatting options
       
     
     
     
     
       
  2. I'm sorry for the CAPTCHA. You have spammers to thank for this: