WPIntell

Source evidence

Problematic attribute handling

Product Feed Manager for WooCommerce – CTX Feed – Support 220+ Shopping & Social Channels · review · 2025-11-29T17:54:00+00:00

complaintsentiment
mediumseverity
0.72relevance
0replies
Evidence linked to opportunitycommercial context

Proof Health

Open evidence

Commercial opportunities need traceable source links before they are treated as build-worthy.

5 / 26 rows with source links

19.2% of this page's analysis has direct source links.

0 build-decision rows missing links

0 rows here require auditable proof before promotion.

21 rows with no attached evidence

0 rows have source counts but still need direct links.

Conversation

review · 3 stars
mirons unresolved
The output of all all of Google’s attributes in an xml file are cluttered as it is when using this plugin, as this plugin doesn’t remove empty attributes in products where the attributes are empty. But even if we ignore that and keep the empty tags, the real problem I found was specifically with the handling of the Google’s attribute product_detail. When submitting a feed to Google Shopping, I rely heavily on the Google attribute product_detail, as it allows to submit a great amount of custom attributes. Unfortunately, this plugin doesn’t output the product_detail attribute in a way that complies with Google instructions. The attribute product_detail includes 3 sub-attributes: section_name (optional), attribute_name (required), attribute_value (required). The input mechanism for product_details in this plugin is not very good and the output it provides is problematic. When using xml, if certain products don’t have values for certain attributes that use product_detail, instead of omitting the attribute altogether or, for the very least, omitting the attribute_name, the plugin outputs the actual attribute name while leaving it hanging without a value. For example (and I’ve replaced the html tags with parentheses): (g:product_detail) (g:attribute_name)Resolution(/g:attribute_name) (g:attribute_value/) (/g:product_detail) In the case of outputting the feed in a tsv format it’s even worse, as the product_detail column would just include the specific attribute name without any context to what it is or to what Google should do with that word, whether it’s a section_name, attribute_name or an attribute_value. And when the tsv file does have a product that has both an attribute_name and an attribute_value, but not a section_name (as it’s optional), it incorrectly outputs it like this: Resolution:4k Instead of the way Google instructs to output it in the tsv format, which is to start with a colon(:) to indicate there is no section_name. Like this: :Resolution:4k Other than that, if you don’t need to use the Google Shopping feed, the plugin does offer some extra options for feed customization.

Comments

0 shown

No comments were stored for this source.