On Tue, Sep 8, 2009 at 10:45 AM, Alexander Cherednichenko<lex...@gmail.com> wrote: > > I am not expert, though i have some recommendations. > > 1. Don't even try to generate _really_ different content for searchbot > and for the end-user. Sometimes googles sends request with 'normal' > user-agent, and if you have different content for users and bots, > you'll be banned (because of cloacking :) ) > Though, there are some ways to do so, > Though, not sure /me has enough time to work with google customer > support to clear this issue (if they have customer support, have never > heard of it:) ) > > 2. You may try create normal static application with unique URS, and > just wrap some page elements with javascript to provide rich > functionality. UIBinder is of new stuff. > > 3. You may try searhcing here (in this group) for such problems. > People resolve it in different ways. I've heard of interesting way - > generating html content by HTMLUnit and feeding it to the bot. Simply > - if your application sees it is a bot, it runs gwt (javascript) code > in headless browser on the serverside, and flushes momental DOM > snapshot to the response. > > 4. Look here - > http://lexaux.blogspot.com/2009/03/afraid-of-being-banned-by-google-for.html > I was going to make a little demo some time ago, but had no time to > complete it :( sorry. Though, there may still be some interesting > facts. @all: thanks for the ideas.
htmlunit is a really cool idea. however, i am not sure if it will fail with adsense and related concepts. so my solution is roughly like this: - generate regular html output - enrich / regroup html output via gwt so - there is no double content (i hope at least). google is happy, because parsing my page is really simple. and the user is happy - because he can use nice web 2.0 goodies. ok. this breaks some things of the gwt (i was hoping that i can forget almost everything about html and css and cross browser compatability issues), but it works. btw. in my opinion, google should run a 1sec htmlunit against my webpage, not me. but - ok takes way more CPU and the result is not predictable (what is this funny js generating? so somehow i can understand google. however - that puts gwt applications in the same bucket as flash applications - a bucket called "not properly indexed by google". thanks again, r > > On Sep 7, 12:04 pm, Raphael André Bauer > <raphael.andre.ba...@gmail.com> wrote: >> hey everybody, >> >> as every friendly web inhabitant i want that google knows my website >> and people that are interested in my stuff can find it easily. >> however, as my first experiments suggest the google bot does not even >> try to analyze (execute) gwt code (a working test of my concept is at >> [1]). >> >> this can -- on the one hand -- be explained by the very nature of gwt >> - it is javascript - much like an application that should not be >> indexed by a search bot by nature. but -- on the other hand -- hey! it >> is so simple. execute the js, see if it generates a more or less >> stable DOM, parse the dom and you are done. and both is from google? >> seems that the GWT hits the same indexing hell flash did. >> >> ok. maybe i am wrong here. in my opinion it is really bad news that >> GWT stuff is not at all analyzed by the google search bot. >> >> to come up with a conclusion would involve to sacrifice a lot of GWT >> coolness. mainly because i have to generate a lot of HTML myself that >> can be analyzed by search robots. i also wrote about that at [2]. it >> is especially interesting how [3] did "solve" the "problem". >> >> do the experts have any recommendations? >> >> thanks! >> >> ra! >> [1]http://scisurfer.com/news >> [2]http://blog.scisurfer.com/2009/09/gwt-and-seo-concerns.html >> [3]http://examples.roughian.com > > > --~--~---------~--~----~------------~-------~--~----~ 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 For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
