• Resolved rcanny

    (@rcanny)


    We have a mixture of products with GTIN buy many that only have MPN (manufacturer part number). I set up the plugin to use MPN, but the structured data result is placing the data into the GTIN field, not MPN. See snip below:
    description
    Medium duty roller conveyor by Ultimation. 27″ wide x 24″ BF x 10′ Long. Contact us to quote different sizes. Fast delivery on standard sizes.
    sku URS19G24-6-10V
    gtin UIRS19G24-6-10V
    productID retailer_item_id:162516
    brand
    @type
    Brand
    name

    Anyone know how to use this plugin to get the data to show up as MPN? Google issues a warning that entering an MPN data into a GTIN field is wrong.
    Thanks!

    The page I need help with: [log in to see the link]

Viewing 9 replies - 1 through 9 (of 9 total)
  • Plugin Author Emanuela Castorina

    (@kreamweb)

    Hello
    you should select MPN inside the dropdown “Structured data product”
    https://pasteboard.co/J5t3ONG.png
    Then Google will see:
    https://pasteboard.co/J5t3AtR.png

    Thread Starter rcanny

    (@rcanny)

    Hi. Thanks for the reply! Yes, that’s what I did, and that’s what I expected to see. But when I do that for both a simple product and for a variable product, it’s getting added to the GTIN field, not the MPN field

    Here’s the new one I just made:
    https://pasteboard.co/J5t8cuM.png

    And here’s my settings where I have selected mpn:
    https://pasteboard.co/J5t9XhT.png

    I am also using WPSSO Schema JSON-LD Markup plugin. Maybe this is causing the problem?
    Thanks very much for your help.

    Thread Starter rcanny

    (@rcanny)

    Information from the other WPSSO plugin which is
    https://wpsso.com/docs/plugins/wpsso/installation/integration/woocommerce-integration/
    says:

    “If you use the Product GTIN (EAN, UPC, ISBN) for WooCommerce or WooCommerce UPC, EAN, and ISBN plugin, the “Product GTIN Attribute Name” and the “Product GTIN Custom Field” options in WPSSO Core Premium will be disabled (as the supported plugin becomes the source of all product GTIN information).”

    However maybe they are not or maybe they are rearranging the structured data from your GTIN plugin?

    Thread Starter rcanny

    (@rcanny)

    H Emanuela,
    Yes, that is the issue. When I turn off the WPSSO plugin, then your plugin works correctly for mpn.

    https://pasteboard.co/J5tfhMz.png

    I’ve turned off WPSSO Schema JSON-LD Markup (Premium) for the moment and will refer the developer of it to this thread.

    Thank you!

    Plugin Author Emanuela Castorina

    (@kreamweb)

    ok! let me know!

    JS Morisset

    (@jsmoriss)

    FYI – The WPSSO Core Premium plugin was reading the ‘_wpm_gtin_code’ metadata value into the Schema ‘gtin’ property.

    As of WPSSO Core Premium v7.1.0 (released this morning), the ‘wpm_pgw_structured_data_field’ setting value is now checked to assign the ‘_wpm_gtin_code’ metadata value to the correct Schema property.

    You can click the “Check Again” button on the WordPress Dashboard > Updates page or the “Check for Updates” button from the SSO > Tools and Actions page to get the latest Premium update information and refresh the local update cache immediately.

    js.

    Thread Starter rcanny

    (@rcanny)

    JS and Emanuela,
    Thanks very much. Confirming that with the update to v7.1.0 that everything is now working as it should. MPN is in the correct location and no errors.

    https://pasteboard.co/J5twZpL.png

    Thanks all. Resolved 🙂

    Scott

    (@kitgrow)

    Would just like to add I just found the “Schema & Structured Data for WP & AMP” plugin was also disrupting my schema data and GTIN from being passed correctly. Once removed all is back to normal.

    Plugin Author Emanuela Castorina

    (@kreamweb)

    @kitgrow
    I’ve tried that plugin, it removes the WooCoommerce Structure Data to add its data , for this reason you don’t see the GTIN code.

Viewing 9 replies - 1 through 9 (of 9 total)
  • The topic ‘Using MPN’ is closed to new replies.