Open graph can resolve relative url?

html facebook-opengraph meta-tags meta

45,124

Solution 1

Documentation have nothing about it, but relative URLs will not work, only full URL including scheme works.

As long as only full URLs supported you may convert relative to absolute url using URL.Content method (as suggested in What is the equivalent to Page.ResolveUrl in ASP.NET MVC?)

NOTES:

In 2012 in old Facebook bug tracker this bug was closed stating this is "by design" http://developers.facebook.com/bugs/192471680829756
If you look into http://ogp.me/ns RDF schema (in Turtle) og:image specified as ogc:url which have next description:

A string of Unicode characters forming a valid URL having the http or https scheme.

Solution 2

I set up an og:image tag on my website with a relative url, and even though facebook reports an error like this :

Object at URL 'http://***/' of type 'website' is invalid because the given value 'preview.png' for property 'og:image:url' could not be parsed as type 'url'.

on https://developers.facebook.com/tools/debug/og/object/, the image shows up in the preview.

So I guess this is kind of supported, at least on facebook.

45,124

ebattulga

using Stackoverflow.com; using Superuser.com; using Google.com; namespace dotnet{ public class Developer { public static Developer ebattulga; public void Ask(string question){...} } }

Updated on July 08, 2022

Comments

ebattulga almost 2 years
I'm adding Facebook Open Graph meta tag to my site. For example:
```
<meta property="og:image" content="../images/aa.jpg"/>
```
Does Open Graph take relative URLs?

Otherwise, how can I convert a relative url to an absolute url in asp.net mvc3 - Is there any available function to do so?
Felipe Pereira over 7 years

it might looks like it works because of the fallback to the best/first image found on the site
Gerard Bosch almost 3 years

It probably "seems" to work because: "Without these Open Graph tags, the Facebook Crawler uses internal heuristics to make a best guess about the title, description, and preview image for your content." -source: developers.facebook.com/docs/sharing/webmasters So, yes, probably FB is using its own fallback mechanism in this case, when it fails to parse the image URL.