Skip to main content

Diagnose FaceBook Posting Problems

Sometimes, in the progress of integrating a FaceBook Wall with our blog, we may face a problem which involves FaceBook Open Graph code.

FaceBook error displays can be as mysterious as Blogger error displays. But, there is hope - provided by FaceBook Developers.

The FaceBook Developers Debugger tool can be invaluable, in diagnosing a problem with our blogs, and FaceBook Open Graph code.

Diagnose FaceBook problems, before asking for assistance.

When we try to share a blog post with FaceBook, and get a mangled mass of pictures and / or text, it's a good idea to diagnose the problem, before requesting help. Sometimes, the Debugger will provide the right clues, and help us identify our problems, immediately.

Provide the URL of the blog, and hit "Debug".

To use the tool, just provide the URL of the blog, or the post, which has a problem.

Paste a URL into the box, and hit "Debug".

Use "Show existing scrape information" or "Fetch new scrape information".

Start with the immediate errors.

Check the raw Open Graph tags. And the "Open Graph properties", that were the usable part of the code that you provided.

The complete code listing is in "Scraped URL".

View an image of what your share will look like, when it hits the Wall. And click on "Scraped URL", for the complete code listing.

You'll have a choice to "Show existing scrape information" or "Fetch new scrape information" - which can be useful, if you are diagnosing a problem after you shared your blog post. For help on using the tool, you'll see the hint.
See our Webmasters doc for more info on the Facebook crawler and debugging your Open Graph markup.

Run the Debugger - then post in the FaceBook Community, if you wish.

And, if worse comes to worst, and armed with Debugger logs as examples of the problem, we can report the problem to FaceBook Support. Having a copy of the "Scraped URL" page will be useful then.


Loretta Folz said…
Does this need to be done for every post before publishing to facebook? When I use the facebook debugger, and see the list of things to be fixed, do I enter these fixes in the html in facebook? If so, where in the html do they go? An example of how to perform a fix would help.

Also, I want my posts to come over from Blogger to facebook without using the name of my blog first in the headline. I want it to show only in the attribution, at the bottom of the post. How to do this?

Thank you.
Chuck Croll said…
Hi Loretta,

Thanks for the question.

The debugger should show you what is wrong, with the code in the template. With enough determination, you should be able to fix the template code - and thereafter, just worry about post content.

In general, no it should not have to be done. Take a look at what gets posted to your Wall - if you are satisfied, nothing more has to be done. If what is posted looks dodgy, then you can use this technique, to figure out what needs to be done.

Almost all system code is a balance between what you would like to do, and what can be done, right now. Blogger is a massive conglomerate of compromises.

Popular posts from this blog

Stats Components Are Significant, In Their Own Context

One popular Stats related accessory, which displays pageview information to the public, is the "Popular Posts" gadget.

Popular Posts identifies from 1 to 10 of the most popular posts in the blog, by comparing Stats pageview counts. Optional parts of the display of each post are a snippet of text, and an ever popular thumbnail photo.

Like many Stats features, blog owners have found imaginative uses for "Popular Posts" - and overlook the limitations of the gadget. Both the dynamic nature of Stats, and the timing of the various pageview count recalculations, create confusion, when Popular Posts is examined.

Help! I Can't See My Blog!

I just posted to my blog, so I know that it's there. I can tell others are looking at it. But I can't see it.

Well, the good news is you don't have a blog hijack or other calamity. Your blog is not gone.

Apparently, some ISPs are blocking *, or maybe have network configuration or infrastructure problems. You can access or you can access, but you can't access, or

You can't access them directly, that is. If you can access any free, anonymous proxy servers, though, you may be able to access your blog.

Note: You can use PKBlogs with the URL pre packaged. Here is the address of this post (with gratuitous line breaks to prevent the old post sidebar alignment problem):

And an additional URL, to provide to those suffering from this problem, would be the WordPress version of this post: