Facebook - meta tags (open chart)

In an update to my previous question, I got a new warning from the facebook debugger.

  • Inappropriate Parser metadata The parser result for this metadata does not match the input metadata. This was likely caused by an unexpected data order, with multiple values ​​being specified for a property that expects only one value, or property values ​​for that property are incompatible. Here are the input properties that were not visible in the parsed result: 'og: image: url, og: site_name, fb: admins'

  • og: the image cannot be loaded or is too small og: the image is not defined, cannot be loaded, or is not large enough. Please define the selected image using the og: image meta tag and use an image that is at least 200x200px and available from Facebook. The image Http: // (MY_WEBSITE) /images/mylogo.png will be used instead.

  • Trying Frozen Title Change It looks like you are trying to change the og: title property from (my_wesbite_name) to (my_wesbite_name_plus_tagline). If so, you are not allowed this object because too many actions have been posted against it.

these are my tags:

    <meta property="og:title" content="Myname - Best Products in Town">
    <meta property="og:type" content="Product">
    <meta property="og:url" content="http://www.mybestproducts.com/">
    <meta property="og:site_name" content="Myname">
    <meta property="og:description" content="Selling the best products">
    <meta property="og:image" content="images/mylogo.png">
    <meta property="og:image:width" content="550">
    <meta property="og:image:height" content="550">

      

Questions:

Oh 1. I have no idea what this means

About 2: As shown in my meta tags, I have defined mylogo.png. I need to put the whole url in order to be recognized.

About 3. I need an explanation for this too.

+3


source to share


1 answer


Relative to 1:

og:type

should be a website in your case, i think instead of a product.

Cm

Regarding 2:



You need to pass the absolute path for the property og:image

instead of the relative one.

Cm

Regarding 3:

I think it is caused by wrong og:type

+2


source







All Articles