Test 185: Does Continually Refreshing Content With Ajax Help With Ranking Multiple Keywords?

Last month, we looked at indexing through Javascript which was successful. This month, we are moving forward with Ajax, a form of Javascript. For this test, we wanted to look at the concepts of providing different content to search engines using Ajax. The content refreshes every time the page is pulled up. Is this a SEOHack? Will we get to index the keywords?

Test Downloads

Transcription Below

Last month, we looked at JavaScript and we saw that Google will in fact, read what is in JavaScript. Ajax is a form of JavaScript and this might be a completely imprecise definition but the idea is that JavaScript actually runs from the page that you are on so when JavaScript runs, they run from that particular page. What Ajax does, which is a form of JavaScript, is it actually calls content from somewhere else – another site, page, server – so when you render the page, it calls out and grabs the content vs regular JavaScript which has it contained within that page and displays the function when you pull up the page. That is the difference there between JavaScript and Ajax.

There are SEO tools that will allow you to constantly refresh your page and your page’s content to show Google new content to show different keywords. What I did for this particular test is I ran an Ajax function where we had 9 different sections that had a unique piece of content that would be loaded at one time – only one section will display but there were 9 different ones, each one has their own keyword. Every time the page is re-loaded, it would refresh that content. The idea is that we have the opportunity to rank for 9 different keywords by doing this Ajax refresh. This concept is big part of where a lot of web content are going, what tools are doing, but it is kind of a black hat thing to be doing as well. There is also the idea of you need to continually refresh your content and a lot of people advocate refreshing it quite regularly so that is what we are looking at in here. Can we get one page to index for 9 different keywords where they are constantly refreshing that content every time the page is loaded.

Those are the keywords there. What is a lot of fun in this screenshot here – this is from fetch and render. When you do fetch and render in search console, it will show you how Google bot sees the page and they will show you how your visitors see the page and you can kind of see if there are problems with Google Bot rendering anything. You can see in the bottom section, that is the section where it is getting the refresh content. What is really cool, and I didn’t know this about fetch and render, is that it run it twice and the reason that we know that it run it twice is because it has a different keyword and this Ajax is set to refresh every time a crawl happens. I thought that was pretty cool – I had no idea that when Google is doing a fetch and render, that it would actually crawl the page two times. The page cached and it has been cached since March but this is to show that it is cached and that is the page title. However, none of the keywords are indexed. That is one of the particular keywords, none of the nine is indexed.

What I think is going on here is that the page is refreshing too quickly. Because it is happening every time Google bot is coming, what this tells me is that it can cache the page, it can take a picture of it, but it can’t index it appropriately. It cannot index it for those keywords which tells me that indexing requires several crawls – more than one. Probably 2, 3, or 4 and those are not recorded by cache date. So the bot is going more than what we can see in the cache which is this firm date right here that we can confirm that Google came to this page on this day because it has the cache but clearly, Google is coming more than that and I am sure you can see that within the server logs. But if you are doing some black hat thing where you are refreshing the content every time, you are probably doing yourself a disservice. In fact, if you are refreshing it every couple of days, you are still probably doing yourself a disservice. I would wager that in order to get your content to index properly and for it to rank, you would need several Google crawls, several processes to get it in and I think that is what this test is showing us.

Dori: This is really important because I would have thought that it would have cached it and indexed it with all these keywords and when we used to cloak, we used to refresh all the time and so, this is telling me that I was doing a disservice to myself – that static or at least some time is going to out perform a dynamic page, perhaps.

I thought so too. I thought, most of them, not all of them would index but I think the problem is that the refresh was happening too quickly and the bot came one time and it sees the content and it starts part of the indexing process but it needs a couple more crawls to get in there in order to make it stick but every time the bot came back, it got a new page. Things change, I do not know how to index it.

Dori: This is really important. I think the non-indexing is just as important. I kind of wished it had, it would be cool to hit all kinds of keywords with Ajax but knowing that it is not is just as important. Getting the sense that it needs to be static at least for a certain amount of time to rank. Pretty critical, actually.

Is this test affected with the issues of getting content indexed lately?

I think that is a certain thing to consider, for sure. The only reason or one of the reason I think this is valid as is even despite the indexing issues is that Google announced the update that we were looking for, that we were talking about – hey this update is coming – that hit on the 16th. We’d had 10days since then and at least in a lot of the test that we had that had indexing normalized. It is still difficult but that certainly is a possibility. I think after that 16th day, we are still getting the same results, none of those keywords have indexed. I think we are seeing true results but I am considering to let this run to see if we can actually get any of those to index. It is possible that it could. We are letting this go but I feel good about showing this now because I had all those days after the announced update.