---
# System prepended metadata

title: Wóo Wòo

---

<h1 style="text-align:center;">Wóo Wòo</h1>

<h2>Installation</h2> 

Our plugin only helps to install automatically:
* Preview badge on collection/product page
* Review widget on product page

So if merchants want to have other widgets(like verified review count badge), they would need to manually install them via shortcodes that we provided in <a href="https://help.judge.me/en/articles/8398919-adding-judge-me-widgets-using-shortcodes">this article.</a>

<h4 style="font-style: italic;">When merchants use a page builder:</h4>

This could be simple like adding/dragging a widget block from Shopify if they also use some page builder plugin like Elementor, Divi, Beaver,... In case the page builder plugin they use doesn’t have a `shortcode` block, you can insert the code into an `HTML` block instead.

<h4 style="font-style: italic;">When merchant don’t use any page builder:</h4>

You would need to inspect what product template page they are using and then try to insert the shortcode into any section it appears on their frontpage. Most of the time, they use standard Woocommere product templates so you can try to add the shortcode directly in the product description field.
![](https://i.imgur.com/iy59zV8.png)

<h4>Customization</h4>

For the simplest and easiest way, you can guide merchants to go to **Appearance > Customize > Additional CSS** and insert the css for customization. Some page builder plugins can also provide a placement to input css code.


<h4>Advanced customization</h4>

Sometimes, merchants want us to make something like click the preview badge to open the review tab or fix Leex theme issue,... Assuming that you can access their store, you can add a Javascript block provided from the page builder and place your custom code in there. In case they don’t use any page builder, you can ask them to install a plugin that supports adding custom code(JS,CSS, HTML,..). The guide’s author would highly recommend <a href="https://wordpress.org/plugins/custom-css-js/">Simple Custom CSS and JS By SilkyPress.com</a> for adding custom code. Another plugin that we usually use is <a href="https://wordpress.org/plugins/code-snippets/">Code Snippets By Code Snippets Pro</a> but it requires you to have knowledge about PHP and Woo’s webhook.

<p style="display: inline-block; color:white; background:red;">DO NOT</p>

<p style="background: #ffa5007a;">Do not try to add any code inside Themes > Theme files editor unless you are confident enough to know what you are doing. This would crash their page and hard to revert and you don’t want them to sue you for destroying their business.</p>


<h2>Troubleshooting</h2>

Before you begin to troubleshoot a woo problem, please make sure that the store meets these criteria:
- [x] It is a working domain (no localhost) - that is accessible from the Internet and is not password-protected.

- [x] The domain is a root domain or subdomain (examplestore.com or sub.examplestore.com), but not a subdirectory (examplestore.com/shop/).
- [x] The store is publishing REST API via the path /wp-json(examplestore.com/wp-json). This should return their shop information in JSON format. Please note that this is public for everyone to see and it is good if you can see our plugin is listed there([for instance](https://www.1800doorbell.com/wp-json)).![](https://i.imgur.com/hHv7rn2.png)

 
<p style="background:#ffa5007a;">If one is not satisfied, our plugin will not work on their store.</p>

<hr>

<h4>Try to be familiar with </h4>

> <p style="display: inline-block;background:#35b935; color:white;">Danger action: Simulate pushing webhooks to Shop Server</p>

This will help to monitor the two webhooks
* judgeme/v1/widget/review_widget/updated
* judgeme/v1/widget/preview_badge/updated

with their `failure count` and `response status`. We can call this danger action to know if our widgets are updating the reviews or not. `Failure count` = 0 means our webhooks are not getting blocked. Else if it is greater than 1, something is preventing our webhook from calling our server to update the widgets. You can share the `response status` to merchants if they know anything about this. 

> <p style="display: inline-block; background:#35b935; color:white;">Warning action: List all api webhook</p>

This will list out all of the webhooks url and its `failed count`.

>> You can safely ignore these two webhooks specificially:
>> 
>> * /wp-json/judgeme/v1/widget/shop_reviews_rating/updated
>> * /wp-json/judgeme/v1/widget/shop_reviews_count/updated
>>
>> Sometimes they have `failed count` greater than 1 but actually do not represent our webhooks are being blocked.

### When widget not updating

#### Our webhooks are coordinated in wrong urls 

Use warning action “list all api webhooks” and compare the urls from the result of warning action and the live url of the store `http` or `https`.
 
![](https://i.imgur.com/lHEoAFw.png)

If the warning action urls are `http` but the live store url is `https` then try to use 

> <p style="display: inline-block;background:#35b935; color:white;">danger action “update woo shops webhooks and pictures protocol” </p>

and then go to settings and try to turn off/on a review or a setting so our settings/reviews can be updated.

#### Products are probably not found in our app

This can happen when merchants duplicate their store(A) into a new one(B), while there are no reviews from store B, store B still displays the reviews. To solve this, ask them to synchronise manually the products, you can send them [this article](https://support.judge.me/support/solutions/articles/44001917145-how-to-synchronize-your-woocommerce-products-with-judge-me). After that, try to use the widget update button in shop info.



#### Reviews contain unsuported emojis

Ask them to remove the unsupported emoji out of the reviews or hide the reviews.

#### Some plugins can cause our widget stop working/update
Be sure that woo users are not usually that smart, just ask for their staff account so you can check the plugins by yourself, try to read the plugin description so you can “guess” which ones are causing this, usually are:
* Optimizer
* Hosting service
* Cache

<div style="display: inline-block; background:#ffa50042;">
    

<p style="font-weight:bolder;">
Not recommendeded</p>
  
You can try to deactivate their plugin to test if that plugin really harms our widgets. This could be a way to find out the cause. Be sure to ask for their permission first.

</div>

When you know the plugin affects this, you can follow the internal articles to try to exclude our script and webhooks.


## Others

Some knowledge that you should understand:

1 Judgeme account = 1 shop info

1 store can only have one judgeme account and the account only assigns for 1 token

<div style="display:-webkit-box;">
    
<div style="
            display:inline-block;
    padding: 6px;
    text-align: center;
    background: #339999;
    border: 1px solid #339999;
    box-shadow: 0px 2px 4px rgb(0 0 0 / 25%);
    border-radius: 4px;
    font-style: normal;
    font-weight: normal;
    font-size: 14px;
    color: white; margin-right:10px;">clear shop's token</div>
    
will create a brand new account(and token) for the shop and this cannot be reverted.</div>

<p style="display: inline-block; color:white; background:red;">DO NOT</p>

<p style="background: #ffa5007a;">Do not click(or advise merchants to click) indiscriminately this button unless you are confident enough to know what you are doing. Please consult with your closest Tier 2 agent when you are not sure if it is needed to solve the case.</p>

### When merchants cannot access our plugin
Woo's merchant love updating their domain so they always end up not able to access Judge.me (they will be directed to https://judge.me/login?type=shop to enter a Shopify domain). You can ask them what their previous domain is and then use

> <p style="display: inline-block;background:#35b935; color:white;">danger action: update Woo shops domain</p>

and enter their new domain.

### Merchant mistakenly clicked clear shop's token button and now they lose all their reviews

Try to find the old account(shop info) then export its reviews and settings. You can differentiate both shop info by the shop's token - ask them what their shop's token is(this can be found in Advanced tab - close to the clear shop's token button). The next step is to import the reviews and settings into the new account. This is the only solution we are having to solve this case.

And remember to update the domain of old shop info into something else so we can recognize which one is the correct shop info.

### AggregateRating


Our plugin adds the AggregateRating field by script after the page is fully loaded. To check whether it is present on the product page or not, you can inspect the page and find the keyword `jdgm-aggregate-rating-jld`
![](https://i.imgur.com/xSJAL7x.png)



<div style="display: inline-block; background:#ffa50042;">
    When testing rich result from a product page, try to test it by URL option and avoid testing by CODE(page source) because page source will not include our AggregateRating field.

</div>

<br>

---


If you want to have a new result(avoid Google not fetching new effects), try to add `#judgeme` or `?judgeme_badge=show` at the end of product url so Google can know it is different URL and fetch new effects you have made.

#### Missing field AggregateRating

* `jdgm-aggregate-rating-jld` is present but Google rich result still saying Missing field AggregateRating.
* `jdgm-aggregate-rating-jld` is not presnt.

Then there is something **delaying/minifying/defering** our script. You can ask the merchant if they are using any plugin that can **delay/minify/defer** Javascript and then exclude our script from being **delayed/minified/defered**.
