Skip Navigation

[Resolved] Redirecting posts to external link- Open Graph data

This support ticket is created 6 years, 1 month ago. There's a good chance that you are reading advice that it now obsolete.

This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.

Sun Mon Tue Wed Thu Fri Sat
8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 - -
13:00 – 17:00 13:00 – 17:00 13:00 – 17:00 13:00 – 17:00 13:00 – 17:00 - -

Supporter timezone: America/New_York (GMT-04:00)

This topic contains 3 replies, has 2 voices.

Last updated by Charles 6 years, 1 month ago.

Assisted by: Christian Cox.

Author
Posts
#1127714
2018-10-15-16-05-www.facebook.com.png

Christian,

I'm hoping you can assist me with Open Graph Protocol for my posts. I redirected my WordPress post URL to external links using the advice you gave me here: https://toolset.com/forums/topic/redirect-each-post-url-to-an-exernal-url-from-a-custom-field/

Now I am trying to share the WordPress posts to Facebook using the social share option beneath each post (seen here: hidden link), but instead of pulling the data from the external link, the data is being pulled from the WordPress post. Is there a way to bypass this so data is pulled from the external link? If I input the WordPress link directly into a Facebook post, Facebook will fetch the correct data (screenshot attached).

Thanks,
Charles

#1127720
2018-10-15-16-09-www.facebook.com.png

Another image is attached showing the correct fetch using the WordPress link itself, fetching the external data.

Thanks,
Charles

#1127738

No, unfortunately Toolset doesn't have any features for managing OpenGraph metadata. A good SEO plugin like Yoast can be configured to help customize metadata content, but I don't know if it has the ability to fetch data from another site.

#1128215

Thanks. I'll dig further into this.

Best,
Chuck