From time to time Twitter Card Validator shows an error for twitter:image:src - Failed to get a proxied URL for the image.
Domain is approved, robotx.txt is present in web root. Twitterbot successfully retrieves robots.txt, web page and image, but image is not shown in the Twitter Card.
Source page: http://www.bluefountainmedia.com/blog/how-to-create-great-content-for-your-business-blog/
Twit: https://twitter.com/mstzfort/status/363004775891087361
Metatags:
<meta name="twitter:card" content="summary">
<meta name="twitter:site" content="#BFMWeb">
<meta name="twitter:url" content="http://www.bluefountainmedia.com/blog/how-to-create-great-content-for-your-business-blog/" />
<meta name="twitter:title" content="How to Create Great Content for your Business Blog">
<meta name="twitter:description" content="In case you hadn’t already noticed, 2013 is all about content. Check out 7 content Ideas (+1 bonus) to help come up with great content for your business blog.">
<meta name="twitter:image:src" content="http://www.bluefountainmedia.com/blog/wp-content/uploads/2013/06/Business-Blog-Content-197x110.jpg">
So, the question - how to show images in twitter cards?
Related
I am trying to leverage the rich text messages with open graph meta tags. So I have included my meta tags in my website head and it passes all of the Facebook debug and iOS API validation tool.
Yet when I text the link to people either on Android or iOS it doesn't often work. It works typically with Facebook messenger
Does anyone know if this is a cell carrier issue or do I have something configured wrong?
<meta property="fb:app_id" content="********" />
<meta property="og:type" content="website" />
<meta property="og:url" content="https://dameranchdesigns.com/" />
<meta property="og:title" content="Dame Ranch Designs" />
<meta property="og:description" content="Divinely inspired logo graphics and
website design. A whole new way of being ... on the internet." />
<meta property="og:image"
content="https://dameranchdesigns.com/images/logos/DRDSunLncropped.png" />
Yetter,
A couple of quick things to help you out here:
Apple Support Open Graph for rich SMS messages only since iOS 10+, so make sure that the device you are testing the sent text message to is at least iOS 10 (or higher)
Apple only supports og:title and og:image. It ignores the rest (so in your example above, og:description is completely disregarded. Furthermore, if your og:image is a gif image, Apple doesn't support that.
Your url in the text message needs to be on it's own "word" meaning there needs to be at least a space between it and any other word in the text. Furthermore, and perhaps most importantly, it needs to specify a scheme, so either: http:// or https://.
You can only have one hyperlink to your site with the og:tags. More than one shuts this functionality down.
Lastly, I don't believe Android supports such rich messaging functionality in it's SMSs (at least not with Open Graph) -- at least as far as I know as of this writing (Nov-2017). It would be great if they adopted OG as a standard.
So for example These wouldn't work:
you were invited. You can join on: grapevite.com //no scheme present
you were invited on http://grapevite.com. Care to join? //Link is between text.
Whereas these would work:
you were invited on Grapevite. http://grapevite.com
http://grapevite.com. The world's premier platform for creating, sharing and joining experiences
Reference Reading:
Some sites like these would provide you with some insight as to the above: https://uplandsoftware.com/mobile-messaging/resources/blog/what-ios-10-means-for-mobile-messaging/
https://www.tatango.com/blog/ios-10-what-sms-marketers-need-to-know-and-do/
A bit of an update for anyone dealing with this mid-2019. I was dealing with this today. I was trying to specify a certain thumbnail to be shown in the rich message preview across Facebook messenger, iOS messages and android messages.
Using actual code from the website I was working on. Be sure to replace content with your own.
These 4 tags made it work for me on Facebook messenger and iOS messages:
<meta property="og:title" content="Software to manage leasing and rental applications" />
<meta property="og:type" content="website" />
<meta property="og:url" content="https://geteagle.com.au/products/leasing-tools/" />
<meta property="og:image" itemprop="image" content="https://geteagle.com.au/site/templates/images/logo-og-white-big.jpg" />
For some reason, android messages refused to show the thumbnail I specified. I did a lot of research and tried everything I could find in this other question: Showing Thumbnail for link in WhatsApp || og:image meta-tag doesn't work
My tags bloated to 9 (8 meta, 1 link), but it was actually the link tag that made it work in android messages:
<link itemprop="thumbnailUrl" href="https://geteagle.com.au/site/templates/images/logo-og-white-big.jpg">
I'm not sure if the other tags are needed in addition to the link tag to make it work on android messages, but here is the full block if you want to try:
<meta property="og:title" content="Software to manage leasing and rental applications" />
<meta property=”og:description” content="Eagle offers a suite of of leasing tools and application management features to power-up your rental team!" />
<meta property="og:type" content="website" />
<meta property="og:url" content="https://geteagle.com.au/products/leasing-tools/" />
<meta property="og:image" itemprop="image" content="https://geteagle.com.au/site/templates/images/logo-og-white-big.jpg" />
<meta property="og:image:secure_url" itemprop="image" content="https://geteagle.com.au/site/templates/images/logo-og-white-big.jpg" />
<meta property="og:image:width" content="1000" />
<meta property="og:image:height" content="500" />
<link itemprop="thumbnailUrl" href="https://geteagle.com.au/site/templates/images/logo-og-white-big.jpg">
Many thanks to this particular answer from the question mentioned above that resolved my frustrating situation.
Hope this helps. Good luck!
I'm wanting to put my OpenGraph properties into a shared view to be used across multiple pages however Facebooks sharing debugger is giving me back errors despite following the open graph documentation.
The Code
<head>
<meta property="og:image" content="www.myimage.co.uk/images/image.png"/>
<meta property="og:title" content="#ViewBag.Title">
<meta property="og:site_name" content="...">
<meta property="og:url" content="www.myimage.co.uk/">
<meta property="og:description" content="...">
<meta property="og:type" content="website">
</head>
Facebook debugger
When I submit my url into the debugger and press debug, and even scrape again to make sure it's giving me back this error:
Inferred Property
The 'og:image' property should be explicitly provided, even if a value can be inferred from other tags.
I've also inspected my webpage in the browser and the code is exactly as stated above. Is there something obvious that I'm missing?
Edit:
Using the 'scraped url' option on Facebook's debugger, it shows that the meta tag's aren't being picked up by Facebook's scraper - is there a way of ensuring that this data is picked up by a scraper?
I have one big web app that is basically one page where every content is created dynamically. It also has a forum, how do I expose the forum to Google or other search engines? Should I create a seperate view of the forum especially designed for search engines?
Use meta tag in your html. This metadata can be used by search engines (keywords).
<meta name="description" content="xyz your web site name etc">
<meta name="keywords" content="xyz your web site name etc">
<meta name="author" content="xyz your web site name etc">
I'm writing a SPA that uses underscore templating. The app searches for and rates music albums and returns the result via ajax. If facebook open graph metatags cannot be altered dynamically and the url of the page is constant regardless of search result, how can i make it so users can share that they rated a certain album.
ie)
<meta property="fb:app_id" content="118454308341351" />
<meta property="og:url" content="http://www.appurl.com" />
<meta property="og:title" content="Fleetwood Mac's Rumors" />
<meta property="og:image" content="AppImg.jpg" />
and update those properties to reflect a given search result.
The way I handle this is to create a dynamic page which I use as my open graph object, which is simply populated from the url parameters and redirects back to my SPA using the meta redirect.
<meta http-equiv="refresh" content="0;URL=http://YOUR_WEBSITE_WITH_DYNAMIC_CONTENT">
Thanks to this tutorial I found a solution: https://speakerdeck.com/sienatime/facebook-sharing-for-single-page-apps?slide=15
I send only meta tags if the user-agent of the http request includes "facebookexternalhit".
Here is some code for a backend with node and express:
app.get('/', (req,res) => {
if(req.header('user-agent').includes('facebookexternalhit'){
res.send(`
<meta property="og:title" content="The Slits' Cut" />
`);
} else {
res.sendFile(index.html);
}
})
You could also write your own middleware for that.
Our solution was to use Netlify pre-rendering, which pre-renders and then caches the rendered HTML to serve to crawlers and bots specifically.
This seems to work well. It allows us to dynamically update the OG meta tags, which are then cached by Netlify and served to crawlers, so they see the correct content.
It was easy to setup too, so if you are using Netlify this may be a good solution for you.
When I try to debug my gwt app that's inside an iframe (note that gwt codserv and webserv are all local) I'm having permissions issues. The following errors are thrown:
on Chrome console: "Refused to display document because display
forbidden by X-Frame-Options.";
on Chrome webpage window: "Plugin
failed to connect to Development Mode server at 127.0.0.1:9997 Follow the underlying troubleshooting instructions"
This ONLY happens in Google Chrome, firefox and IE are ok.
I've already searched for simillar problems but all of them are on crossdomain context, and mine is local. Also, tried the proposed solutions but all without success.
Here is an example of my webpage containing my iFrame. I can't debug MyGWT app.
<!doctype html>
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
<iframe src="MyGWT.html?gwt.codesvr=127.0.0.1:9997"></iframe>
</body>
</html>
The page that's being blocked is probably TroubleshootingOOPHM
FYI, this has been fixed in GWT 2.5, which now links to this page rather than trying to display it in an iframe (moreover underneath the error glasspane, which made it hardly readable anyway before Google changed their server settings)