Re: Search engine indexing
Well that was easy, chears :) On Apr 7, 7:46 am, Vitali Lovich vlov...@gmail.com wrote: DOM.toString(RootPanel.get().getElement()) On Tue, Apr 7, 2009 at 1:45 AM, Darkflame darkfl...@gmail.com wrote: As a mater of interest semi-relivent to this, Is it possible to burn out GWT webpages into static html? (obviously losing interaction...just taking a snapshot of the current state of the dom and expressing the html nesscery to reproduce it). I mean, I guess you could cut and paste out of firebug, but is there a better method? On Apr 6, 5:35 pm, Jason Essington jason.essing...@gmail.com wrote: There are discussions about this (SEO) on this list, have a search for them. But basically, you'll want to embed the information you want indexed into your host pages. This is not a GWT limitation but rather a limitation of any web application that uses DOM modification to present content. -jason On Apr 6, 2009, at 9:29 AM, Prashant Gupta wrote: any alternative or solution to this ? On Mon, Apr 6, 2009 at 7:20 PM, djd alex.dobjans...@gmail.com wrote: Current crawl bots ignore flash and javascript. So if your web app is completely built in GWT (the default behavior when creating a project with projectCreator is to create a single HTML file with a single link to a .nocache.js files which is actually your entry point for entire app), all content will be discarded. On Apr 6, 4:11 pm, Prashant Gupta nextprash...@gmail.com wrote: does my GWT website gets indexed same as any other (non GWT) website..? --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: Search engine indexing
Current crawl bots ignore flash and javascript. So if your web app is completely built in GWT (the default behavior when creating a project with projectCreator is to create a single HTML file with a single link to a .nocache.js files which is actually your entry point for entire app), all content will be discarded. On Apr 6, 4:11 pm, Prashant Gupta nextprash...@gmail.com wrote: does my GWT website gets indexed same as any other (non GWT) website..? --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: Search engine indexing
any alternative or solution to this ? On Mon, Apr 6, 2009 at 7:20 PM, djd alex.dobjans...@gmail.com wrote: Current crawl bots ignore flash and javascript. So if your web app is completely built in GWT (the default behavior when creating a project with projectCreator is to create a single HTML file with a single link to a .nocache.js files which is actually your entry point for entire app), all content will be discarded. On Apr 6, 4:11 pm, Prashant Gupta nextprash...@gmail.com wrote: does my GWT website gets indexed same as any other (non GWT) website..? --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: Search engine indexing
There are discussions about this (SEO) on this list, have a search for them. But basically, you'll want to embed the information you want indexed into your host pages. This is not a GWT limitation but rather a limitation of any web application that uses DOM modification to present content. -jason On Apr 6, 2009, at 9:29 AM, Prashant Gupta wrote: any alternative or solution to this ? On Mon, Apr 6, 2009 at 7:20 PM, djd alex.dobjans...@gmail.com wrote: Current crawl bots ignore flash and javascript. So if your web app is completely built in GWT (the default behavior when creating a project with projectCreator is to create a single HTML file with a single link to a .nocache.js files which is actually your entry point for entire app), all content will be discarded. On Apr 6, 4:11 pm, Prashant Gupta nextprash...@gmail.com wrote: does my GWT website gets indexed same as any other (non GWT) website..? --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: Search engine indexing
As a mater of interest semi-relivent to this, Is it possible to burn out GWT webpages into static html? (obviously losing interaction...just taking a snapshot of the current state of the dom and expressing the html nesscery to reproduce it). I mean, I guess you could cut and paste out of firebug, but is there a better method? On Apr 6, 5:35 pm, Jason Essington jason.essing...@gmail.com wrote: There are discussions about this (SEO) on this list, have a search for them. But basically, you'll want to embed the information you want indexed into your host pages. This is not a GWT limitation but rather a limitation of any web application that uses DOM modification to present content. -jason On Apr 6, 2009, at 9:29 AM, Prashant Gupta wrote: any alternative or solution to this ? On Mon, Apr 6, 2009 at 7:20 PM, djd alex.dobjans...@gmail.com wrote: Current crawl bots ignore flash and javascript. So if your web app is completely built in GWT (the default behavior when creating a project with projectCreator is to create a single HTML file with a single link to a .nocache.js files which is actually your entry point for entire app), all content will be discarded. On Apr 6, 4:11 pm, Prashant Gupta nextprash...@gmail.com wrote: does my GWT website gets indexed same as any other (non GWT) website..? --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: Search engine indexing
DOM.toString(RootPanel.get().getElement()) On Tue, Apr 7, 2009 at 1:45 AM, Darkflame darkfl...@gmail.com wrote: As a mater of interest semi-relivent to this, Is it possible to burn out GWT webpages into static html? (obviously losing interaction...just taking a snapshot of the current state of the dom and expressing the html nesscery to reproduce it). I mean, I guess you could cut and paste out of firebug, but is there a better method? On Apr 6, 5:35 pm, Jason Essington jason.essing...@gmail.com wrote: There are discussions about this (SEO) on this list, have a search for them. But basically, you'll want to embed the information you want indexed into your host pages. This is not a GWT limitation but rather a limitation of any web application that uses DOM modification to present content. -jason On Apr 6, 2009, at 9:29 AM, Prashant Gupta wrote: any alternative or solution to this ? On Mon, Apr 6, 2009 at 7:20 PM, djd alex.dobjans...@gmail.com wrote: Current crawl bots ignore flash and javascript. So if your web app is completely built in GWT (the default behavior when creating a project with projectCreator is to create a single HTML file with a single link to a .nocache.js files which is actually your entry point for entire app), all content will be discarded. On Apr 6, 4:11 pm, Prashant Gupta nextprash...@gmail.com wrote: does my GWT website gets indexed same as any other (non GWT) website..? --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: Search Engine Indexing
In case it's any help to anyone, this is how I think I'll solve the
indexing problem.
My wife has a web site on which she sells various things, the
descriptions of which are stored in a database. I re-jigged her
website as a way to learn GWT. She was quite keen to have the GWT
version, but pretty peeved when I told her it would not be indexed by
Google, hence my desire to solve the indexing problem.
Currently, I have a cron job that re-creates a sitemap file each night
with URLs of the form
http://mysite/show_product.aspx?key=1234
etc, and the app is started from http://mysite/index.aspx. (Backend
is currently using Mono). Using the GWT app, the cron job will now
create a new index.html file which looks like:
html
body
script type=text/javascript
window.location = http://mysite/MyGWTApp;;
/script
noscript
some welcome blurb
a href=http://mysite/TextOnlyServlet?1234;/a
insert URL for every product we want indexed...
/noscript
/body
/html
and the sitemap will now contain URLs like
http://mysite/TextOnlyServlet?1234
etc. (These URLs probably don't need to be in index.html as the search
bot should read the sitemap anyway).
The TextOnlyServlet simply reads the product description from the
database and sends an unformatted HTML document back to the browser
which looks like:
html
body
script type=text/javascript
window.location = http://mysite/MyGWTApp#1234;;
/script
noscript
blurb for product 1234 read from database. Don't care about
format, just the words
/noscript
/body
/html
So if a person clicks on a Google search result, which will be a URL
like http://mysite/TextOnlyServlet?1234, their browser will get the
HTML above and should redirect to the GWT app, which uses the correct
history token, and we're away. Certainly there is a small overhead in
the unnecessary text HTML sent down the line, but hopefully once in
the GWT app they will bookmark from within there, so next time around
they just get the GWT app.
I think this should work, and seems to me to be within the spirit of
the Google Webmaster guidelines.
Bryan
--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---
Re: Search Engine Indexing
Quick answer for me - no, never expected it to be indexed so there was never any wondering The trade off that Eric mentions was always made pretty clear by the search engines and in my case, we decided to render pages we wanted indexed outside of GWT and we have a parallel application structure to render these pages with a minimum of javascript. We still have some problems: 1. a slide show of multiple pictures is not so easy to deal with 2. we use a couple of 3rd party embedded components, that we like, but we'll have to replace at some point because the content in them doesn't get indexed I think your second question makes a presumption that a GWT rendered webpage has only a single URL. This is not necessarily the case. There are some GWT apps out there that have large URL spaces based on content that they render. They have an indexing problem if they cannot provide the same content sans GWT execution. On Jan 25, 7:12 am, Peter Ondruška peter.ondru...@gmail.com wrote: Following discussion on indexing AJAX applications I have to ask if those who wonder why their GWT applications cannot be indexed if you expect search engines to index Java applets or Flash out there on the web, or compressed files and executable files? And if somehow GWT application get indexed what links do you expect to be shown insearch results--it can only be yourapp#variables. Is it not enough to have the application entry html indexed and available in results? Peter 2009/1/25, Eric Ayers zun...@google.com: Here are some official answers on the subject: Notes on Ajax: http://www.google.com/support/webmasters/bin/answer.py?hl=enanswer=8... Don't be evil, Guidelines for Webmasters: http://www.google.com/support/webmasters/bin/answer.py?answer=35769 On Sun, Jan 25, 2009 at 5:04 AM, jos jot...@gmail.com wrote: Eric Just to make sure I understood your last point, we should be looking for a search bot indicator like a URL parameter or something, and if we see it we should render our page as statically and flat as possible? Thanks, jos On Jan 24, 5:01 am, Eric Ayers zun...@google.com wrote: Hi Bryan, I understand your frustration. Unfortunately, due to the extremely competitive nature of web search, we here at Google can't say a lot about the Google bot or the roadmap for future improvements. Indexing JavaScript apps is a general problem not particular to GWT. Obviously, this is one of those problems everyone in the web apps search community needs to keep coming back to in order to find better ways to solve it. Just to give you an idea of the complexity involved, the first page of JavaScript for GWT basically runs a big switch statement that loads a different script depending on which browser is running (which browser should the googlebot run. Which bugs should it emulate?). It doesn't actually create the DOM until after the body of the document is finished loading (when does it know to start looking at the DOM?). Your app might be perfectly happy for the bot to index just the front page, but that is still going to leave a huge swath of unhappy app developers. Another page might present something on the first page that is not very indicative of the content, like: this browser is not supported or Login or create an account or choose your region using images before continuing. A page might have tabs or a menu with content that doesn't actually get attached to the DOM until after the tabs are clicked and has a message (click on the menu to ...). Here's some spin for you: I think the message from the search side of search engines isn't Don't use JavaScript. Instead, the message is to provide a page of HTML that faithfully describes your app and/or its content when the search engine crawls your page. I know its more work, but think about how that might actually be an opportunity for Web 2.0 authors. -Eric. On Sat, Jan 24, 2009 at 2:59 AM, bryanb webbt...@gmail.com wrote: That's the point of my query/question, Why can't the Google bot understand Javascript ? As I said originally, using Firebug I can see what the Javascript has rendered to the DOM, so there's no good reason the Google bot can;t do the same. Granted, it cannot follow links or any of the possibly unlimited execution paths in the Javascript, but it should be able to render the initial state of the page, and consequently index stuff on that page. Likewise if there is a site map with history tags, it should be able to render the initial state of each of those pages and index accordingly. The initial state is really all you want indexed anyway - if I do a Google search for fubar, I reasonably expect the URLs returned to point to a page with fubar on it somewhere i.e. for a GWT app the initial state of that page. It just seems a bit strange that one part of
Re: Search Engine Indexing
Eric Just to make sure I understood your last point, we should be looking for a search bot indicator like a URL parameter or something, and if we see it we should render our page as statically and flat as possible? Thanks, jos On Jan 24, 5:01 am, Eric Ayers zun...@google.com wrote: Hi Bryan, I understand your frustration. Unfortunately, due to the extremely competitive nature of web search, we here at Google can't say a lot about the Google bot or the roadmap for future improvements. Indexing JavaScript apps is a general problem not particular to GWT. Obviously, this is one of those problems everyone in the web apps search community needs to keep coming back to in order to find better ways to solve it. Just to give you an idea of the complexity involved, the first page of JavaScript for GWT basically runs a big switch statement that loads a different script depending on which browser is running (which browser should the googlebot run. Which bugs should it emulate?). It doesn't actually create the DOM until after the body of the document is finished loading (when does it know to start looking at the DOM?). Your app might be perfectly happy for the bot to index just the front page, but that is still going to leave a huge swath of unhappy app developers. Another page might present something on the first page that is not very indicative of the content, like: this browser is not supported or Login or create an account or choose your region using images before continuing. A page might have tabs or a menu with content that doesn't actually get attached to the DOM until after the tabs are clicked and has a message (click on the menu to ...). Here's some spin for you: I think the message from the search side of search engines isn't Don't use JavaScript. Instead, the message is to provide a page of HTML that faithfully describes your app and/or its content when the search engine crawls your page. I know its more work, but think about how that might actually be an opportunity for Web 2.0 authors. -Eric. On Sat, Jan 24, 2009 at 2:59 AM, bryanb webbt...@gmail.com wrote: That's the point of my query/question, Why can't the Google bot understand Javascript ? As I said originally, using Firebug I can see what the Javascript has rendered to the DOM, so there's no good reason the Google bot can;t do the same. Granted, it cannot follow links or any of the possibly unlimited execution paths in the Javascript, but it should be able to render the initial state of the page, and consequently index stuff on that page. Likewise if there is a site map with history tags, it should be able to render the initial state of each of those pages and index accordingly. The initial state is really all you want indexed anyway - if I do a Google search for fubar, I reasonably expect the URLs returned to point to a page with fubar on it somewhere i.e. for a GWT app the initial state of that page. It just seems a bit strange that one part of Google has created a tool for making really usable web sites, but the search side of Google says don''t use Javascript if you want to be indexed. -- Eric Z. Ayers - GWT Team - Atlanta, GA USAhttp://code.google.com/webtoolkit/ --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: Search Engine Indexing
Hi Bryan I recently had the chance to speak with some good SEO types and the subject of javascript did come up. The bottom line is don't hold your breath waiting for this to happen in any search engine. I think its easy to appreciate how difficult it would be for a search engine to do this. You'd essentially be creating a virtual browser machine which would be loading a page and executing it (as you point out) but it's not so simple, how much execution should be done? How to does the engine know when to stop? It's kind of a halting problem. The other thing we have to keep in mind is that the cost of this is pretty high and there are a *lot* of pages out there to index. I feel your pain, I'd like to create a commenting system using GWT, but any of the content in that commenting system is going to have to be sent down to the client in HTML if I want it indexed. I was discussing another similar problem I have where we use a component that is wrapped by an iframe, how much of the content in that iframe is going to get parsed? Not clear. jos On Jan 23, 11:59 pm, bryanb webbt...@gmail.com wrote: That's the point of my query/question, Why can't the Google bot understand Javascript ? As I said originally, using Firebug I can see what the Javascript has rendered to the DOM, so there's no good reason the Google bot can;t do the same. Granted, it cannot follow links or any of the possibly unlimited execution paths in the Javascript, but it should be able to render the initial state of the page, and consequently index stuff on that page. Likewise if there is a site map with history tags, it should be able to render the initial state of each of those pages and index accordingly. The initial state is really all you want indexed anyway - if I do a Google search for fubar, I reasonably expect the URLs returned to point to a page with fubar on it somewhere i.e. for a GWT app the initial state of that page. It just seems a bit strange that one part of Google has created a tool for making really usable web sites, but the search side of Google says don''t use Javascript if you want to be indexed. --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: Search Engine Indexing
Why does the GWT compiler not create a version for the google index bot that contains only static content that can be indexed? When you can compile from Java to Javascript there must be a way to compile it in a static html content. Where you can exclude the whole grafical stuff. --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: Search Engine Indexing
Here are some official answers on the subject: Notes on Ajax: http://www.google.com/support/webmasters/bin/answer.py?hl=enanswer=81766 Don't be evil, Guidelines for Webmasters: http://www.google.com/support/webmasters/bin/answer.py?answer=35769 On Sun, Jan 25, 2009 at 5:04 AM, jos jot...@gmail.com wrote: Eric Just to make sure I understood your last point, we should be looking for a search bot indicator like a URL parameter or something, and if we see it we should render our page as statically and flat as possible? Thanks, jos On Jan 24, 5:01 am, Eric Ayers zun...@google.com wrote: Hi Bryan, I understand your frustration. Unfortunately, due to the extremely competitive nature of web search, we here at Google can't say a lot about the Google bot or the roadmap for future improvements. Indexing JavaScript apps is a general problem not particular to GWT. Obviously, this is one of those problems everyone in the web apps search community needs to keep coming back to in order to find better ways to solve it. Just to give you an idea of the complexity involved, the first page of JavaScript for GWT basically runs a big switch statement that loads a different script depending on which browser is running (which browser should the googlebot run. Which bugs should it emulate?). It doesn't actually create the DOM until after the body of the document is finished loading (when does it know to start looking at the DOM?). Your app might be perfectly happy for the bot to index just the front page, but that is still going to leave a huge swath of unhappy app developers. Another page might present something on the first page that is not very indicative of the content, like: this browser is not supported or Login or create an account or choose your region using images before continuing. A page might have tabs or a menu with content that doesn't actually get attached to the DOM until after the tabs are clicked and has a message (click on the menu to ...). Here's some spin for you: I think the message from the search side of search engines isn't Don't use JavaScript. Instead, the message is to provide a page of HTML that faithfully describes your app and/or its content when the search engine crawls your page. I know its more work, but think about how that might actually be an opportunity for Web 2.0 authors. -Eric. On Sat, Jan 24, 2009 at 2:59 AM, bryanb webbt...@gmail.com wrote: That's the point of my query/question, Why can't the Google bot understand Javascript ? As I said originally, using Firebug I can see what the Javascript has rendered to the DOM, so there's no good reason the Google bot can;t do the same. Granted, it cannot follow links or any of the possibly unlimited execution paths in the Javascript, but it should be able to render the initial state of the page, and consequently index stuff on that page. Likewise if there is a site map with history tags, it should be able to render the initial state of each of those pages and index accordingly. The initial state is really all you want indexed anyway - if I do a Google search for fubar, I reasonably expect the URLs returned to point to a page with fubar on it somewhere i.e. for a GWT app the initial state of that page. It just seems a bit strange that one part of Google has created a tool for making really usable web sites, but the search side of Google says don''t use Javascript if you want to be indexed. -- Eric Z. Ayers - GWT Team - Atlanta, GA USAhttp:// code.google.com/webtoolkit/ -- Eric Z. Ayers - GWT Team - Atlanta, GA USA http://code.google.com/webtoolkit/ --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: Search Engine Indexing
Following discussion on indexing AJAX applications I have to ask if those who wonder why their GWT applications cannot be indexed if you expect search engines to index Java applets or Flash out there on the web, or compressed files and executable files? And if somehow GWT application get indexed what links do you expect to be shown insearch results--it can only be yourapp#variables. Is it not enough to have the application entry html indexed and available in results? Peter 2009/1/25, Eric Ayers zun...@google.com: Here are some official answers on the subject: Notes on Ajax: http://www.google.com/support/webmasters/bin/answer.py?hl=enanswer=81766 Don't be evil, Guidelines for Webmasters: http://www.google.com/support/webmasters/bin/answer.py?answer=35769 On Sun, Jan 25, 2009 at 5:04 AM, jos jot...@gmail.com wrote: Eric Just to make sure I understood your last point, we should be looking for a search bot indicator like a URL parameter or something, and if we see it we should render our page as statically and flat as possible? Thanks, jos On Jan 24, 5:01 am, Eric Ayers zun...@google.com wrote: Hi Bryan, I understand your frustration. Unfortunately, due to the extremely competitive nature of web search, we here at Google can't say a lot about the Google bot or the roadmap for future improvements. Indexing JavaScript apps is a general problem not particular to GWT. Obviously, this is one of those problems everyone in the web apps search community needs to keep coming back to in order to find better ways to solve it. Just to give you an idea of the complexity involved, the first page of JavaScript for GWT basically runs a big switch statement that loads a different script depending on which browser is running (which browser should the googlebot run. Which bugs should it emulate?). It doesn't actually create the DOM until after the body of the document is finished loading (when does it know to start looking at the DOM?). Your app might be perfectly happy for the bot to index just the front page, but that is still going to leave a huge swath of unhappy app developers. Another page might present something on the first page that is not very indicative of the content, like: this browser is not supported or Login or create an account or choose your region using images before continuing. A page might have tabs or a menu with content that doesn't actually get attached to the DOM until after the tabs are clicked and has a message (click on the menu to ...). Here's some spin for you: I think the message from the search side of search engines isn't Don't use JavaScript. Instead, the message is to provide a page of HTML that faithfully describes your app and/or its content when the search engine crawls your page. I know its more work, but think about how that might actually be an opportunity for Web 2.0 authors. -Eric. On Sat, Jan 24, 2009 at 2:59 AM, bryanb webbt...@gmail.com wrote: That's the point of my query/question, Why can't the Google bot understand Javascript ? As I said originally, using Firebug I can see what the Javascript has rendered to the DOM, so there's no good reason the Google bot can;t do the same. Granted, it cannot follow links or any of the possibly unlimited execution paths in the Javascript, but it should be able to render the initial state of the page, and consequently index stuff on that page. Likewise if there is a site map with history tags, it should be able to render the initial state of each of those pages and index accordingly. The initial state is really all you want indexed anyway - if I do a Google search for fubar, I reasonably expect the URLs returned to point to a page with fubar on it somewhere i.e. for a GWT app the initial state of that page. It just seems a bit strange that one part of Google has created a tool for making really usable web sites, but the search side of Google says don''t use Javascript if you want to be indexed. -- Eric Z. Ayers - GWT Team - Atlanta, GA USAhttp:// code.google.com/webtoolkit/ -- Eric Z. Ayers - GWT Team - Atlanta, GA USA http://code.google.com/webtoolkit/ --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: Search Engine Indexing
Hi Eric, Thanks for the heads up on that I appreciate there's a few more 'gotchas' than my admittedly simplistic scenario, and I'm sure there's lots of big brains at Google thinking about the problem. Thanks again, Bryan --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: Search Engine Indexing
AFAIK, the Google bot (or any other bot for that matter), does not understand Javascript. Therefore, if your entire website is built with GWT, all the Google bot will see is a javascript import for the nocache file. You'll have to search the group for Search engine optimization to get some ideas of how to tackle this problem. -- Arthur Kalmenson On Thu, Jan 22, 2009 at 10:04 PM, darkflame darkfl...@gmail.com wrote: I think its possible exactly how you discribed. Its certainly how I planned to do it, and it seems to work. bryanb wrote: I've searched the forum on this topic, and it appears the only way to get a GWT site indexed is by some horrible hacks. If I use Firebug with Firefox, I can get the HTML displayed that the Javascript is writing to the DOM, so this means it should be possible for the Google search bot to do a similar thing, then parse the HTML like any static web page. Obviously, links cannot be followed, but the Google Webmaster site indicates that you should submit a site map to Google with the pages you want indexed anyway. So, provided I have implemented history in my GWT app correctly, I could submit a site map like: http://www.example.com/com.example.gwt.HistoryExample/HistoryExample.html#page1 http://www.example.com/com.example.gwt.HistoryExample/HistoryExample.html#page2 etc The Google bot could read each page as suggested above, index the words/labels etc and add the links to the search index, so that if they were displayed via Google search you go to the correct history page and everyone's happy. Is this not possible ? Bryan --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
