The templates will support optimizations through server-side rendering, so that's certainly possible although not guaranteed based on which container you're on. Your best bet for server-side rendering is probably through the use of a new feature called proxied content, which fetches a <Content> section from your remote server, meaning you can deliver rendered app information without needing to build DOM through JavaScript. This feature is currently being developed, but it looks like it'll be available on orkut to test very soon. Make sure you're following the orkut developer blog and the opensocial api blog, as we'll announce in those places when we have more information about this feature.
~Arne On Oct 1, 4:59 am, fbjork <[EMAIL PROTECTED]> wrote: > Hi Arne, > > many thanks for the response. > > The main problem for us would be all the content rendered in the > gadgets is populated using DOM, after data is retrieved via > makeRequest() and thus not indexable by search engines. > > I read in the OS templates spec that server side rendering is planned, > could that solve the issue? > > regards, > > Fred > > On Sep 24, 1:04 am, [EMAIL PROTECTED] wrote: > > > Any gadget that's publicly viewable should be indexable by Google, > > which is smart enough to follow IFrame URLs. So any technique you'd > > use for an Ajax-heavy website should probably be applicable on a > > gadget as well, with the exception of requestNavigateTo() links (the > > crawler should be able to follow any links to your canvas view from > > the container, like the "view full application" link on orkut, if > > orkut allowed anonymous browsing). > > > The idea of URL templates to let your application construct URLs to > > different portions of the app (different views and owner contexts) was > > introduced in 0.8, but as far as I know, no containers have fully > > working implementations of this yet (if someone knows differently, > > please respond!). Eventually, you should be able to provide links > > with accurate href attributes that point to the correct place, so this > > hopefully won't be a problem in the future. > > > Hope this helps, > > ~Arne > > > On Sep 18, 6:51 am, fbjork <[EMAIL PROTECTED]> wrote: > > > > Hi, > > > > i was wondering if there's anyway to enable search engine indexing of > > > OpenSocial gadgets? > > > > Due to the highly dynamic and non-SEO friendly nature of gadgets, i.e > > > IFRAME and JavaScript dynamic pages I don't see how Google or other > > > search engines would be able to index a Profile page with multiple > > > IFRAMES that use gadgets.views.requestNavigateTo() properly. > > > > I'm working on a community that allows anonymous browsing and SEO is > > > important in this scenario. > > > > Anyone who's thought of this or who could provide me with some hacks/ > > > solutions to this? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "OpenSocial Application Development" group. To post to this group, send email to opensocial-api@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/opensocial-api?hl=en -~----------~----~----~----~------~----~------~--~---
