Understanding compatible Javascript for Google

Beginning in 2016, Bazaarvoice has implemented changes to our hosted display solution to take advantage of the expanded Javascript indexing performance exhibited by Google and, to a lesser extent, Bing. Understanding these improvements can help you get more SEO benefit from your hosted solution. Most improvements require limited or no extra development from your team.


To take advantage of the improvements to our hosted display solution, complete the following steps.

  1. Ensure that each of your product pages includes correct Schema.org markup, and that your Conversations configuration hub settings are correctly configured.
  2. If you are using the Conversations configuration hub, redeploy to production. If you are not using the configuration hub, contact Bazaarvoice to file a case to enable improved Javascript linking.
  3. If you use the Bazaarvoice SDK for server-side deployment, ensure that you update to the latest version of the SDK.

Refer to the following sections for full explanations of the improvements.

Addition of Schema.org markup in CGC code (action required)

We now add correctly formed Schema.org markup to consumer-generated content (CGC) that we serve to your page. When search engines such as Google and Bing index this markup, the likelihood of rich snippets appearing in search results increases, which in turn drives traffic to your site.

In order for the markup we inject to be read correctly when it is in your page, you must also add Schema.org markup to your page.

What you need to do

Add Schema.org itemtype and itemprop declarations to your pages, and adjust your SEO settings in the Conversations configuration hub. The full instructions are listed in the Conversations knowledge base.

Improved linking between CGC content pages (action required)

We have changed the way links are handled in the Javascript code that delivers CGC to your pages. Instead of a Javascript onclick event, we now use href links that search engines can index more easily.

When shoppers view a product that contains more than one “page” of reviews, they interact only with the Javascript. The URL does not change. However, dynamically creating href links between pages of CGC allows search engines to better index all the content and take shoppers directly to relevant results.

What you need to do

  1. If you use the Conversations configuration hub to manage your deployment, redeploy to production to receive these changes. If you do not use the Conversations configuration hub, contact Bazaarvoice to file a case to enable the improved Javascript link.
  2. If you use the Bazaarvoice SDK for server-side deployment, ensure that you update to the latest version of the SDK.

Improved pagination link formation (no action required)

We have improved the parameters used to control pagination in the URLs we create for CGC. Previously, URLs were formed using the bvrrp parameter. This parameter made URLs difficult for clients and SEO consultants to analyze. URLs now include a bvstate parameter that uses key/value pairs.

For example, a URL formed using the new code might include the following parameter:


In this example, ct:r indicates a content type of “review,” and pg:2 indicates page 2.

In addition to forming the URL in an easier-to-analyze way, we also dynamically add the bvstate parameter to URLs in the canonical tag for your implementation. Shoppers only encounter the bvstate parameter when following links from search results. Shoppers who navigate to CGC directly from your site see no difference in their URLs.

What you need to do

Take no action unless you need time to adjust to the new page links. In rare situations, clients might rely on our previous URL format for their SEO technical reporting. Contact Bazaarvoice if you want to postpone this improvement.