Im currently using the fb url linter and can see that everything is there correctly, however when a user likes the page it misses key information.
the linter is also stating there is missing content, however it also shows that all tags are there as well. is there anything wrong with my code ?
this is the result on the facebook url linter
http://developers.facebook.com/tools/debug/og/object?q=http%3A%2F%2Fdev.murchison-hume.com%2FProducts%2FSuperlative-Liquid-Hand-Soap%2FCoriander-Superlative-Liquid-Hand-Soap-Refill
it has conflicting messages stating things dont exist, when they obviously do as they are outlined below the error messages...
any help greatly appreciated
Recheck your type contents. The first error is telling you that you don't own the object type. For custom objects, usually you need to pass in
<meta property="og:type" content="MY_APP_NAMESPACE:product"/>
If that fails, og:type errors usually comes up when you fail to setup your objects correctly in your open graph settings (at developers.facebook.com).
I suspect that fixing the first error will make the others disappear.
Related
Some Time ago our users reported problems with sharing content from our page (text/image wouldn't show up in the share dialog), after some research we added the og:image:width and og:image:height-tags. To reduce loading time, the facebook-scraper receives the page with an empty <body> (we had troubles with timeout too).
Everything worked great until about a week ago. Pages that have already been scraped showed errors in the Object-Debugger:
Error parsing input URL, no data was cached, or no data was scraped.
This error shows up nearly everytime i click Show existing scrape information, eventually it would go away (without re-scraping the page) but then following error shows up:
The 'og:type' property is required, but not present.
The Sharing-Debugger additionally shows following error:
The parser's result for this metadata did not match the input metadata. Likely, this was
caused by the data being ordered in an unexpected way, multiple values being given for a
property only expecting a single value, or property values for a given property being
mismatched. Here are the input properties that were not seen in the parsed result:
'fb:admins, og:type, og:description, og:title, og:site_name, og:image:url, og:image:width,
og:image:height'
Sometimes it also says that our images are too big and couldnt be downloaded, but the image is shown in the preview. Sometimes it even goes as far as showing
Could not scrape URL because it has been blocked
What doesnt add up here is that if i click on See exactly what our scraper sees for your URL it shows me the source of our page with empty <body> and <og:...>-tags in the <head>
The debugger shows me the correct og:url, og:type, og:title, og:description and og:image, the preview is alright, response code is 206 and last scraping was somewhere in August.
After rescraping a few times, most of the time the error messages are gone, but that cant be the solution. It seems as if the debugger sends random errors for whatever reason
So what do these error messages really mean? Are they wrong? What am i missing here?
(Note: a 3rd pary is having trouble sharing our pages in their application due to those error messages, everytime they appeared in the debugger, their data seems to be somehow broken)
After some back and forth with one of facebooks supporter in the developer forum, they acknowledged my problem as a bug and assigned a team for further investigation. However, a few days later my bug report was closed with following message:
Those messages are due to a bug in our Debugger when you scrape no-canonical URLs. On that case, the information about your URL is updated asynchronously so it takes a little while for the error messages to go away.
If you input the canonical URL in the debugger, the error messages will go away after the first scrape.
Unfortunately, due to the way our systems works, we are not planning to fix that error in the near future.
I have a news.read application already accepted by Facebook, but with some Wordpress update it stopped working, because Facebook assumes that "og:type" of my articles are set to "website" and therefore nothing works.
The problem is that the source I can check through my browser has a proper "og:type" and even when clicking "See exactly what our scraper sees for your URL" it reports the proper og:type!
Is this some kind of bug or am I missing something?
Here's an example URL: http://www.jornalinsolito.com/um-ato-sexual-que-dura-ha-47-milhoes-de-anos/
Any help is useful!
You have tags ouside of your . This is either because your was malformed and they fell lower in the parse tree, or you accidentally put your Open Graph tags in the wrong place. Either way you need to fix it before the tags are usable.
checkout here
Having issues getting Timeline to work. It is a two part problem.
First, there is an issue of caching parts of the OG metatags. When the debugger goes to my URL, I know it is hitting it correctly because the og:url it spits back is correct which means it has been processed on my end (ex: I send it to og.php?og=read&chapter=799, and it will spit back the right book_id for the og:url, meaning my script processed it). But all the other information seems to be cached. I originally and erroneously had an fb:app_id and og:site_url for an object, so I removed those. The output still shows those as having an existing site_url which is throwing an error. Having a fb:app_id forces the og:type of 'website', which I have set (correctly) to my namespace and object. When I try to POST the action, I get an oAuthException error back, that an og:type of 'website' isn't valid for an object. Once again, that should be fixed, but it keeps caching the old OG data. I have tried adding ?fbrefresh=1, but that did nothing.
Another issue, possibly related...even though I know it got there, and my script processed the request, Facebook doesn't report that. When I click on "See exactly what our scraper sees for your URL" it shows the authentication URL (see below)! As though, it never got there and the popup was initiated, which isn't even how the code for og.php works!! My guess is they got that from the base domain name itself (exmaple.com) before trying the full request with example.com/og.php.
window.parent.location='https://www.facebook.com/dialog/oauth?client_id=164431733642252&redirect_uri=http%3A%2F%2Fapps.facebook.com%2Fexample%2F%3Fpage%3D&state=064bd26ff582a9ec7c96729e6b69bbd2&canvas=1&fbconnect=0&scope=email%2Cpublish_stream%2Cpublish_actions%2C';
I figured it out. I thought the og:url was the URL you wanted people to use to get to the correct page in your app, like an action link. It is, but it isn't. I now have it match the OBJECT_URL you send to timeline.
I had a different URL (an action link to the app), which when redirected, can't be reached by the crawler because it is inside the applications authorized wall. This caused the og:type of website, and data to appear cached.
To fix it, the object_url I post to timeline, and the og:url in the metatag is the same. But you can figure out if it is the crawler or the action link by looking for the query string: ?fb_action_ids=SOME_ID which is sent from link on the timeline. If it contains that, then I forward it to the application page needed from there.
I'm having similar problems to you. It kept complaining about og:site_url being set, even though I never set those. It appears that the error messages it sends are actually inaccurate, and the problem is not that og:site_url is being set, but that the og:url is different from the object url. Sometimes a wrong error message is worse than no error message!
A further question is why an object url has to correspond to a live page that a user will see. An object is a logical unit, but it doesn't necessarily correspond to a single user-visible page. Your redirection trick might work, but it is not the proper way to do something. When I post an action related to an obect, the object url should be used to draw the information of the object, but I should be able to send the user somewhere else. If this was an intended design I think it is a mistake.
I'm having a weird experience with fb sharing. Whenever me or anyone share's my blog post, in the description area my ad codes are visible. This is hammering my adsense. I tried using facebook debugging tool and I got the following issues but I am unable to resolve it. Any help would be highly appreciable.
Errors That Must Be Fixed: Body Meta: You have tags ouside of your . This is either because your was malformed and they fell lower in the parse tree, or you accidentally put your Open Graph tags in the wrong place. Either way you need to fix it before the tags are usable.
**Warnings That Should Be Fixed: Inferred Property: The og:url property
should be explicitly provided, even if a value can be inferred from
other tags. Inferred Property: The og:title property should be
explicitly provided, even if a value can be inferred from other tags.
Inferred Property: The og:image property should be explicitly
provided, even if a value can be inferred from other tags. Inferred
Property: The og:locale property should be explicitly provided, even
if a value can be inferred from other tags.
It sounds like the meta tags are in the wrong place but because you haven't given us a link to your site it's hard to be sure; they should be in the section of the page. This would be causing the first error.
The second error refers to missing tags, but they might be 'missing' by virtue of not being in the correct place, so fix the first problem first
{edited after seeing your page}
The main error at the top is because you've a
<meta name="alexaVerifyID" content="{snipped}" /> tag outside the <head></head> section of your page.
The rest of the errors are because you haven't added any open graph tags at all - each page should have meta tags telling Facebook what title/description/image to use when sharing, as well as which app/user should be allowed to see the analytics and insights information for the shared links
For more information on how this works, see https://developers.facebook.com/docs/opengraph/
If you want to just get up and running quickly, try the tool at Step 2 of the Like Button Documentation to generate some sample tags
You supplied an Open Graph type via
one of the supported meta tags, but
the type you specified "link" is not
valid.
The above is the error I get when the "LIKE" button is clicked.
I tried to set all sorts of OG meta tags. You can see the code live at http://luxe.sonikastudios.com
I looked at many different forums etc. but no clear answer is given. I don't even have an og type "link" specified.
I put my page through the linter provided by Facebook (http://developers.facebook.com/tools/lint/) and I don't see any errors coming up as far as I can tell (but then I don't even know what this screen is supposed to look like in case there is an error).
Any help would be appreciated.
Appears to be a known FB Bug: http://bugs.developers.facebook.net/process_bug.cgi
I think it doesn't like your <meta property="fb:link"> tag. Where did you get it from?
Just remove everything and leave only required params listed here. I would also recommend setting type to article. See if that works. If it does then start adding new params one by one until it fails.