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
Do you have any insight on if prefix="og: http://ogp.me/ns#" is required in the markup to specify a page using open graph? It shows this on http://ogp.me/ (it includes it in the tag but from some research it has the same effect as assuming all of the meta data is within the head).
I couldn't really find a clear answer if it's required or just suggested, and i looked through several news websites for example that do seem to include this prefix markup. If you have any insight I'd be interested to know, or if you think this should be implemented, appreciate it.
The text was updated successfully, but these errors were encountered:
Apparently it is required. At least for LinkedIn. I couldn't get next-seo to make the OG image show up in LinkedIn. This StackOverflow answer tells me to add the prefix to the meta tag. However, I just learned that setting it as an attribute on the html tag works as well:
Do you have any insight on if prefix="og: http://ogp.me/ns#" is required in the markup to specify a page using open graph? It shows this on http://ogp.me/ (it includes it in the tag but from some research it has the same effect as assuming all of the meta data is within the head).
I struggle to find a clear answer, I am basically referring to this question: https://stackoverflow.com/questions/48933419/opengraph-prefix-in-header-necessary and if next-seo needs to include this prefix, also depending on the type specified it would include article: http://ogp.me/ns/article# , or profile, book, etc.
I couldn't really find a clear answer if it's required or just suggested, and i looked through several news websites for example that do seem to include this prefix markup. If you have any insight I'd be interested to know, or if you think this should be implemented, appreciate it.
The text was updated successfully, but these errors were encountered: