Profile: pumpkinpip

Hi, I downloaded the latest zip from my account, then completely uninstalled, deleted and reinstalled the plugin, but am still seeing:

NEW style girl's ankle strap pump with large double bow on the front, strap with metal buckle, leather lining with instep support, tunit sole, made in Spain with Spanish patent leatherAvailable in lots of other colours.Upper 100% soft patent leatherInner lining 100% natural leatherOutsole synthetic tunitClosure strap and buckleHeel height 0.5cmMade in Spain

Thank you.

I know   is a wide space, but note that it has removed the period (.) before it.

Also can you see what I mean by how words are merged together? It makes sense to add a space where HTML is stripped to prevent words from separate sentences or bullet from merging.

Thank you.

Please see the "Variants grouped using 'inProductGroupWithID'" section on https://support.google.com/merchants/answer/6386198 - would this be the correct way to (optionally) render products that have Product Attributes that vary with size? (i.e. inProductGroupWithID is set to the Product table ID for each Product Attribute)

Please could an update be made to improve the generation of the "description" field when it strips out HTML so words are not combined, for example: add a space wherever HTML is stripped out (then reduce all multiple spaces to one).

For example, here is a live example of a product's description:

<p>NEW</strong> style girl's ankle strap pump with large double bow on the front, strap with metal buckle, leather lining with instep support, tunit sole, <strong>made in Spain with Spanish patent leather</strong>.&nbsp; <strong>Available in lots of other colours.</strong></p>
<ul>
<li>Upper 100% soft patent leather</li>
<li>Inner lining 100% natural leather</li>
<li>Outsole synthetic tunit</li>
<li>Closure strap and buckle</li>
<li>Heel height 0.5cm</li>
<li><strong>Made in Spain</strong></li>
</ul>

Here is how it is rendered in the Rich Cards JSON:

NEW style girl's ankle strap pump with large double bow on the front, strap with metal buckle, leather lining with instep support, tunit sole, made in Spain with Spanish patent leatherAvailable in lots of other colours.Upper 100% soft patent leatherInner lining 100% natural leatherOutsole synthetic tunitClosure strap and buckleHeel height 0.5cmMade in Spain

See the words above that are combined: leatherAvailable, "colours.Upper", "leatherInner", "leatherOutsole", "tunitClosure", "buckleHeel" and "0.5cmMade".

I don't know what implications there might be for a description where the words are merged like this, but it can't be good.

Also in the above example, note how the '.' is incorrectly stripped out within "....</strong>.&nbsp; <strong>...."

NOP v4.50.2

Thank you.

Yes, if you have lots of products that can go out of stock at any time, or that change price (e.g. sales/repricing), it is vital. Otherwise, if Google detects a mismatch, e.g. a product in your feed that goes out of stock during the day, or you put a sale on, the products can be disapproved by Google and it can take a while to get them back online when needed, and if it happens too frequently, your account can be suspended (we only just managed to avoid this).

This Google page explains it: https://support.google.com/merchants/answer/3246284

We have thousands of products, many with low stock, and due to disqualifications, we learned to ensure the structured data markup worked properly, as as we are moving to NOP, we are going to need it.

It might be feasible to do without it if your products don't go out of stock or change prices frequently (and you can force a refresh of the feed after every change), but that is not practical with a lot of products.

Thank you for looking in to this. I understand the solution you mention, but unfortunately with over 1,000 products, most with multiple variants (sizes), some with as many as 10, that would make it very difficult for customers to use the website as they would sometimes see an entire page full of the same product.

I can understand it isn't a problem for retailers where there are no variants or only a few, but with apparel - clothes and shoes, it is not practical to do it that way. Do you have any customers selling apparel who use this plugin?

Is it possible to add an option to the plugin to activate a mode that will automatically render the relevant JSON for attribute combination products? Without this I am concerned that we won't be able to sell on Google Shopping as we are able to do on the current non-NOP website at present.

Thank you.

Kind regards,

Andre

It is done by simply nesting multiple "offers" inside a single "product", each offer being one attribute combination.

The following Google page discusses multiple offers on a page (see under "Getting started"): https://support.google.com/merchants/answer/7331077?hl=en-GB

Here is a website page (not NOP) that uses Microdata with multiple offers successfully with Google Shopping: https://bit.ly/3lZeL73.  Each "offer" has the GTIN, price etc, and Google Shopping/Google Merchant Centre regularly crawls the page to automatically update price and availability for each size of the product that is available (https://support.google.com/merchants/answer/7050465?hl=en-GB).

The plug in would need to work with both products with attribute combinations and products without (on the same website).

I have today purchased your "Rich results" plugin (multiple domains) along with another plugin of yours, but am hopeful that you can upgrade it to cater for attribute combinations - that is vital for my website (the non-NOP one I mentioned above) which I am working on migrating to NOP, due to the products being advertised on Google Shopping. Thank you.

The JSON this plugin renders for products with attribute combinations uses AggregateOffer and lists all GTINS in the combinations and the high and low price.

As explained on https://technicalseo.com/insights/blog/product-schema-google-merchant-vs-google-search/ this is not suitable for Google Merchant Centre/Google Shopping where the product schema for every combination (variant) is needed.

Could this be included? If so I would not hesitate to purchase the multi-domain license. Thank you.

I am evaluating the trial version of NopFeedManager for use on Google Ads and Facebook ads with apparel/clothing/footwear products for children

We have some clothing products which have a Product Attribute of 'Age' (e.g. 3 years, 4 years) and some shoes with a Product Attribute of "Shoe Size" (e.g. EU18, EU19, EU20).

No products have both Product Attributes at the same time.

I need to send separate products for each Age or Shoe Size (combination) to Google and Facebook and populate the <g:size> field for Google and "Size" column for Facebook with whatever value that combination has been given.

In FeedManager I can only define the "Size" attribute to be ONE attribute at a time, e.g. "Product attribute: Age" or "Product attribute: Shoe size".

Therefore my questions is... do I have to create 2 separate feeds to Google and 2 separate feeds to Facebook? (e.g. the 2 Google feeds will be feed 1 a feed containing only products with the "Shoe Size" attribute, and feed 2 containing all other other products (some products don't have Attribute Combinations at all, so need to be included).

Or is there a better way to achieve this?

Thank you.