• Resolved crigdon

    (@crigdon)


    This problem exists for all pages on this site. The meta tags appear correct but whether you use the share link on the site, or try to share direct on FB, the image, title and description are not used.

    There must be a legitimate issue as the Sharing Debugger also shows an empty/plain sharing dialog. But the debugger isn’t given me any helpful info. It sometimes shows a 302, which I don’t understand as there is no redirect on the site. Refreshing the scrape sometimes shows that the og:image is corrupt, which also doesn’t seem to be a legitimate issue.

    Any and all help is very appreciated.

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

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Author JS Morisset

    (@jsmoriss)

    Here’s the image being used:

    
    <!-- og:image:1 --><meta property="og:image" content="http://pikespeakharleyownersgroup.com/wp-content/uploads/2017/11/50-ways-to-save-your-life.png"/>
    <!-- og:image:1 --><meta property="og:image:width" content="598"/>
    <!-- og:image:1 --><meta property="og:image:height" content="308"/>
    

    You have this meta tag in your header, which is not from WPSSO and conflicts with the above – you should remove it.

    
    <meta property="og:image:type" content="image/jpg">
    

    Have you checked the FAQs? This one might help too. 😉

    https://wpsso.com/docs/plugins/wpsso/faqs/why-does-facebook-show-the-wrong-image-text/

    js.

    Thread Starter crigdon

    (@crigdon)

    Thank you for the reply. That line was in there from some testing, I removed it but it was not causing the issue.

    Also the issue isn’t that the wrong image is displayed. The issue is that no image is displayed and most pages don’t display a title or description either.

    Thanks again for any help you may have.

    Plugin Author JS Morisset

    (@jsmoriss)

    Please fix this issue so the Facebook crawler can read your webpage:

    https://developers.facebook.com/tools/debug/og/object/?q=http%3A%2F%2Fpikespeakharleyownersgroup.com%2F50-ways-save-life%2F

    
    Critical Errors That Must Be Fixed
    Could Not Follow Redirect
    URL requested a HTTP redirect, but it could not be followed.
    
    Warning
    Errors That Must Be Fixed
    Circular Redirect Path	Circular redirect path detected (see 'Redirect Path' section for details).
    

    js.

    Thread Starter crigdon

    (@crigdon)

    The error states

    The following will be treated as a redirect by the crawler:
    A HTTP redirect
    A <link rel=”canonical” href=”..” /> tag
    A <meta property=”og:url” content=”..” /> tag

    However there is no http redirect.

    The canonical and og:url are both added by this plugin? Is it an issue that they are the same value? I didn’t think that was a problem.

    Plugin Author JS Morisset

    (@jsmoriss)

    
    $ wget -v 'http://pikespeakharleyownersgroup.com/50-ways-save-life/'
    --2017-11-28 02:22:38--  http://pikespeakharleyownersgroup.com/50-ways-save-life/
    Resolving pikespeakharleyownersgroup.com (pikespeakharleyownersgroup.com)... 23.229.184.70
    Connecting to pikespeakharleyownersgroup.com (pikespeakharleyownersgroup.com)|23.229.184.70|:80... connected.
    HTTP request sent, awaiting response... 302 Found
    Location: /50-ways-save-life/ [following]
    
    Thread Starter crigdon

    (@crigdon)

    Hmm. I get the following:

    wget -v ‘http://pikespeakharleyownersgroup.com/50-ways-save-life/&#8217;
    –2017-11-27 20:09:52– http://pikespeakharleyownersgroup.com/50-ways-save-life/
    Resolving pikespeakharleyownersgroup.com… 23.229.184.70
    Connecting to pikespeakharleyownersgroup.com|23.229.184.70|:80… connected.
    HTTP request sent, awaiting response… 200 OK
    Length: 11188 (11K) [text/html]
    Saving to: ‘index.html’

    Sounds like possibly a DNS issue. I’ll keep looking

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Meta appears correct but shared content is empty’ is closed to new replies.