This is an old revision of the document!
The goal of this spec is to outline how the header of the static server-delivered page should be crafted in order to display per-social network custom format of the included share link snippet.
These networks display shared link as a snippet attached to custom share post message (which the user types in when sharing).
In order to deliver a custom snippet for each social network, a different static link has to be provided for each one, as there is no way to make differing headers for all the networks in one HTML page.
Therefore, I strongly suggest to have a GET parameter as follows:
http://tellmaps.com/?subject=WDAIND01&sharing=facebook http://tellmaps.com/?subject=WDAIND01&sharing=linkedin http://tellmaps.com/?subject=WDAIND01&sharing=googleplus
Server-side should then determine which information to send. All information is contained in <html>
and <meta>
tags.
I don't recommend to share the urls in new URL format. A fallback which the server will process and redirect to new URL format is the most reliable solution, as the new URL format may be google-crawlable, but support in share snippet may vary.
Actually, there is no way to display a snippet for twitter. Therefore, we will leave the “tweet” feature the same as in current tellmaps.
This OG format is well supported in all three social networks and probably many more. The only exception is missing description in Google+. This is not documented and there is the only information I found in that matter: http://www.seoskeptic.com/google-quietly-removes-descriptions-from-snippets/