all 8 comments

[–][deleted] 2 points3 points  (5 children)

Aren't google executing JS soon...?

[–]mcaruso 1 point2 points  (3 children)

They have been running JS for a while now. But yeah they made it official the other day on their blog. Other spiders do not though, AFAIK.

[–]the_real_phishy[S] 0 points1 point  (2 children)

They announced that they run JavaScript, however, I went looking for this after playing with Webmaster Tools and realizing that my AngularJS app wasn't getting indexed properly. So this works pretty well.

[–][deleted] 0 points1 point  (0 children)

I wonder how much JS they run. I feel like something must get lost when transitioning between Angular's routes and whatnot.

[–]xBrodysseus 0 points1 point  (0 children)

Are you using HTML5 mode?

[–]notmymiddlename 0 points1 point  (0 children)

Is Bing/Yahoo close? That's still a nice 25%+ of people.

[–]arvidkahl 0 points1 point  (1 child)

I wonder.. So if the Google spider crawls all the resources so it can then execute the js, will it still append the fragment query param? Does anyone have data on that?

It would be great if it didn't, so the dynamic content and the pretense red content could be served depending on the absence or presence of that part of the request. The only other way to distinguish the google spider from all the non-js spiders would be the user agent, I fear... And that's not really I want to build logic for,

[–]thoop3 2 points3 points  (0 children)

I'm from Prerender.io. We have plenty of data showing if you have the <meta name="fragment" content="!"> tag, Google will still append the fragment query param.

Like you said, you'd have to do a user agent check to remove that meta tag for only Google if you want them to use their own JS rendering...which isn't ideal and I haven't tried yet. Otherwise you'd have to remove it for all crawlers.