Script-Served Content Indexing
Google has supported crawling and indexing of AJAX content for several years now, and even created special guidelines utilising HTML snapshot capabilities to help webmasters ensure that their rich content served this way was discovered and indexed fully.
The Test – How to check Script-Served Content Indexing
First, we registered a new domain name and set it up on Google Webmaster Tools. We made two versions of the homepage – one with a charming poem about widgets served via Google Tag Manager custom HTML, and one with a different poem served as normal inline HTML.
The inline HTML page was put up first and tracked using Stat, which takes ranking samples from SERPs based on specific query terms. We were aiming for an immensely long-tailed search term of course for purposes of this experiment, and after WMT submission it only took 3 days for the content to appear in Google results.
Note that this was just the raw content – no links, no social, nothing but a single webpage and a Webmaster Tools account. Not bad, eh?
We then replaced this with the version of the homepage that had different content on it, all deployed this time via Google Tag Manager so the source code of the page looked like this:
This took a little longer – about three days to initially become visible, then a hiccup for over a week before it started ranking consistently for the page H2 term. Note that at no point did the page become visible at all in Bing or Yahoo even after the WMT submission – but then those engines have never claimed to be AJAX crawling experts, which is fair enough. The SERP sampling for these terms is provided by our chums over at Stat, if anyone wants to see visibility graphing like this for themselves.