Either 'offers', 'review' or 'aggregateRating' should be specified

[netamismb]

I get the following errors in Google search console:

Either 'offers', 'review' or 'aggregateRating' should be specified

Either 'ratingCount' or 'reviewCount' should be specified

Missing field 'ratingValue'

I am using modules Customer loyalty and rewards v3.0.2 and Google JSON+LD v1.0.4  and Niara theme.  How i can add those values, even there is no reviews for products. As far as I am aware, Google just want to see there is possibility to add the review, and not really care if there are reviews or not.

 

[Chandra]

I have the same issue and Google calls them invalid items due to the error.

I use Niara too.

[datakick]

On 3/22/2020 at 6:23 PM, netamismb said:

How i can add those values, even there is no reviews for products

You can't. It's just not possible to include reviews metadata if you don't have any reviews. 

Google search console is an idiot in this case. Simply ignore these warnings. 

[Wartin]

And it's not a warning, but an error:

I'll keep trying with the other errors. Thanks!

Edit: it doesn't find those labels in homefeatured's products, not in every product's page. I suppouse it's product-list-item.tpl which doesn't write the expected 'itemprops'. I'm using Niara.

Edited August 13, 2020 by Wartin

[Wartin]

I see that it gives me one error for every product in every category. Each product page is OK, just a few warnings.

There are dozens of messages in PS forums about this, but found no solution.

 

 

Has anybody fixed Niara or other theme in order to not have any errors from Google? I'm not sure if I have to modify just product-list-item.tpl or if blockspecials.tpl has something to do with printing prices in categories.

Anyway, so far I just got more errors or warnings editing these templates.

Thanks!

 

[Wartin]

On 8/19/2020 at 2:54 PM, Wartin said:

Has anybody fixed Niara or other theme in order to not have any errors from Google?

Hello. I finally found how to make those errors disappear from Google Search Console in Niara. I found how to do it from community theme, from github:

https://github.com/thirtybees/community-theme-default/blob/1.1.x/product-list-item.tpl

So, edit /themes/niara/product-list-item.tpl

In line 126 put:

                <div class="" itemprop="offers" itemscope itemtype="https://schema.org/Offer">

line 130:

                        <meta itemprop="price" content="{$product.price}">
                        <meta itemprop="priceCurrency" content="{$currency->iso_code}">

And finally close the <div> tag in line 150:

</div>

I'm not sure if it's perfect, but google now finds 'offers' and 'price' under categories lists.

Here is all that part of product-list-item.tpl with number lines:

                {if (!$PS_CATALOG_MODE AND ((isset($product.show_price) && $product.show_price) || (isset($product.available_for_order) && $product.available_for_order)))}
                <div class="" itemprop="offers" itemscope itemtype="https://schema.org/Offer">
                    <div class="content_price">
                        {if isset($product.show_price) && $product.show_price && !isset($restricted_country_mode)}
                            {hook h="displayProductPriceBlock" product=$product type='before_price'}
                            <meta itemprop="price" content="{$product.price}">
                            <meta itemprop="priceCurrency" content="{$currency->iso_code}">
                            <span class="price product-price">
              {if !$priceDisplay}{convertPrice price=$product.price}{else}{convertPrice price=$product.price_tax_exc}{/if}
            </span>
                            {if $product.price_without_reduction > 0 && isset($product.specific_prices) && $product.specific_prices && isset($product.specific_prices.reduction) && $product.specific_prices.reduction > 0}
                                {hook h="displayProductPriceBlock" product=$product type="old_price"}
                                <span class="old-price product-price">
                {displayWtPrice p=$product.price_without_reduction}
              </span>
                                {hook h="displayProductPriceBlock" id_product=$product.id_product type="old_price"}
                                {if $product.specific_prices.reduction_type == 'percentage'}
                                    <span class="price-percent-reduction">-{$product.specific_prices.reduction * 100}
                                        %</span>
                                {/if}
                            {/if}
                            {hook h="displayProductPriceBlock" product=$product type="price"}
                            {hook h="displayProductPriceBlock" product=$product type="unit_price"}
                            {hook h="displayProductPriceBlock" product=$product type='after_price'}
                        {/if}
                    </div>
                  </div>
                {/if}

 

Hope it's useful.

I found some forum's threads saying that there is no need to use rich content in product listing, I don't know if it's better or not having it.

Edited August 20, 2020 by Wartin
add currency

[datakick]

14 hours ago, Wartin said:

I found some forum's threads saying that there is no need to use rich content in product listing, I don't know if it's better or not having it.

I personally believe that product miniatures should NOT have rich content metadata. Especially when you display them on product page - for example if you have list of related products, "customer also bought", or "other products from this category". In this situation, google has hard time to understand what the page is about. From google's perspective, the product page contains multiple products. Sure, one of them is primary, but how should google know this?

The primary goal of google is to understand and interpret the page. Adding too much noise to the page is not helping this, I think. I strongly believe that, in this case, less is more.

I have it implemented like that on my website, and I'm very happy with it. I have zero warnings/errors in search console, and more importantly - my rich data are displayed correctly in search page result.

 

[Wartin]

Good point, indeed Google is not giving errors in product's page in Niara. Just the homepage and categories pages.

Maybe we could edit Niara deleting rich content metadata from product-list-item.tpl then? Now, out of the box, is filling with errors the G's Search Console. On the other hand, I don't know who shows 'related products' or 'customer also bought' in product's page.

 

[cienislaw]

there are modules/templates for that, so we could clean up those too.

[jmeca]

On 20/8/2020 at 17:04, Wartin said:

Hola. Finalmente encontré cómo hacer que esos errores desaparezcan de Google Search Console en Niara. Encontré cómo hacerlo desde el tema de la comunidad, desde github:

https://github.com/thirtybees/community-theme-default/blob/1.1.x/product-list-item.tpl

Entonces, edite /themes/niara/product-list-item.tpl

En la línea 126 ponga:

línea 130:

Y finalmente cierre la etiqueta <div> en la línea 150:

No estoy seguro de si es perfecto, pero Google ahora encuentra 'ofertas' y 'precio' en las listas de categorías.

Aquí está toda esa parte de product-list-item.tpl con líneas numéricas:

 

Espero que sea de utilidad.

Encontré hilos de algunos foros que decían que no hay necesidad de usar contenido enriquecido en la lista de productos, no sé si es mejor o no tenerlo.

Hoy he corregido esto, voy a ver el resultado y te digo. Muchas gracias por compartirlo.

[jmeca]

Error 500 pagina no disponible

[Wartin]

On 9/15/2021 at 8:48 AM, jmeca said:

Hoy he corregido esto, voy a ver el resultado y te digo. Muchas gracias por compartirlo.

Si tenés error 500 podés buscar el código de error y desencriptarlo desde el backoffice. Pero lo idea sería revertir los cambios que hiciste.

De cualquier manera, como se dijo en el hilo, es mejor quitar todo lo relativo a contenido enriquecido de las listas de productos, y que solo estén en los productos por separado. De cualquier manera el buscador entrará en todos los productos.

Saludos!