Canonical is already supported by Webflow through custom attributes, ad a rel=canonical to any page, or use custom code on <head> to add it to certain CMS content. However that would be cool to have this option at page level, maybe.
og:url, og:type, fb:app_id are really for Facebook business. The first one prevents fb to scrape further away, type is for how the Like button will be handled and to last one is self explanatory.
What in your use cases absolutely requires that you have the url and type attributes? (genuine question )
Opinion ā that is personal, obviously: The OG tech is really useful and the fb scrapper very effective, but do we have to craft our sites for Facebook? Weāre already bullied by Chrome into having all of our site SSL for no valid reason, letās not feel obliged to follow Facebook rules and clutter our tools.
I am just reacting to tests that say āNeeds fixingā according to FB and other testing tools. My only use case is I want to deploy right for clients and FB is the other channel for many (for now).
I guess as long as the preview card is visible in posts then all is ok ??
I know what you are saying with regard the bullying . But I see most sites have these extra og properties. I guess regardless what I would like is the ability to add dynamic urls or any other site/page attributes via custom code on static pages for when the need arises. That would avoid the feature setting bloat and minimise errors.
In that case, is there another tool that is reporting those fb errors?
That really depend on what youāre doing. if your website is tightly tied with fb things, using an app, using comments etc, you surely want to be fully compliant with them. But thatās really them, fb, a private company, as big as it is. Itās one things to natively support private products such as maps, Youtube etc within the Webflow UI, because they are features, itās another thing to support their custom attributes who donāt bring any feature to your site.
I donāt see how you can be penalized for not supporting them. (only did a quick search though).
I get the same warning message: āThe following required properties are missing: og:url, og:type, fb:app_idasā as @HammerOz despite having the image url set in the Open Graph Image URL.
Iād like to get this warning resolved because it can have a positive effect on advertising costs (lower CPM) on FB. So it really is important, particulary for your ecommerce user base running FB ads. Can you advise if/how we can get rid of this warning please.
I am using a custom collection and even though the below statement is true, FB is used so widely that I feel like it makes sense for it to be optimised there also
The OG tech is really useful and the fb scrapper very effective, but do we have to craft our sites for Facebook?
If this costs my client more as @GrahamCox seems to point out, that also makes me not look so great. Hopefully, this high on someone at Webflowās todo list? At the moment, I donāt have a clue how to manually fix this for every page. I literally showed the SEO section per page to the client as āsee how awesome this platform youāre paying for is!?ā
Iād like to get this warning resolved because it can have a positive effect on advertising costs
How can I verify this? The client is currently on a shoestring budget, so very penny counts (even more directly, the more they save, the sooner/faster I get paid). Kinda lame if I have to tell them āoh that great platform I told you to use, yeah sorry it costs you higher costs per impressions for no reason.ā :-/
You are right. I was having a minor cut webflow some slack moment, but the whole OG & twitter card setup needs an overhaul. Webflow need to fix this. It was half baked years ago.
I get the same error in FB debugger ā and also having issues on Twitter (see below). Sharing on iMessage is also missing info - guessing this is also related, since my static pages are pulling in fine?
Not sure if this helps anyone elseā¦ but I figured out my issueā¦
My OG images were SVGsā¦ Facebook didnāt like that. Once I updated to PNGs that were at least 200x200, then it all worked out well!
I also added this code into the head of my CMS page to help Facebook grab the image more quickly and reliably on the first try. <meta property="og:image:width" content="[your image width]" /> <meta property="og:image:height" content="[your image height]" />
This resolved the issue for me! Personally, Iād prefer to paste and delete the url, so that the image/link is generated and the text in the post looks clean, but oh well. Just dropped the link at the bottom of the post and I could run my ad.
Thank you! Iāve been trying to figure this out for like 3 hours as to why they wouldnāt show up. Wish Webflow had specified that in Open Graph Settings.