I've created a website using a vanity domain extension, http://thatme.me. I've added the necessary OpenGraph meta tags for the urls to display all pretty on Facebook. If a user posts a full URL, for example http://thatme.me/notbad, the OpenGraph data gets pulled and shows the image on the post. However, if a user only types a url like this thatme.me/notbad the URL is not recognized and the OpenGraph data doesn't show.
Is there something I need to do so that those URLs will be recognized or am I just out of luck?
Related
We have a rather large site that features travel properties.
Each property has its own Property ID #
When a user posts to Facebook using our full property url Facebook pulls the featured property image correctly.
However our urls are long for each property. So we created a shortened redirect for all. www.domain.com/propertyID#.
When a user posts the redirect version on Facebook it fails to scrape an image because the redirect does not have the og:image data.
Is it possible to have Facebook pull the image when the redirect URL is posted? We do not want the redirect URL's to be indexed.
I have the following problem. I hope some one can help me :)
I have a client who has the following URL
http://www.clientwebsite.com/pageA.html
On the above page client has door images which he allows the visitor to select with a radio button. This page i.e. pageA.html does not have any open graph meta tags on it.
Once the visitor selects the door image on pageA.html he is taken to
http://www.clientwebsite.com/pageB.html
Now the client wants to use open graph meta tags on pageB.html which will pass the URL of pageA.html and the selected door image of the visitor from pageA.html to Facebook.
However this is not working as planned. I have tested this using the Facebook open graph debugger tool and below are my findings
When I pass the og:url meta tag with the URL of pageA.html, Facebook just picks random images from pageA.html and not the one I am passing in the og:image meta tag.
When I omit the og:url meta tag, Facebook picks up the image I am passing in the og:image meta tag but it does not know the URL which I need it to use.
Is there a solution to this?
UPDATE
Here is the URL in question
http://www.jvd.me.uk/share-test3.html
The above is pageB.html. The URL mentioned in the og:url meta tag is pageA.html
Anyone?
I am POSTing the values from pageA.html to pageB.html
Well, Facebook’s scraper doesn’t POST any data to your page B when it requests it, so this approach is of course bound to fail.
It is not possible to have different content based on the user’s choice under the same URL (because when the scraper visits the URL, there is no user to make that choice), so you will need to set up different URLs for your different images. (Using a GET parameter to determine what image to embed would be enough, since different GET parameters make different URLs.)
I’ve recently added a Facebook like button to a site of mine and all seems to work fine except that the post on my Facebook wall has a url with a load of parameters appended to the url.
Example: http://domain.com/this-is-a-new-post-to-test-the-url?fb_action_ids=1403388974344336068&fb_action_types=og.likes&fb_ref=sp_facebook_57&fb_source=aggregation&fb_aggregation_id=247881481237582
I have set the open graph meta tag but this does not seem to make any difference.
What I find interesting is that some pages I’ve liked (on a different domain) don’t have these parameters appended to it.
The question is: how to “sanitise” the url on my Facebook wall so it looks like http://domain.com/this-is-a-new-post-to-test-the-url and NOT like http://domain.com/this-is-a-new-post-to-test-the-url?fb_action_ids=1403388974344336068&fb_action_types=og.likes&fb_ref=sp_facebook_57&fb_source=aggregation&fb_aggregation_id=247881481237582
Facebook adds these parameters so that website owners can keep track of where incoming traffic from Facebook originated and can not be removed.
I am trying use open graph API to publish an action. URL that I provide as part of meta data property og:url can be accessed by authenticated users only. Facebook is trying to scrape the URL and is ending up with a sign_in page due to a 302 redirect.
Do I have to construct a page just for facebook scraping with meta tags in it? Isn't this url linked to the content published on facebook?
If you want your articles to be sharable or do any SEO, you shouldn't be using 302 redirects. Bots will only see the content from the destination of the redirect.
You want to have just one URL for each piece of content. If an unauthenticated user, the Facebook Scraper, or Googlebot visits that URL, you want it to see all your Meta tags and some teaser content.
If the user isn't authenticated, use a server-side scripting language to display a register/sign_in dialog instead of the premium content. If the user is authenticated, then you show them the full content.
This is better even from a UX perspective: Say I follow the link from Facebook and register. When I sign in, how are you going to get me back to the content I wanted to see in the first place?
Our websites article backend does not allow access to anything above </head> which prevents our writers from specifying shareable content with use of the facebook meta tags. Anyone know an alternative route of specifying the article image, title, and description of a shared article without accessing the <head>? My search yielded no results, my apologies if this has been answered.
Can you give your writers a way to create meta tags in other separate pages, outside of your article backend?
The Facebook Open Graph meta tag content does not need to reside within the same page that the like button is rendered on. The shareable content (images/titles/descriptions) will be pulled from the meta content of the page referenced in the URL parameter of the Facebook button. So you could create separate pages corresponding to each of your articles that serve simply to supply the meta content for the Facebook news story post. The Facebook news story posts would still link back to your articles as long as the meta "og:url" in the placeholder file is set to your article url.