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

    (@algoritmika)

    Hi @omaco,

    I’ve just checked the source of your page, and I can see that EAN is included in the product structured data – this means that our “Product structured data” option (in “WooCommerce > Settings > EAN > General”) is enabled, as it should be. However, I can see that the key there is ean which is not what Google expects. As I understand, you’ve disabled our “Product structured data > Automatic key” option and have set the “Product structured data > Custom key” option to ean, correct? If that’s the case, you need to either re-enable our “Automatic key” option or set the “Custom key” option to gtin (or gtin13).

    Please give it a try and let me know if that solves it?

    Thread Starter Yvette

    (@omaco)

    Hi,
    Fantastic to get help from Plugin Author.

    Do I understand it correctly that I should use:
    1/ In WooCommerce=>Setting=>General=>Type Use Automatic (EAN-13, UPC-A, EAN-8, ISBN-13, JAN)
    2/ In WooCommerce=>Setting=>General=>Product structured data Use Automatic key and have emty field in the Custom key field (before it was written gtin)

    FYI: I tried to run a new update on GSC to get the warnings away, but I still get the same warning message.

    Plugin Author Algoritmika

    (@algoritmika)

    Hi @omaco,

    Not exactly. Here is what you need to do:

    1. You need to check the “Enable” checkbox in “WooCommerce > Settings > EAN > General > Product structured data”.

    2. You need to check the “Automatic key” checkbox – again in “WooCommerce > Settings > EAN > General > Product structured data”.

    As for the “Custom key” option (once again in “WooCommerce > Settings > EAN > General > Product structured data”) – it’s not really important what’s set there, as long as the “Automatic key” checkbox (from my point nr. 2) is enabled.

    Hope this helps. Please let me know if there are still any issues.

    Thread Starter Yvette

    (@omaco)

    Hi,

    Implemented. Still get the same message from Google Search Console. Went to server (one.com) and refreshed database.

    How can I make Google understand that I have implemented nr 1 and 2 from above?

    Plugin Author Algoritmika

    (@algoritmika)

    Hi @omaco,

    Yes, you are right – I’ve checked the sources of your pages, and I can see that EAN is still not in the product structured data. Could you please try temporarily disabling the “Rank Math SEO” plugin to see if that fixes the issue?

    Plugin Author Algoritmika

    (@algoritmika)

    Hi again @omaco,

    Nevermind my previous request – I’ve just tested it on my server, and I can confirm that there is a compatibility issue with the Rank Math SEO plugin. I’m already working on fixing it – will release a new plugin version in a couple of hours or so.

    Plugin Author Algoritmika

    (@algoritmika)

    @omaco,

    Ok, I think I was able to fix it. Please update the plugin to the latest version 3.7.0 (released just a couple of minutes ago). Then you need to enable the new checkbox I’ve added – “Rank Math SEO” plugin – it’s in “WooCommerce > Settings > EAN > General > Product structured data”.

    Please give it a try and let me know if it’s ok now?

    Thread Starter Yvette

    (@omaco)

    Woh! Soo good service. And I think it works. Enabled the checkbox. And in GSC I was now able to get the preview validation accepted, so now pages are being processed by Google and will hopefully be accepted so no more warnings.

    Plugin Author Algoritmika

    (@algoritmika)

    Happy to hear it’s solved ??

Viewing 9 replies - 1 through 9 (of 9 total)
  • The topic ‘Warning No global identifier provided (e.g., gtin, mpn, isbn)’ is closed to new replies.