hi,
as radDataPager claim to SEO Paging but this make a huge problem on navigating link.
For example see this Demo and go to page 8 [last page in demo] then next link button create link to next page [defaultcs.aspx?RadListView1=9],this link has onclick="return false;" but link is a canonical link and Google known it as a Crawl Errors.
is there a solution to prevent create this link only in server side?
Thanks
as radDataPager claim to SEO Paging but this make a huge problem on navigating link.
For example see this Demo and go to page 8 [last page in demo] then next link button create link to next page [defaultcs.aspx?RadListView1=9],this link has onclick="return false;" but link is a canonical link and Google known it as a Crawl Errors.
is there a solution to prevent create this link only in server side?
Thanks
6 Answers, 1 is accepted
0
Hello Hasan,
I will ask our developers to examine this case. I will let you know when I have any information about this.
Regards,
Daniel
Telerik
I will ask our developers to examine this case. I will let you know when I have any information about this.
Regards,
Daniel
Telerik
Check out the Telerik Platform - the only platform that combines a rich set of UI tools with powerful cloud services to develop web, hybrid and native mobile apps.
0
Hasan
Top achievements
Rank 1
Rank 1
answered on 28 Jul 2014, 08:24 AM
Hello Daniel,
There is no incertitude,this is a Bug.I waiting for fixing this problem because this is a important problem for seo.
Thanks
There is no incertitude,this is a Bug.I waiting for fixing this problem because this is a important problem for seo.
Thanks
0
Hello Hasan,
The aforementioned demo has 8 pages in total (provided that the default page size of 10 has not been changed) so if you go to the 8th page, the next and last page buttons should not be working nor crawled because the current page (8) is the last page available.
So, according to Google (Google Search Appliance: Administering Crawl > Advanced Topics), links containing onclick='return false' won't be crawled at all.
Nevertheless, I contacted our developers and they told me they are going to introduce a property to enable the hyperlink buttons to render a sharp sign for the url instead of return false. This is needed to avoid any breaking changes.
Regards,
Daniel
Telerik
The aforementioned demo has 8 pages in total (provided that the default page size of 10 has not been changed) so if you go to the 8th page, the next and last page buttons should not be working nor crawled because the current page (8) is the last page available.
So, according to Google (Google Search Appliance: Administering Crawl > Advanced Topics), links containing onclick='return false' won't be crawled at all.
Nevertheless, I contacted our developers and they told me they are going to introduce a property to enable the hyperlink buttons to render a sharp sign for the url instead of return false. This is needed to avoid any breaking changes.
Regards,
Daniel
Telerik
Check out the Telerik Platform - the only platform that combines a rich set of UI tools with powerful cloud services to develop web, hybrid and native mobile apps.
0
Hello Hasan,
This is to inform you that this feature request has been approved and will be available in the next official release - Q3 2014.
Regards,
Daniel
Telerik
This is to inform you that this feature request has been approved and will be available in the next official release - Q3 2014.
Regards,
Daniel
Telerik
Check out the Telerik Platform - the only platform that combines a rich set of UI tools with powerful cloud services to develop web, hybrid and native mobile apps.
0
Hasan
Top achievements
Rank 1
Rank 1
answered on 02 Aug 2014, 07:37 AM
Hello Daniel,
As This Post:
[quote]Daniel said:Hello Hasan,
The aforementioned demo has 8 pages in total (provided that the default page size of 10 has not been changed) so if you go to the 8th page, the next and last page buttons should not be working nor crawled because the current page (8) is the last page available.
So, according to Google (Google Search Appliance: Administering Crawl > Advanced Topics), links containing onclick='return false' won't be crawled at all.
Nevertheless, I contacted our developers and they told me they are going to introduce a property to enable the hyperlink buttons to render a sharp sign for the url instead of return false. This is needed to avoid any breaking changes.
Regards,
Daniel
Telerik
[/quote]
please see 2 attached pic from my webmaster,I use datapager with routing [routing segment is Page] and number of item is 12.
I see another problem with datapager when use routing with default Page size and going to end page when change Page size to larger number,first page shown in browser even pager show first page but address show last page [address and pager not equal].
for example in mentioned Demo with Page size: 10 go to last page [page 8] and now change Page size to 50 after response you seen first page in pager and top 50 first record but address is:
demos.telerik.com/aspnet-ajax/datapager/examples/raddatapagerseopaging/defaultcs.aspx?RadListView1=8_50
As This Post:
[quote]Daniel said:Hello Hasan,
The aforementioned demo has 8 pages in total (provided that the default page size of 10 has not been changed) so if you go to the 8th page, the next and last page buttons should not be working nor crawled because the current page (8) is the last page available.
So, according to Google (Google Search Appliance: Administering Crawl > Advanced Topics), links containing onclick='return false' won't be crawled at all.
Nevertheless, I contacted our developers and they told me they are going to introduce a property to enable the hyperlink buttons to render a sharp sign for the url instead of return false. This is needed to avoid any breaking changes.
Regards,
Daniel
Telerik
Check out the Telerik Platform - the only platform that combines a rich set of UI tools with powerful cloud services to develop web, hybrid and native mobile apps.
please see 2 attached pic from my webmaster,I use datapager with routing [routing segment is Page] and number of item is 12.
I see another problem with datapager when use routing with default Page size and going to end page when change Page size to larger number,first page shown in browser even pager show first page but address show last page [address and pager not equal].
for example in mentioned Demo with Page size: 10 go to last page [page 8] and now change Page size to 50 after response you seen first page in pager and top 50 first record but address is:
demos.telerik.com/aspnet-ajax/datapager/examples/raddatapagerseopaging/defaultcs.aspx?RadListView1=8_50
0
Hello Hasan,
The problem with the return false and the non-existing URL's has been addressed by introducing a new property which allows you to change this behavior. This functionality will be available in the next official release.
As to the second problem, I have notified our developers about it. I will let you know when I have any information about that.
Regards,
Daniel
Telerik
The problem with the return false and the non-existing URL's has been addressed by introducing a new property which allows you to change this behavior. This functionality will be available in the next official release.
As to the second problem, I have notified our developers about it. I will let you know when I have any information about that.
Regards,
Daniel
Telerik
Check out the Telerik Platform - the only platform that combines a rich set of UI tools with powerful cloud services to develop web, hybrid and native mobile apps.