Hi Ian, Are you talking about using Ajaxcrawling ( http://code.google.com/web/ajaxcrawling) or some other way ?. Can you give details on what are you doing for this or any link which will provide details ?
- Abdullah On Fri, Apr 2, 2010 at 9:36 PM, Ian Bambury <ianbamb...@gmail.com> wrote: > Have to disagree with you, Sri. > > It is simple to create SEO-friendly content-driven web sites with GWT used > just for navigation and history. There is no need for a recompile if content > changes. I'm working on one like that right now. > > If you design it properly, then you don't even need to recompile to add > pages to your GWT-driven menu system and without too much trouble, you can > even have an SE-friendly site with the information held in a database. > > Ian > > http://examples.roughian.com > > > > On 2 April 2010 16:19, Sripathi Krishnan <sripathikrish...@gmail.com>wrote: > >> Entire website in GWT, yes/no ? >>> >> I would say no. >> >> There are two types of websites - >> >> - *Content driven* - which share information. Think blogs, corporate >> websites, forums etc. SEO is usually important. And content is almost >> always >> delivered over http. >> - *Interaction driven* - in which the user and site interact closely, >> typically involving ajax. Think web apps like gmail, google docs, >> facebook. >> Here, the content is usually specific to a user, and is typically >> delivered >> after login. So, you'd want https, and wouldn't care much about SEO. >> >> You can build both kinds of websites with GWT, but it really is suited for >> the interactive web-apps. For content-driven websites, GWT is an overkill. >> You have to do a lot of extra work to make it SEO friendly. Modifying >> content will require a re-build, which gets bugging after a point. There are >> ways to get around these limitations, but its just not worth it. >> >> I would recommend you split your website into two parts along the above >> lines. For the website portion, use whatever technology you are familiar >> with, make it SEO friendly, and deliver it over http. For the interactive >> portion, use GWT. That way, you get best of both worlds. >> >> --Sri >> >> >> >> >> On 2 April 2010 19:29, Katharina Probst <kpro...@google.com> wrote: >> >>> Hi Abdullah, >>> >>> to make your app searchable, you may also want to consider looking at >>> http://code.google.com/web/ajaxcrawling. (Note that this only works for >>> Google right now). >>> >>> kathrin >>> >>> >>> >>> >>> On Fri, Apr 2, 2010 at 3:56 AM, Abdullah Shaikh < >>> abdullah.shaik...@gmail.com> wrote: >>> >>>> Hi All, >>>> >>>> I am planning to have my entire website in GWT, but there a few issues, >>>> for which I would like to have your suggestions on. >>>> >>>> 1) The site should be searchable (SEO) >>>> >>>> 2) I would need to switch between Http/Https depending on the input I >>>> will be taking from the user >>>> >>>> Any idea how to achieve this ? >>>> >>>> >>>> The other thing I have in mind is, I go with plain html approach, that >>>> is use jsp/ftl, put the content there, and have the gwt application in the >>>> same jsp/ftl file and fetch the data using DOM to display it in GWT UI, >>>> this >>>> way the content will be searchable. >>>> >>>> Is the above approach good or is there any issues with ? also I would >>>> need to have multiple gwt applications using this approach for each & every >>>> page where I need got user interactivity & UI. >>>> >>>> Thanks for any help. >>>> >>>> - Abdullah >>>> >>>> -- >>>> You received this message because you are subscribed to the Google >>>> Groups "Google Web Toolkit" group. >>>> To post to this group, send email to >>>> google-web-tool...@googlegroups.com. >>>> To unsubscribe from this group, send email to >>>> google-web-toolkit+unsubscr...@googlegroups.com<google-web-toolkit%2bunsubscr...@googlegroups.com> >>>> . >>>> For more options, visit this group at >>>> http://groups.google.com/group/google-web-toolkit?hl=en. >>>> >>> >>> -- >>> You received this message because you are subscribed to the Google Groups >>> "Google Web Toolkit" group. >>> To post to this group, send email to google-web-toolkit@googlegroups.com >>> . >>> To unsubscribe from this group, send email to >>> google-web-toolkit+unsubscr...@googlegroups.com<google-web-toolkit%2bunsubscr...@googlegroups.com> >>> . >>> For more options, visit this group at >>> http://groups.google.com/group/google-web-toolkit?hl=en. >>> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Google Web Toolkit" group. >> To post to this group, send email to google-web-tool...@googlegroups.com. >> To unsubscribe from this group, send email to >> google-web-toolkit+unsubscr...@googlegroups.com<google-web-toolkit%2bunsubscr...@googlegroups.com> >> . >> For more options, visit this group at >> http://groups.google.com/group/google-web-toolkit?hl=en. >> > > -- > You received this message because you are subscribed to the Google Groups > "Google Web Toolkit" group. > To post to this group, send email to google-web-tool...@googlegroups.com. > To unsubscribe from this group, send email to > google-web-toolkit+unsubscr...@googlegroups.com<google-web-toolkit%2bunsubscr...@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/google-web-toolkit?hl=en. > -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
