Most of the traffic for PoppaString comes from web searches and most of those searches originate from Google. However, I am noticing an increase in traffic coming from social networks and mobile devices, and so I wanted to ensure that all searches for *me*, regardless of origin, was as consistent and unified as possible. My first step was to take advantage of the Google’s support for authorship markup.
<link rel="me" type="text/html" href="/blog/syndicationservice.asmx/GetRss/"> <link rel="me" type="text/html" href="http://twitter.com/PoppaString"> <link rel="me" type="text/html" href="http://www.linkedin.com/in/markdownie">
I am not sure how well blogs are prepared for the onslaught of mobile devices and the various ways in which they interpret the tradition pixel. In short we have a proliferation of devices with pixel density outputs that are radically different from that of a typical computer display. In these cases the user agent will need to know to rescale the pixel values, the following is an example of a viewport meta tag to control layout on mobile browsers.
<meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0"/>
<meta name="msapplication-task" content="name=Apps;action-uri=/Apps;icon-uri=/images/ps.ico" /> <meta name="msapplication-task" content="name=PoppaString on Twitter; action-uri=http://twitter.com/PoppaString;icon-uri=/images/twitter.ico" /> <meta name="application-name" content="Blog" /> <meta name="msapplication-tooltip" content="Blog" />
Here is the output: