mpn issue in schema markup

#199737
  • Resolved Alessandro
    Rank Math free

    mpnHi, from a while i’ve an error in google testing for “mpn”

    Thing non è un tipo di target considerato valido per la proprietà mpn.

    @type

    Thing.

    How to change this or eliminate “mpn”? Thanks much

Viewing 7 replies - 1 through 7 (of 7 total)
  • Hello,

    Thanks for contacting us and sorry for any inconvenience that might have been caused due to that.

    Can you please share some of the affected URLs in the sensitive data section so we can check and assist you further?

    We really look forward to helping you.

    Hello,

    I have updated the sensitive data as requested. Can you please check further?

    Thank you.

    Hello,

    Thanks for getting back.

    I tried to check your product with Google’s Rich Results Test but due to some issue with your schema code, this tool is not able to test your page:

    I was able to check it with the Structured Data Testing tool and there is an error with your MPN. It seems like some plugin or your theme is causing some issues with Rank Math’s schema code as our plugin doesn’t output the MPN field like this:

    To determine which plugin is causing the conflict, please follow this troubleshooting guide:
    https://rankmath.com/kb/check-plugin-conflicts/

    Let us know if you find the culprit. We really look forward to helping you.

    Hi, it’s quite hard to check wich plugin at this time but i’ve no other plugin apart Stamped that use schema..

    In fact Stamped support say to me that problem maybe from your plugin from these line of code but that i can’t find where it is

    add_filter( ‘rank_math/snippet/rich_snippet_product_entity’, function( $entity ) {

    global $post;

    $entity[ ‘@id’ ] = get_the_permalink( $post ) . ‘#product’;

    $entity[ ‘mpn’ ] = isset( $entity[ ‘brand’ ] ) ? $entity[ ‘brand’ ] : ”;

    return $entity;

    });

    Hello,

    Thank you for keeping in touch with us.

    We might need to take a closer look at the settings. Please edit the first post on this ticket and include your WordPress login in the designated Sensitive Data section.
    Sensitive Data Section

    It is completely secure and only our support staff has access to that section. If you want, you can use the below plugin to generate a temporary login URL to your website and share that with us instead:

    https://wordpress.org/plugins/temporary-login-without-password/

    You can use the above plugin in conjunction with the WP Security Audit Log to monitor what changes our staff might make on your website (if any):

    https://wordpress.org/plugins/wp-security-audit-log/

    We really look forward to helping you.

    Hello,

    I have updated the sensitive data as requested. Can you please check further?

    Thank you.

    Hello,

    Thanks for getting back. Sorry for the delay and any inconvenience that might have been caused due to that.

    I checked and noticed that you were using an old version of Rank Math. I have updated your WordPress and Rank Math to the latest version. After that, I was able to check your site with the Rich Results Test and the Product schema added by Rank Math is working fine and there is no error related to MPN.

    So you can ignore the results of the structured data test as that tool is outdated and Google no longer recommends using that. You can check your site here with the Rich Results Test: https://search.google.com/test/rich-results

    However, your page is still not eligible for rich results as the schema added by Stamped plugin is throwing an error: Missing field ‘name’

    Please contact their support team and get their help in resolving the issue. Also, I noticed that you are using old versions of most of the plugins on your site. I would recommend updating all of the plugins to the latest version to avoid any conflicts and performance issues.

    Hope this helps. Let us know if you need any further assistance.

    Hello,

    Since we did not hear back from you for 15 days, we are assuming that you found the solution. We are closing this support ticket.

    If you still need assistance or any other help, please feel free to open a new support ticket, and we will be more than happy to assist.

    Thank you.

Viewing 7 replies - 1 through 7 (of 7 total)

The ticket ‘mpn issue in schema markup’ is closed to new replies.