![]() (I wont spend any time on this other than to point out it will waste colossal amounts of your time if not double checked.To get started with implementing Cards markup, specify the type of card for your content by adding the following HTML markup to the HEAD section of the page:Ĭard properties are simple key-value pairs, each defined in an HTML meta tag as seen above. PS: remember that a CDN or serverside cache will serve to Facebook's scraper even if you "think" you can see the most recent version. In closing, YES the cache busters, random vars, changing urls and suggestions here can work, but they will seem like "intermittent voodoo" if the og:type is not specified correctly. If you do that now Facebook will give you far far less problems with scraping your NEW images. ![]() (there is good reason for that, but its off topic)Ĭonsider this solution (which is what most people "really want") (try it, you'll see) - if you set the og:url to be your root or parent domain you've told facebook they are all canonical. ![]() If you do that Facebook will think all of those are canonical and it will put the FIRST og:image into all of them. Those are not "all websites", 1 is a website, the others are articles. Ergo: /sub-page/ and /child-2/ will inherit the og:image of the parent This means you will have trouble getting your images to update using the scraper no matter what you do.Ĭonsider this "assumption and common mistake" Years later and this is still a common problem, but its not always facebook's cache: It is very often human error (allow me to elaborate)īe aware that og:type=website will cause any /sub-pages/ of that url to become "canonical". If the meta information is up to date in your code and you've tried all of the above (unless another suggestion comes to fruition), the correct answer is you can do nothing but wait. Inspecting your code is always a spot on way to confirm it is not an issue with browser cache or some caching service. ![]() Choosing to see exactly what the scraper sees - does not appear to request real time un-cached scrape data, it still shows the cached image url even if the file no longer exists.Choosing the graph API link at the bottom of the og dev page.Adding the "./?fbrefresh=anything" query string to the debugger fetch url.Adding a query string to the image url by appending a PHP TIMESTAMP or ?anything.Changing the actual image filename and/or deleting the original.Choosing "Fetch new scrape information".Here are things that have been reported to work by others but I have had ZERO success with any of them. It is cached until fb updates (reportedly every 24 hours) There is no fool proof way to update the open graph og:image url with immediate result. I'm sorry folks but the correct answer is: Otherwise, someone would be able to pretend that a user shared something that he/she actually didn't. There is no way to update all previous posts and it's this way by design for security reasons. When you call the debugger to scrap changes on your og:tags of your page, all previous Facebook shares of that URL will still show the old image/video.Note regarding image or video updates on previously posted posts: The only effective workaround for me has been to assign a new name to the image.(even passing a ?last_update= at the end of the image url didn't work for me). If the og:image URL remains the same but the image has actually changed it won't be updated nor recached by Facebook scrapers even doing the above.you can even parse the json response to get the number of shares of that URL.Make sure the og:url tag included on the head on that page matches with the one you are passing.Make a GET call programmatically to this URL: &scrape=true (see: ).Click the Fetch Scrape information again Button.(Make sure you use the same url included on your og:url tag) These are the only 2 options that should be used as of November 2014: For non developers The most voted question is quite outdated: Why is Facebook caching og:title and og:url? Is anyone experiencing the same issue? I am now currently using these meta tags (you can verify if you view the source of the HTML): However, The last two entries are the OLD entries that I used for this site. Notice that there are two values for og:title and og:url, and the last one prevailed. I ran Lint on a page in my site, and this appeared: Old values for Attributes og:title and og:url are still used, even though I have changed them already. It seems as though Facebook is caching old values of my meta tags. I'm having troubles with my meta tags with Open Graph.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |