Google’s indexing of rendered javascript – Retest

As we tested a while back, about a year from the time of this posting, read more here.  But, as with many things – changes happen.  Same deal with the Google algorithm changes, we want to be sure the user experience tweaks we make are good for both SEO and leave people’s ability to purchase our products.

The back story

The website I work on at Clickstop is US Cargo Control, we sell cargo control product both B2C and B2B.  We leverage the ERP system Netsuite, it handles all our back-end process and front-end web hosting too.  Which can be a blessing and a curse.  The curse part is very old, non-changeable HTML.  It kind of stinks…but we work around it.

1inchRatchetPageWhat we had prior is a large grid style layout.  It works, especially when you have a small amount of products which are different – what we had when we started.

Our game Plan

We have taken the HTML Netsuite puts out – and used jquery to make some changes to the DOM – in the name of use experience.  We want to show the page with more of a larger table based display.  Same exact data – but just a different layout, so people can see more and purchase more.

See an example here – on the US Cargo Control 6×19 Wire Bright Wire Rope page.

Again I ask – What does Google think of this

Firstly – Google is very anti-SEO spamming.  And that is fine – but Google has no issue with using javascript/jquery to make pages more useful.  If the appearance of the page, IF it is helping the user use the page.  It is usability improvement, and that is for sure what we are doing.

So – how can we test it.  The last test (Does Google index rendered javascript?) we ran started to bring back some interesting results with Google’s algo changes.  We found that Google was not reading the rendered javascript, it was only reading the HTML  But as we discussed above – changes are the constant.

So – we designed this test to look and act more like our website and its grid layout.  We want to know if Google is indexing rendered javascript – or said another way, does Google index the changes we have made to the page for user experience.

How are we going to test it?

table-exampleWe’re going to build something like it and see how Google handles it.  As you can see here…this is what the code looks like prior…and also after we modify it.  Notice the tables – they will not be present when you “inspect” the DOM, only in the source.

So we’ll recreate that in the test, only we’ll just use one item and switch it out to one little table.  Shouldn’t be too bad.  We’ll get some random keywords to use as unique identifiers – and we’ll be off to the races.

We have the keyword in an H3 tag and do the exact same thing in the rendered javascript, we’re switching that out which replicates what do in the table layout on our website to help more items be seen.

Here’s the diagram from the last test

Does Google index rendered javascript?
We will use the exact same method – we’ll update the keywords and see what comes with it.

Here are the keywords:

New Test: 04/2014

Keyword 1: tootagtootagtweedle
HTML:  2014-04-google-index-rendered-javascript-k1-html.htm
JS: 2014-04-google-index-rendered-javascript-k1-js.htm

Keyword 2: baddoodlewingo
HTML: 2014-04-google-index-rendered-javascript-k2-html.htm
JS: 2014-04-google-index-rendered-javascript-k2-js.htm

Keyword 3: wootybosinkabull
HTML: 2014-04-google-index-rendered-javascript-k3-html.htm
JS: 2014-04-google-index-rendered-javascript-k3-js.htm

Keyword 4: hobbertyvino
HTML: 2014-04-google-index-rendered-javascript-k4-html.htm
JS: 2014-04-google-index-rendered-javascript-k4-js.htm

Keyword 5: zangodippity
HTML: 2014-04-google-index-rendered-javascript-k5-html.htm
JS: 2014-04-google-index-rendered-javascript-k5-js.htm

Off we go…

Here is a link to all 5 keywords in Google to see what is getting indexed.

Tags: , , , , , , , ,