Case Study

Analysis of a malfunctioning module and saving position in Google - Divezone.pl

"Probably the biggest dive shop in Poland.
Over 5000 products in stock.
Over 18 years of diving experience" - Divezone.com

It all started with a group on Facebook

On the Polish group of PrestaShop users there was an entry in which an employee and a shop owner ask for urgent help with displaying products on Google. The post has come to our attention due to the lack of a meaningful explanation.

There was a curiosity “What’s going on there? Nobody’s reacting. They don’t know what the problem is? You have to check it out.” – we like challenges! (well-worn formula in the industry, but it’s true we love challenges)

Initial problem analysis

An employee in the post showed a problematic product, a quick checklist:

  1. Product available in the shop? Yes!
  2. Implemented Rich Snippet? Yes!
  3. Chrome development console returns errors? No
  4. Are all results in Google without extended elements? No

Checking the visibility of the domain. Making a first diagnosis

Czas na sprawdzenie widoczności domeny w Google. The view wasn’t interesting, a huge fall in position. A large drop in the item suggested a malfunction of the script or an error in robots.txt or a dozen or so other problems that make no sense to write down – let’s call it a lack of access to content.

A large drop in the item suggested a malfunction of the script or an error in robots.txt or a dozen or so other problems that make no sense to write down – let’s call it a lack of access to content.

Bot trap test

Since Google has no access to the content and the website looks like it works. We assumed that a bots’ trap was set (yes, something like that exists). The test was passed, but not as we would have expected. Our software returned HTTP 200 information to us without redirections with unreasonably low response weights.

After suspicious response it turned out that the shop script did not return a subpage of the product card but only returned it:

<script>window.document.location.reload(true);</script>

Google only sees a JavaScript line

Using our proprietary testing tool, we launched JavaScript, loading another testing scenario. It showed that during the first call the JavaScript line responsible for reloading the window content is returned. The second answer is already the correct source of the site. Instead of seeing the product, Google Bot only saw a line of JavaScript code, which should not be there.

Time to inform the customer and fix the error

We wrote to the client presenting a preliminary diagnosis of the problem with the cooperation proposal. After a few minutes, we received the necessary accesses with the green light to operate.

Tracking the malfunctioning element was just a cherry on the cake. The problem was a dubious quality module for cleaning the cache of the client’s browser.

Business benefits and effects

The effect of our work could be observed a few days after removing the dubious quality of a module from another company. The website has started to be five again after the positions in the search engines.

According to the customer’s information, a malfunctioning module caused the number of visits to be halved. Bringing financial losses.