Amber Milan Eskridge wrote:
> You could create the HTML on the server side using Amber and serve it to
> Google
1. Use paths for inter-app navigation, either #!path/to/part or normal
/path/to/part using HTML5 pushState() family.
2. Create htmls on the server for google (or for that matter, anyone):
- in #!path/to/file case, Google has even a protocol for this, so if
it ask your server for a page, it sends it scrambled so it is
_googlescrambledprefix/path/to/file (find it somewhere on the net, if
you're interested);
- in /path/to/file case, serve pre-made page with <script> to you
application (amber or whatever else), so that google is happy (and the
user as well, since page appears loaded immediately), and then let the
application take it over and continue as usual.
(I understand it's not the easiest way; you have to write the code
reusably so you can render same things on the client as well on the
server... maybe look at jsdom or the kind for the help, so you can
render using client-side code on the server).
Herby
> On Tue, Apr 24, 2012 at 1:41 AM, Sebastian Sastre
> <
[hidden email] <mailto:
[hidden email]>> wrote:
>
> shit :/
>
>
>
>
> Em sábado, 21 de abril de 2012 07h27min26s UTC-3, nicolas petton
> escreveu:
>
> Hey!
>
> If the content is built dynamically, then yes, that's a problem
> for Google.
> Look at what Twitter does, there's also a static version for
> each profile, etc page.
>
> BTW, I'll do the same for SmalltalkHub.
>
> CHeers,
> Nico
>
> On Apr 20, 2012, at 10:31 PM, Sebastian Sastre wrote:
>
>> Hey guys,
>>
>> what about SEO with amber?
>>
>> If you make a site with amber, lets say a landing page, are it
>> going to be SEO friendly?
>>
>> Any reason for not to choose amber for that job?
>>
>> sebastian
>
> --
> Nicolas Petton
>
http://www.nicolas-petton.fr>
>
Locked
