Log In
Home
Support
Demos
Documentation
Blogs
Training
Webinars
[Expand]General Information
[Expand]WinForms Controls
[Collapse]ASP.NET Controls and MVC Extensions
 [Expand]Prerequisites
 [Expand]What's Installed
 [Expand]Common Concepts
 [Expand]ASP.NET WebForms Controls
 [Collapse]ASP.NET MVC Extensions
  [Expand]Product Information
  [Expand]Getting Started
  [Expand]Common Concepts
  [Expand]Grid View
  [Expand]Tree List
  [Collapse]Card View
    Overview - CardView
    Main Features - Card View
   [Collapse]Concepts
    [Expand]Binding to Data
    [Expand]Data Representation Basics
    [Collapse]Focus and Navigation
      Focused Card
     [Collapse]Paging and Scrolling
       Data Paging
       Endless Paging
       SEO Paging
       Vertical Scrolling
      Selection
    [Expand]Data Editing and Validation
     Adaptivity
    [Expand]Export
   [Expand]Member Tables
  [Expand]Reporting
  [Expand]Charting
  [Expand]Pivot Grid
  [Expand]Spreadsheet
  [Expand]Rich Text Editor
  [Expand]Scheduler
  [Expand]Site Navigation and Layout
  [Expand]HTML Editor
  [Expand]Vertical Grid
  [Expand]Data Editors Extensions
  [Expand]Docking and Popups
  [Expand]File Management
  [Expand]Data and Image Navigation
  [Expand]Multi-Use Site Extensions
  [Expand]SpellChecker
  [Expand]Query Builder
 [Expand]Localization
 [Expand]Redistribution and Deployment
  Get More Help
 [Expand]API Reference
[Expand]ASP.NET Bootstrap Controls
[Expand]ASP.NET Core Bootstrap Controls
[Expand]WPF Controls
[Expand]Xamarin Controls
[Expand]Windows 10 App Controls
[Expand]Office File API
[Expand]Reporting
[Expand]Report and Dashboard Server
[Expand]Dashboard
[Expand]eXpressApp Framework
[Expand]CodeRush
[Expand]CodeRush Classic
[Expand]Cross-Platform Core Libraries
[Expand]Tools and Utilities
 End-User Documentation

SEO Paging

A known problem with grid-like components is that search engines simply ignore pagers. When indexing a site, they only use the information contained on the first page. The reason for this is that pager links are usually not represented as hyperlinks to other pages. Instead, they simply respond to click events to raise data update callbacks.

The CardView allows you to make a SEO-friendly pager. Use the ASPxGridPagerSettings.SEOFriendly property for this purpose.

If this property is set to SEOFriendlyMode.CrawlerOnly, the CardView renders hyperlinks in the pager when a web-crawler is detected. For other visitors, standard pager links are generated. Thus, search engines can index an entire CardView content, and site visitors experience the same callback functionality.

If the property is set to SEOFriendlyMode.Enabled or SEOFriendlyMode.Disabled, automatic web crawler detection is disabled. The pager renders either SEO-friendly or standard links respectively.

Note

If the ASPxGridPagerSettings.SEOFriendly property is set to SEOFriendlyMode.Enabled, each pager button link refers to a unique address. In this case, clicking a pager link does not post back to the same page, but generates a completely new request. As a result, a totally new page is created on the server, and information about the previous page state is lost. By design, in this mode, only sorting information applied to the CardView extension is preserved using specific request parameters. Other CardView states (such as applied filter criteria, column order, card selection, etc.) are not preserved. Thus, to keep the CardView's appearance consistent and content relevant for all pages, we recommend that you enable the SEO mode only for extensions that use minimum functional features, such as sorting.

Is this topic helpful?​​​​​​​