You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
data.image returns https://cdn.loom.com/assets/img/og/loom-banner.png, whereas if I paste the same URL on opengraph.xyz, you'll see the og:image property returns https://cdn.loom.com/sessions/thumbnails/473fad25ebd24b5ea8091503253dfecf-1650653926695.gif.
Is this expected behavior for dynamic routes or is there a way to properly parse OG images for sites like Loom?
open-graph-scraper returns static placeholder:
iMessage, FB tools, and opengraph.xyz returns correct image for URL:
Thanks in advance for your help, this is my first time using your API :) hopefully this is just a pebkac error :)
The text was updated successfully, but these errors were encountered:
thanks for the reply @jshemas -- but most of the OG generators don't reference the static HTML, for example, if you paste that loom video URL into iMessage or the OG checker that I linked above that Meta provides, you'll see it loads the dynamic OG Image. Lots of services like Vercel have OG runtime support. Does open-graph-scraper support dynamic runtimes?
I'm trying to get open-graph-scraper to return OG images for a Loom video.
E.g.: if I call the below function with the URL
https://www.loom.com/share/473fad25ebd24b5ea8091503253dfecf
,data.image
returnshttps://cdn.loom.com/assets/img/og/loom-banner.png
, whereas if I paste the same URL on opengraph.xyz, you'll see theog:image
property returnshttps://cdn.loom.com/sessions/thumbnails/473fad25ebd24b5ea8091503253dfecf-1650653926695.gif
.Is this expected behavior for dynamic routes or is there a way to properly parse OG images for sites like Loom?
open-graph-scraper
returns static placeholder:iMessage
,FB tools
, andopengraph.xyz
returns correct image for URL:Thanks in advance for your help, this is my first time using your API :) hopefully this is just a pebkac error :)
The text was updated successfully, but these errors were encountered: