Andreas Lohr
Top achievements
Rank 1
Rank 1
Andreas Lohr
asked on 28 Sep 2006, 10:15 PM
Hi,
SEO becomes more and more important. I know that already the navigation controls (like radmenu) are search engine friendly. But why reduce it to that controls?
SEO is related to the whole website not only a part of it. The point that I want to show is:
Telerik takes a method or standard and declare it as important for all members of RadControls. The examples in the past were: standard compliance with XHTML. In the near past compliance with ATLAS.
What is now with SEO? It would be a great advantage for telerik to competition, if telerik would announce the first SEO-compliant ASP.NET control suite.
Or what do you think?
Best regards
Andreas
SEO becomes more and more important. I know that already the navigation controls (like radmenu) are search engine friendly. But why reduce it to that controls?
SEO is related to the whole website not only a part of it. The point that I want to show is:
Telerik takes a method or standard and declare it as important for all members of RadControls. The examples in the past were: standard compliance with XHTML. In the near past compliance with ATLAS.
What is now with SEO? It would be a great advantage for telerik to competition, if telerik would announce the first SEO-compliant ASP.NET control suite.
Or what do you think?
Best regards
Andreas
7 Answers, 1 is accepted
0
Hello Andreas,
All telerik navigational controls which render links support SEO. Even the controls' native AJAX mechanism (supported by r.a.d.grid, r.a.d.combobox, r.a.d.treeview, etc.), as well as r.a.d.ajax, automatically detects crawlers and search engines and provides traditional (non AJAX) output for them. A small modification has to be done to the Web.Config file, but everything works nicely. Our CMS Sitefinity can also be crawled and indexed by search engines.
I guess it is a good idea to provide a page on our site to describe SEO compliance in full.
As to the other controls which do not render links (editor, spell, window, upload, etc), we do not see how to make them search engine friendly. Actually, I am not sure that you talk about these anyway as SEO is not applicable here.
May be you mean r.a.d.grid, where the case is a little different. If you have paging, only the first page is indexed, rather than all. The reason behind this is that the grid shows its data in tables, and only one is sent to the client at a time. Still, there is a workaround - when the page is being crawled, the grid's paging has to be stopped so that it provides all of its data. This is a simple and intuitive solution.
Could you share which control(s) you have problems with? We will be happy to help you find the problem.
Greetings,
Rob
the telerik team
All telerik navigational controls which render links support SEO. Even the controls' native AJAX mechanism (supported by r.a.d.grid, r.a.d.combobox, r.a.d.treeview, etc.), as well as r.a.d.ajax, automatically detects crawlers and search engines and provides traditional (non AJAX) output for them. A small modification has to be done to the Web.Config file, but everything works nicely. Our CMS Sitefinity can also be crawled and indexed by search engines.
I guess it is a good idea to provide a page on our site to describe SEO compliance in full.
As to the other controls which do not render links (editor, spell, window, upload, etc), we do not see how to make them search engine friendly. Actually, I am not sure that you talk about these anyway as SEO is not applicable here.
May be you mean r.a.d.grid, where the case is a little different. If you have paging, only the first page is indexed, rather than all. The reason behind this is that the grid shows its data in tables, and only one is sent to the client at a time. Still, there is a workaround - when the page is being crawled, the grid's paging has to be stopped so that it provides all of its data. This is a simple and intuitive solution.
Could you share which control(s) you have problems with? We will be happy to help you find the problem.
Greetings,
Rob
the telerik team
0
Jurgen Van Landeghem
Top achievements
Rank 1
Rank 1
answered on 06 Nov 2006, 04:42 PM
this is very good news, but i don't see how rad.splitter could be SEO-friendly. It generates a lot of javascript and i think many crawlers will get very confused about this.
0
Hi Lorenzo,
the r.a.d.splitter control is using inline Javascript only for initialization purposes. It is not rendering the content in the panes using JS.
So until the content that is included in the panes is rendered using a simple and standards-compliant html - it will be indexed by the search engines.
Best wishes,
Valentin.Stoychev
the telerik team
the r.a.d.splitter control is using inline Javascript only for initialization purposes. It is not rendering the content in the panes using JS.
So until the content that is included in the panes is rendered using a simple and standards-compliant html - it will be indexed by the search engines.
Best wishes,
Valentin.Stoychev
the telerik team
0
tag2453
Top achievements
Rank 1
Rank 1
answered on 14 Nov 2006, 06:04 PM
Could you clarify exactly what type of SEO support is available for the paging links on the RadGrid?
I would like the links rendered as standard anchor tags with either a querystring parameter to identify the page or an seo url such as:
<a href="default.aspx?pg=1">Page 1</a>
or
<a href="default_pg1.aspx">Page 1</a>
Please verify if this is in fact supported and possibly provide a sample application. Also please verify that this is possible when using AJAX and scrolling on the grid as well.
I can't purchase the suite unless this is supported and doesn't require a lot of customization. Otherwise I will need to look to other controls such as: http://www.manuelabadia.com/products/PDS_features.aspx
I would like the links rendered as standard anchor tags with either a querystring parameter to identify the page or an seo url such as:
<a href="default.aspx?pg=1">Page 1</a>
or
<a href="default_pg1.aspx">Page 1</a>
Please verify if this is in fact supported and possibly provide a sample application. Also please verify that this is possible when using AJAX and scrolling on the grid as well.
I can't purchase the suite unless this is supported and doesn't require a lot of customization. Otherwise I will need to look to other controls such as: http://www.manuelabadia.com/products/PDS_features.aspx
0
Hi,
We are happy to inform you that in the upcoming service pack for the grid there will be built-in SEO Paging support. In case of crawler, the grid will turn off the paging automatically.
Sincerely yours,
Vlad
the telerik team
We are happy to inform you that in the upcoming service pack for the grid there will be built-in SEO Paging support. In case of crawler, the grid will turn off the paging automatically.
Sincerely yours,
Vlad
the telerik team
0
tag2453
Top achievements
Rank 1
Rank 1
answered on 15 Nov 2006, 08:48 PM
Please clarify because I'm not sure what you mean by "In case of crawler, the grid will turn off the paging automatically."
If you mean that when visitor is identified as a crawler that the grid will turn off the paging links and show ALL of the results then that is not an acceptable solution. If I have 100 pages of results and try to return all the results to the crawler then the page will likely time out. And even if it doesn't, most crawlers will only index about the first 100k of HTML.
This also doesn't solve the issue where a user might want to be able to bookmark a particular page in the results. Say page 12.
I hope you would consider creating a method to specify paging links as normal anchor tags with a user specified format regardless of the visitor type.
I.e. Grid1.PagerURLFormatString = "<a href='mypage.aspx?pg={0}'>Page {0}</a>"
If you mean that when visitor is identified as a crawler that the grid will turn off the paging links and show ALL of the results then that is not an acceptable solution. If I have 100 pages of results and try to return all the results to the crawler then the page will likely time out. And even if it doesn't, most crawlers will only index about the first 100k of HTML.
This also doesn't solve the issue where a user might want to be able to bookmark a particular page in the results. Say page 12.
I hope you would consider creating a method to specify paging links as normal anchor tags with a user specified format regardless of the visitor type.
I.e. Grid1.PagerURLFormatString = "<a href='mypage.aspx?pg={0}'>Page {0}</a>"
0
Hi,
Indeed you are right. Turning off paging will not be the best solution in some situations and that is why we will do our best to implement your or similar suggestion.
Don't hesitate to contact us if you have other questions.
Sincerely yours,
Vlad
the telerik team
Indeed you are right. Turning off paging will not be the best solution in some situations and that is why we will do our best to implement your or similar suggestion.
Don't hesitate to contact us if you have other questions.
Sincerely yours,
Vlad
the telerik team