Skip to main content

Blogger & Facebook OG object debugger

Facebook or any network that gets your URL and displays preview, actually scrapes the URL through a system developed by Facebook called the open graph.

They might look something like this in the page's source,

<meta content='' property='og:url'/>
<meta content='Blogger & Facebook OG object debugger' property='og:title'/>
<meta content='My Facebook preview shows incorrect information. How to fix?' property='og:description'/>

Therefore, while sharing a link for the first time on facebook, the object debugger stores meta information like these in its cache so when you share again, instead of scraping the URL, it takes from its own cache. After a while, when the cache expires, it scrapes again. So a shared URL even upon changing the description/image/title, does not get affected immediately.

It doesn't mean, there's no other way other than to wait. To overcome this and see quicker results of custom description/ changing image/ changing blog or post title, Facebook has a facility called the Open Graph Object Debugger. 

How to use OG Object Debugger?
  1. Go to the Open Graph Object Debugger,
  2. In the input URL box, provide your blog post URL
  3. Click on Debug.
  4. If the URL was never shared to facebook, it will ask to Fetch new information.

  5. If the URL is already shared, it will show all the scraped details. If they are incorrect, please click on Scrape again.

  6. When this is done, try sharing the post on your Facebook News feed.
This time you should get the proper and newly scrapped information. 


People also read,

How to secure your Google account and Blogger blog?

As a part of contributions to NCSAM, I am writing this article down on what all should we be aware of with respect to Google's security aspect and how to make sure your blog stays yours forever.
What is NCSAM? It's National Cyber Security Awareness Month which is observed during the month of October every year in America.

However, we all know cyber security is a world topic and is not limited to just the USA. So let me give some tips with respect to keeping the Google account safe and Blogger blogs safe from hackers. As I secure my account, I hope you people catch up too.

In this blog post, I am going to tell about the following,
Securing your Google account.Securing your Blogger blog. Securing your Google account Since Blogger is also part of your Google account, let's first see what all we need to do to keep our Google account safe. Don't share your password to anyone.Keep changing your password every 60 - 90 days.Make sure your password is strong enough. Have at leas…

Blogger HTTPS for custom domain and Cloudflare

In BHF, there was a recent issue related to cloudflare where the browser screams the site is a phishing site. So I thought of writing up how does a service like cloudflare affect your blogger blog.

What is Cloudflare?
Well we have that written all over Wikipedia: Cloudflare. Let's go on with why Blogger users look for Cloudflare.
Anciently Blogger users used Cloudflare for one simple reason. HTTPS for custom domains.
So what happens when you introduce Cloudflare into your domain?
DNS Redirect. Your custom domain will be configured with the proxy info provided by Cloudflare and when the request is hit, DNS redirect happens.
DNS redirect is bad for the site's health. A number of reasons, but the most important is that some browsers, when it detects a DNS redirection, it thinks that it is a phishing site.

What is a DNS redirect?
I am trying to explain this in easy terms. I'll try not to be too technical. When a custom domain URL is hit, usually the domain requests go to Name ser…

Blogger & Twitter card previews

So, there was a report in Blogger Help Community which is what made me write this down. This is in correlation with Blogger & Facebook OG Object debugger. The report was that Blogger blogs doesn't show preview in Twitter card validator.So, I went ahead and tried previewing one of my blog posts and I got the following,

Therefore, I tweeted the same link which is here and it didn't show any preview.  Hence, I concluded not just the validator, the whole twitter stopped scraping my open graph information. Therefore, I made a small research and added a tag in my template.Please follow instructions below,Go to > ThemesClick on the three dot menu near "My Themes" and choose Edit HTMLIn the appearing page, press Ctrl + F and find the below code,
<b:include data='blog' name='all-head-content'/>
Right after that code, paste the following code,
<meta name="twitter:card" content="summary" />
So, it should look…