facebook is not recognizing my meta tags

拥有回忆 提交于 2019-11-30 11:45:09
Daniel Torvisco

The URL you've specified at the og:url meta tag contains an invalid fb:admin. Please update it with a valid admin ID and try again.

See Lint information at the Facebook Debugger Tool

Object at URL "http://reviewumpire.com/movies/54-katha-screenplay-darsakatvam-ksd-appalaraju-" of type "website" is invalid because the given value "57728908711" for property "fb:admins" could not be parsed as type "fbid". Invalid Admins -> The fb:admins field contained some invalid ids, namely 57728908711

kawal

I had the same problem and what I found out was that Facebook recognizes

AddMetaData("og:url", "yourURL")

and then goes to yourURL to get the other tag info like og:title...etc

You're missing the namespace definitions xmlns:fb="http://www.facebook.com/2008/fbml" xmlns:og="http://opengraphprotocol.org/schema/"

Edit: <html xmlns:fb="http://www.facebook.com/2008/fbml" xmlns:og="http://opengraphprotocol.org/schema/" xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en" dir="ltr">

Dampas

I know that this is an old question but I can't really see the answer that I find - just remove slash (/) at the end of facebook meta code.

So Facebook create wrong code if you not using right DOCTYPE:

<meta property="og:title" content="Katha Screenplay Darsakatvam (KSD) Appalaraju "/>

right is:

<meta property="og:title" content="Katha Screenplay Darsakatvam (KSD) Appalaraju ">

I checked out my code and discovered that i was outputting some data before the tags. This caused the facebook parser to mess up and as soon as i removed the html from outside those tags it worked fine.

kaliostrozen

Check the HTTP response headers your server is sending out for that page.

If the Content-Length field is missing then that is your problem. In my experience, Facebook will not parse your page if that field is missing.

For me, this was because I had a 302 Redirect to get to the actual page with the OG meta tags. My guess would be that the Facebook crawler doesn't follow redirects so you have to make sure you're returning a 200 on the first request.

Might also be wrong encoded double quotes in the meta tags, if e.g. you have copied the code from a browser into your editor.

I found a huge number of bugs in my pages markup by using the linter at https://developers.facebook.com/tools/debug/

Down below is a function: "See exactly what our scraper sees for your URL" which is really helpful.

try removing

<meta property="fb:app_id" content="162180660488445" />
<meta property="fb:admins" content="57728908711" />

and use this, to test your url and error info

http://developers.facebook.com/tools/debug

Jason

What we noticed is that the facebook crawler is willing to follow redirects in the og:image url but the facebook client does not. Take this example.

Try posting the following link into facebook. If facebook has seen the url before, their crawler will have properly cached the image. If it hasn't, it will not. To simulate this behavior, put a random string into the ref parameter of the url below.

http://www.blipboard.com/4fac51e571272e0100000015?ref=1

If you try to post this url (with the random id inserted) it will fail to show the correct image the first time. If you then reload the facebook page and try to post again, this time it will work.

The meta-tag is the following (which requires a redirect):

<meta property="og:image" content="http://graph.facebook.com/1000484548/picture?type=large" />

The best explanation I have for this is that the facebook client code doesn't follow redirects but the crawler does (as does the debugger)

易学教程内所有资源均来自网络或用户发布的内容,如有违反法律规定的内容欢迎反馈
该文章没有解决你所遇到的问题?点击提问,说说你的问题,让更多的人一起探讨吧!