In 2009 google issued the ajax crawling proposal
https://developers.google.com/webmasters/ajax-crawling/docs/getting-started?hl=en
The proposal basically says that for every url of the form
http://www.foo.com/page#!var=value where the URL fragment (staff after #)
are not visible to the server side and therefore are used by client side
technologies such as GWT and JS to render dynamically the page the google
bot wil visit your site with this URL
http://www.foo.com/page?_escaped_fragment_=var=value which is server side
visible and therefore can serve static content (pre-rendererd pages).
In the summer of the 2015 there were people talking about deprecation of
the above scheme.
Finally in 14 of October 2015 finally deprecated the scheme. Note that at
least twitter, linkedin, google plus, and facebook honor the scheme and
visiting the links you share in order to pick up content like images etc.
Google says that they will continue to support it but nobody knows (or at
least I don't know) when they will decide to kill it.
Right now my GWT application that employs the #! URL fragment is being
crawled twice. One with the old scheme (_escaped_fragment_) and one with
the new scheme. The new scheme basically says that:
- you don't serve static content
- you create the DOM dynamically with JS and googlebot knows how to run
JS and create the DOM
So basically no changes at all.
Given my application is crawled twice I have questions about:
- don't know what takes precedence?
- how to handle duplication?
- how to handle parameters in webmaster's console?.
Hope it helps but I doubt it... at least I am feeling a little bit better
:-)
Vassilis
On Fri, Oct 23, 2015 at 11:25 PM, Ed <[email protected]> wrote:
> How did you make your GWT site Crawlable by Google ?
> Please share your experience?
>
> According to the Goolge info (link
> <https://developers.google.com/webmasters/ajax-crawling/>): To make it
> crawlable you should generate the static content and make it accessible
> through specified url's.
>
> I am currently thinking of generating the static content myself during the
> compilation by using something like htmlUnit, or using a tool like
> prerender.io.
> I am not sure which approach to take, please your feedback.
> - Ed
>
> --
> You received this message because you are subscribed to the Google Groups
> "GWT Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To post to this group, send email to [email protected].
> Visit this group at http://groups.google.com/group/google-web-toolkit.
> For more options, visit https://groups.google.com/d/optout.
>
--
Vassilis Virvilis
--
You received this message because you are subscribed to the Google Groups "GWT
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.
