Check out the “342 matches” snippet attached to the MadisonApartmentLiving.com result for “madison wi apartments“:
So not only is Google seeing content in JS, it considers a number + “matches” relevant enough to put it in the SERP snippet.
We always tell clients not to rely on Google to see your content that requires JS, and we still will, but GOOG is getting pretty good at this kind of thing.
7 Response Comments
The fact that it appears as a snippet is interesting. Suggestive that there might be a benefit to serving dynamic content via JS.
Curious to see the server log files on that one and if gbot crawls it any differently.
I wonder what implications are here regarding dynamic number swapping js script like callrail. We have been using DNS successfully without having bots scrape that call tracking info so far. Do you see any issues here Andrew?
Dave, I don’t think this has anything to do with the text being in JS. It’s more likely where the text appears (Close to the target keywords on the page) that is key.
Cody, I think this pretty much shows that you should only be serving DNS #s to visitors that come via organic, paid and maybe social else Googlebot is going to see them.
Wow, very cool insight. Would be interested in seeing how else Google is using JS for NAP purposes, like Cody mentioned with CallRail.
Wow, very cool indeed! And I don’t think that google will fix such kind of things soon.
I appreciate it, It’s a good article. Would be interested in seeing how else Google is using JS for NAP purposes.