Unable to display image on Twitter Card

@dubkei

Could you please edit your robots.txt to the optimized rule as given here and check if this resolves the issue?

Be sure to clear your browser, server and plugin cache if any applicable?

My robots.txt file is

User-agent: Twitterbot

Allow: /images

This should allow Twitter to access the image on the site, right?

I cleared browser, servers, and plugin cache and still same issue.

Hello @dubkei,

We can’t say what your custom directive in the robots.txt should do/not do. But what you have currently doesn’t meet our recommendations. Also, the warning in the deprecated Twitter card validator points to the same issue we pointed out:

WARN: ?The image URL https://9jf6a2.p3cdn1.secureserver.net/wp-content/uploads/2023/02/IMG_1908-2.png specified by the ‘twitter:image:src’ metatag may be restricted by the site’s robots.txt file, which will prevent Twitter from fetching it.

So you may want to address that first.

A bit confused by the recommendations page…What specifically do I need to change that pertains to what my current robots.txt is?

Hi @dubkei ,

Right now, the image for the meta tags is outputted from another domain on your website. ie; from https://9jf6a2.p3cdn1.secureserver.net. So the Twitter image is outputted as the following:

<meta name="twitter:image" content="https://9jf6a2.p3cdn1.secureserver.net/wp-content/uploads/2023/02/Untitled-1.png?time=1682247480" />

When an image is added from another domain using CDNs, the respective domain robots.txt file will be checked by the Twitter bot; in your case the domain https://9jf6a2.p3cdn1.secureserver.net is added with Disallow directive, and due to that the Twitter bot is not able to fetch the image. So we recommend you remove the Disallow from the robots.txt of the domain from which the image is added on your website, to help the Twitter bot to crawl your page effectively.

We hope this helps you in the right direction.

This thread was marked resolved due to a lack of activity, but you’re always welcome to re-open the topic. Please read this post before opening a new request.