The Facebook Open Graph Debugger has been a faithful friend for a very long time. I use it frequently and with succes.
However, when I try to debug certain pages from the website jannekestielstra.nl, the query results in a completely blank page. No header, no footer, no content. Completely blank.
For instance, debugging http://jannekestielstra.nl/daisy-goddijn/ results in a blank page:
https://developers.facebook.com/tools/debug/sharing/?q=http%3A%2F%2Fjannekestielstra.nl%2Fdaisy-goddijn%2F
Has anyone seen this before? And does anyone know what causes this?
Thanks in advance.
Rick
Try https://developers.facebook.com/tools/debug/og/object/ instead, it often works better in my experience. (I don’t know why, the underlying technology should be the same.)
You can also file a bug report, if you like - if the scraper/sharing debugger has a problem with your URL, then it at least should tell you what that problem is, and not “die” with a blank page. https://developers.facebook.com/bugs
It looks like a Curl Timeout: The request to scrape the URL timed out.
Related
I have started to experience a really strange problem with Facebook link scraping/caching which seems random in nature.
On brand new posts when I go to check: https://developers.facebook.com/tools/debug/ with my new URL I get a message saying 'Cannot scrape: URL blocked'
We have literally been sharing URL's to Facebook for YEARS with no problem whatsoever. All open graph tags are present and working fine.
What is really weird is if I just manually press the 'scrape again' button it grabs all the bits properly and says everything is fine. It's always just the first attempt.
I have also tried manually calling the scrap API instead of letting Facebook do it when someone shares the URL for the first time and still sometimes (not always) it returns empty (just 'id' and 'url' returned) indicating the URL was blocked.
What's going on here it's driving me mad? We are nowhere near our API limits if maybe that was the issue...
Why would it say blocked first go on the debug page then literally 2 seconds later you press 'scrape again' and it works fine.
Just to note sometimes when it says blocked it still shows maybe the image in the link preview but no title or description. It's like it's grabbed some tags but then given up. Very strange...
I have checked our access logs and I can see 'Facebot' accessing our site fine.
Hope someone can help, I am really hoping this is some weird Facebook bug as I can't see any change in our code base that would effect this.
Facebook does not return anything helpful when this happens even with the API. I have no way in contacting Facebook direct either. If we are somehow getting blocked I would love to know why and fix that issue. But it's impossible to debug at the moment.
Just to note I have 3 sites all running the same code base (WordPress environment). They are all experiencing this issue. All been running fine for many years.
Cheers
This was to do with rate limiting that was not visible in the Facebook APP dashboard. Helpful...
Full details here: https://developers.facebook.com/bugs/232343637174087/
Solution for your problem: You can use Facebook image button after adding link on Facebook news feed, like shown in iamge
second thing upload image on othe site and give the image path to your website and then put it on your news feed, you can get definitely positive result using this two methods.
also refer this image
thanks hope this two will work for your problem
I've searched all over for a solution to this, but can't find anyone else with the same problem. The Facebook Comments plugin is telling me: "Warning: http://www.runnersworld.com/fun/gear-review-old-yellow-jacket is unreachable." but when I look up that page in the Facebook Object Debugger, I get a Status 200 and no errors:
https://developers.facebook.com/tools/debug/og/object?q=http%3A%2F%2Fwww.runnersworld.com%2Ffun%2Fgear-review-old-yellow-jacket
(There is one warning, but it's about an image, and shouldn't be causing the unreachable error. I think it is unrelated.)
Every other forum thread that I found was solved by fixing the errors that appears on the Debugger console, but without any errors appearing there, I'm not sure what I'm supposed to be fixing.
We tried matching the data-href to match the og:url (the only difference is a query string) but that didn't fix the problem and wiped out all of our existing comments, so we rolled it back.
Any ideas how we can fix this? It's not just this one article, but several articles throughout the site.
Try to remove the cache from facebook like this :
got to facebook debugger and post your URL with refresh param like this
http://www.runnersworld.com/fun/gear-review-old-yellow-jacket?referesh=true
Try this more than once until facebook remove the cache.
I found that this problem was being caused by the Fetched URL and Canonical URL being different in Facebook's Object Debugger. To resolve it, I copied the Canonical URL (http://www.runnersworld.com/fun/gear-review-old-yellow-jacket?page=single) into the Input URL box at the top, then clicked the "Fetch new scrape information" button. That fixed the issue.
here is my headache situation:
I have my weblog's single article page, if I try to share this page with the facebook like button, or with the old sharing bookmarklet, I get no image on Facebook post preview, and of course I don't get any image on my Facebook page too.
I can hear you say, well, check it with linter, sure, that's what I did, and this is what I've found so far:
Linter returns no error and it shows the right thumb image
if "after" the linter passage, I try to share the same page again, well, I get the thumb.
Do you have any idea of what's going on?
here you can see an example: https://developers.facebook.com/tools/debug/og/object?q=http%3A%2F%2Flegrandj.eu%2Farticle%2Falain_baczynsky
this is the original page: http://legrandj.eu/article/alain_baczynsky
well, I know at this point it's not easy do debug, because I've "linted" almost all pages, but you can trust me, no images.
thank you!
if "after" the linter passage, I try to share the same page again, well, I get the thumb.
This is because you already tried to share them and they're now cached without images. If you want to get all pages fresh with image(s), you have to wait or re-lint every page you want to share in future. That's the only way to lift all caches immediately.
I am trying to implement facebook like box for my facebook page on my own site. I copied the code from http://developers.facebook.com/docs/reference/plugins/like-box/ (HTML5 or any other) and pasted on my site. Box appears with all the correct information bu when I click on like, I get an error message saying
"The page at http://www.facebook.com/pages/xxxxx/111111 could not be reached."
I've been trying to find a solution for this for hours but couldn't find anything. It's nothing to do with the privileges etc.
I also ran it through Object Debugger and it didn't come up with any problem.
Does anyone has any solution for this? I created the page today, does facebook needs time to parse/index my page before like box works?
Thanks in advance
Are there any demographic restrictions on your page that would prevent it being seen by somebody logged out of Facebook? Is it the published? Those are the two most common reasons for that error that I've seen
Ok, all of a sudden it started working. Haven't changed anything in the code. So I guess Like Box won't work if you install it on the same day you create the FB Page.
I am very surprised about this problem. If you check along several web sites, you can see that many times the Facebook likes counter does not show any value, although the link has a count value greater than zero. If you check that thing with the Twitter same service, it always works right. It is a programmer or a Facebook team fault? Exists any way to solve this problem?
Thanks for reading.
I'm not 100% sure what the problem is, but chances are it's Facebook's fault (when in doubt blame them). :)
No, seriously... the Facebook Like plugin has several options that let you determine how the total gets displayed (if at all): standard, count, button_count and box_count. And if behavior is not what is documented and expected, then chances are Facebook is having a buggy kind of day/week/month.
But if you just need to query for the count, then you can use FQL to pretty easily get that info:
http://www.saschakimmel.com/2010/05/how-to-get-statistics-for-a-facebook-like-button-and-shared-urls/
I think it's the default behaviour to sometimes not show the count bubble until someone click on the share button.
Here is a description from another blog and how to get around it.
http://kopepasah.com/social-media/facebook/facebook-share-count-button/
Check for missing ampersands after parameters in like button's "src" url.
As far as iframe box_count type of like button for Facebook Page is concerned
I had the same problem because I manualy pasted fanpage link in to src of like button witohut & or '&' after pageid or page name.
I think that if there is no ampersand later parametrs aren't parsed.