Menu
Meta-tags "Viewport", "MobileOptimized" and "HandheldFriendly" can be used to provide appropriately formatted HTML-content to mobile devices. Are these tags good things? They seem pretty platform specific in many cases, and even when not platform specific (viewport), they seem to require device specific attributes in order to work properly.
Should they be used? Where and when is it appropriate to use them? Are there alternatives (without user-agent recognition)?
Note: I have been using CSS media queries to achieve mobile-support, but this requires some UAR in order to get optimize font size.
439
Meta tags are important because they impact how your site appears in the SERPs and how many people will be inclined to click through to your website. They will therefore impact your traffic and engagement rates, which can impact your SEO and rankings. Meta tags are an important part of a solid SEO strategy.
Using the meta tag is said many times in the specification to be worse than the header. Only use it if you need to. But it's as safe as it can be: Note: A policy specified via a <meta> element will be enforced along with any other policies active for the protected resource, regardless of where they're specified.
<meta> HTML Tag This element must not contain any content, and does not need a closing tag.
These tags can be easily abused by web site creators anxious to bait search engines and bring scores of visitors to their sites. The law about metatags is far from settled and many legal scholars are uncomfortable with the conclusion that the unauthorized use of a trademark in a metatag represents infringement.
The simple answer is: viewport is good, the others are... less good.
viewport is a widely supported de-facto standard - originally created by Apple for mobile Safari on iPhone, it's been adopted by almost all other mobile browsers: Opera Mobile, iPhone, Android, Iris, IE, BlackBerry, Obigo, Firefox
Simple example use case: make the site full width on mobile:
<meta name="viewport" content="width=device-width, initial-scale=1.0"/> The other two are older de-facto 'standards' for 'feature phones' - which are generally too old to support viewport:
This tag was originally used to identify mobile content in AvantGo browsers, but became a general standard for identifying mobile websites. However, it’s unknown what range of browsers support this meta tag:
<meta name="HandheldFriendly" content="true"/> This is a Windows-proprietary meta tag that also eventually became used as another means of identifying mobile content. The drawback with this tag is that a specific width must be given. Again, it’s unknown what the support for this tag is:
<meta name="MobileOptimized" content="320"/> Use viewport unless you need to support older feature phones which don't support it, in which case, probably use both HandheldFriendly & MobileOptimized - but test your target devices and find out.
Should they be used? Where and when is it appropriate to use them? Are there alternatives (without user-agent recognition)?
They should be used when you want the effects they create - generally, telling phones what default zoom to use, controlling re-sizing, etc. This is a good explanation of why you might want to use viewport, for example: http://davidbcalhoun.com/2010/viewport-metatag - it also lists the other properties that you can set with viewport and what they do.
They only other way to achieve these effects, without using these metatags, is with funky JS tricks - which will be slower, require script loading, be difficult to maintain and will be unreliable. Browsers that don't support viewport will probably have very buggy JS interface to viewport related stuff; see the quirksmode links below.
60
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
