I'm not sure if this is a bug or not, but...
On WordPress SEO's "Social" page is a field called "Description" for the Facebook frontpage settings. However, when I enter some text in there, it does not appear anywhere in the page source HTML.
I imagine it's supposed to be used as the content of the "og:description" field, but this field just shows the exact same text as the meta description.
So either I'm misunderstanding the purpose or behaviour of this "Description" field, or else it's not working as it should. :)
Thank you for reporting. I suspect this might have something to do with settings not being saved in their proper place. v1.5 of WP SEO will fix this.
Just updated to 1.5.2 and this issue doesn't appear to be resolved. The "og:description" field of the front page still just contains the same text as the "Meta Description" field of the front page, even though I have different text entered on the SEO->Social page for the Facebook front page description.
To be honest I wonder what is the purpose or point of having the Frontpage settings "Image URL" and "Description" fields on the SEO->Social page in the first place. Both of those values can be edited directly from the Social tab of the WordPress SEO meta box when editing the front page itself. Why do we need separate fields for these two values, at SEO->Social?
(I hope you can follow all that!) ;)
Ah! That actually explains it.... the Facebook OG description and image from the Social page are only used when you are not using a static front page, i.e. when your front page is your blog. When you are using a static front page, the data will be taken from the page as you surmised.
@jdevalk May be it should be made a little clearer in the options page text that those two fields will only be used for non-static front pages ?
Aha - that kinda makes sense! Yes, in that case, it would definitely help to have some kind of explanatory text to make this clearer! ;)
@jdevalk Actually on second thought, we might as well not show those fields when the user has chosen to use a static frontpage. Implemented in pull request #751.