4 ms·
They've been working on it for years, and improving it. They've only recently started claiming that their javascript rendering was ready for "prime time". The
by chrisfosterelli 11y ago
They've been working on it for years, and improving it. They've only recently started claiming that their javascript rendering was ready for "prime time".
The "hashbang" URLs (they call them Escaped Fragment URLs) actually required you to use server-side rendering, that had nothing to do with the spider's javascript rendering engine. I used them on a few sites and it worked pretty well, but I have heard of mixed results on sites that weren't originally on hashbang URLs who transitioned to them. They don't recommend you use these anymore.
- profeta 11y ago> "hashbang" URLs (they call them Escaped Fragment URLs) why not use the RFC terms? https://tools.ietf.org/html/rfc3986#section-3 https://tools.ietf.org/html/rfc3986#section-3 "url fragment" Also, it won't help you on server side rendering since the server will never even see it on the request.
- rmccue 11y agoA hashbang is specifically a fragment starting with a ! character, hence "hashbang".
- TazeTSchnitzel 11y ago> Also, it won't help you on server side rendering since the server will never even see it on the request. It will when Googlebot sees the link and rewrites the URL.
- tyingq 11y ago>>why not use the RFC terms? Because it's specifically different, on purpose. The RFC doesn't cover the "bang" part....the "!". >>the server will never even see it on the request Explained on the (now deprecated) page from Google on this "hashbang" approach: *"The answer is the URL that is requested by the crawler: the crawler will modify each AJAX URL such as www.example.com/ajax.html#!key=value to temporarily become www.example.com/ajax.html?_escaped_fragment_=key=value"