3 ms·
Currently I use prerender.io and this meta tag: <meta name="fragment" content="!"> I don't actually use #! URLs, (or pushstate, though I might use pushsta
by nailer 11y ago
Currently I use prerender.io and this meta tag:
<meta name="fragment" content="!">
I don't actually use #! URLs, (or pushstate, though I might use pushstate in the future) but without both of these Google can't see anything JS generated - using Google Webmaster Tools to check.
Does this announcement mean I can remove the <meta> tag and stop using prerender.io now?
- rgbrgb 11y agoWe have a similar setup and were wondering the same thing (though we use push state). Today we were actually trying to figure out a workaround for 502s and 504s that google crawler was seeing from prerender. We just took the plunge and removed the meta tag because over 99% of our organic search traffic is from google. Fingers crossed!
- thoop 11y agoI'd love to help here if I can. I'd also love to hear the results of you removing the meta tag! todd@prerender.io
- thoop 11y agoIf Google Webmaster Tools is unable to render your website correctly, then that's a good indicator that Googlebot won't be able to render the pages correctly either. If you remove the fragment meta tag, then Google will need to render your javascript to see the page. Let us know how that goes if you try it! todd@prerender.io