• Resolved nolandolce

    (@nolandolce)


    Hello all! Thanks in advance for helping. We’ve just moved from AISEO to TFS. For some reason, when sharing an article, facebook works fine (shares the featured image and tags correctly), but twitter doesn’t do either. Instead, it shares the backup image from the system settings, instead of pulling the image selected in editor (that facebook pulls fine). AISEO actually let you choose from multiple image choices for twitter and facebook separately, so that’s already a point against TFS. But, I don’t see why the image selected for both is only working for one? And furthermore, it’s tagging us in twitter as “@rare parenting” instead of “@rareparenting.” Any ideas for both? We like all the other settings for TFS but we’re wondering if we need to move back to AISEO (frustrating!) just to avoid this image problem. Thanks!!

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

Viewing 1 replies (of 1 total)
  • Plugin Author Sybre Waaijer

    (@cybr)

    Hello!

    I noticed Twitter picked up on the favicon, which is not what you selected.

    Please note that Twitter caches URL responses — otherwise, everyone viewing the tweet would hit your site –, and I think they cached the page’s response while you were switching plugins.

    I couldn’t find an issue with the meta tags, so I tested again an hour after seeing the favicon. Twitter has cleared the cache, so the correct image is showing again: No more favicon but a handful of delicious berries.

    I couldn’t find where you’re spotting the space in their tagging mechanism. Could you elaborate on this?

    We only have one input field because both networks’ requirements are almost identical. Unless the agency allows for it (copywriters, artists, and dedicated SMOs employed), there’s virtually no need to have separate image upload fields. It’ll only burden the many people who do not have a large, talented team employed.

Viewing 1 replies (of 1 total)
  • The topic ‘Twitter sharing not using correct image or tag’ is closed to new replies.