Viewing 5 replies - 1 through 5 (of 5 total)
  • Thread Starter Jeff Daigle

    (@jeff-daigle)

    This is my opening head tag, per the plugin’s instructions:
    <head <?php do_action( ‘add_head_attributes’ ); ?>>

    Plugin Author JS Morisset

    (@jsmoriss)

    Your meta tags are the same for the Facebook and Pinterest crawlers:

    $ get-og-images.sh https://dbdc.us/articles/case-study-christopher-taylor-timberlake-fine-art-jewelry/
    
    Checking images from https://dbdc.us/articles/case-study-christopher-taylor-timberlake-fine-art-jewelry/
    
    Facebook user-agent:
    
     <meta property="og:image:secure_url" content="https://dbdc.us/wp-content/uploads/2016/05/cttj-header-600x315.jpg"/>
     <meta property="og:image" content="https://dbdc.us/wp-content/uploads/2016/05/cttj-header-600x315.jpg"/>
     <meta property="og:image:width" content="600"/>
     <meta property="og:image:height" content="315"/>
    
    Pinterest user-agent:
    
     <meta property="og:image:secure_url" content="https://dbdc.us/wp-content/uploads/2016/05/cttj-header-600x315.jpg"/>
     <meta property="og:image" content="https://dbdc.us/wp-content/uploads/2016/05/cttj-header-600x315.jpg"/>
     <meta property="og:image:width" content="600"/>
     <meta property="og:image:height" content="315"/>

    I would guess you’re using a caching plugin, and have not excluded the Pinterest crawler, right? Have a look at the “Caching Plugins and Services” section of the Setup Guide (under the SSO menu). ??

    js.

    Thread Starter Jeff Daigle

    (@jeff-daigle)

    Why did you mark this as resolved? I think I’m the one who should be the judge of that ??

    I added all those user agent strings as a pass-through group for W3 Total Cache and still have the problem, so this is NOT resolved yet.

    edit: I also tried disabling W3 Total Cache and my CDN (CloudFlare) entirely, and the problem still persists.

    Sometimes a picture is worth 1000 words. Here is a screenshot of the “Select Media” tab showing the Pinterest/Rich Pin settings for the post:
    https://i.imgur.com/J32AOkG.png

    Note the URL of the image I want to use for a rich pin: https://dbdc.us/wp-content/uploads/2016/05/cttjewelry-case-study-pinterest-image.jpg

    And here is a screenshot from the “Head Tags” tab, showing the Pinterest-specific tags I expect to see in the head of the page:
    https://i.imgur.com/PVrseIO.png

    However, they are not there, and without them there is no way for Pinterest to know about the special image I want to use when pinning this page. In fact, this is what I get when I pin the page:
    https://i.imgur.com/wj9q7Kz.png

    So again: how do I get the correct image and the Pinterest meta tags (pinterest:image:secure_url, pinterest:image, pinterest:image:width, pinterest:image:height, pinterest:image:cropped; pinterest:image:id) to be inserted properly?

    Thanks–

    Plugin Author JS Morisset

    (@jsmoriss)

    The pinterest:image:* meta tags are an internal meta tags, meant only to show the values that will be used for the og:image:* meta tags when the pinterest crawler is detected. The problem is almost certainly an issue of caching — do you use a front-end service like CloudFlare or another? If disabling W3TC did not solve the problem (you must check using a Pinterest user-agent value in your browser), then this would point to a second layer of caching (though this is not optimal for performance, it happens on occasion). If you’d like to disable W3TC again, I could have a second look.

    js.

    Thread Starter Jeff Daigle

    (@jeff-daigle)

    My post https://www.ads-software.com/support/topic/pinterest-rich-pin-image-not-working?replies=4#post-8455743 indicated that disabling W3 Super Cache and CloudFlare made no difference.

    I ended up resolving the problem on my own. Turns out the Jetpack share buttons aren’t compatible with WPSSO because they send the sharing data to Pinterest using a AJAX request instead of opening Pinterest’s dialog in a new window like WPSSO SSB. Thus they don’t trigger WPSSO’s crawler detector because the Pinterest crawler doesn’t reload the whole page.

    Not sure if you’ll want to change this behavior since it encourages adoption of WPSSO SSB, but you might want to add a FAQ item about it so that people don’t end up spending a lot of time troubleshooting this all over again.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Pinterest Rich Pin Image Not Working’ is closed to new replies.