Returns or sets the title of the media to be played. MediaMetadata.artist Returns or sets the name of the artist, group, creator, etc. Of the media to be played. MediaMetadata.album Returns or sets the name of the album or collection containing the media to be played. MediaMetadata.artwork Returns or sets an array of images associated with playing media. Meta Media, Inc. Is top provider of Web site design, development and online marketing services, specializing in usability, design, back-end development and marketing strategy & execution for retail.
Example
Describe metadata within an HTML document:
<meta charset='UTF-8'>
<meta name='description'>
<meta name='keywords'>
<meta name='author'>
<meta name='viewport'>
</head>
More 'Try it Yourself' examples below.
Definition and Usage
The <meta> tag defines metadata about an HTML document. Metadata is data (information) about data.
<meta> tags always go inside the <head> element, and are typically used to specify character set, page description, keywords, author of the document, and viewport settings.
Metadata will not be displayed on the page, but is machine parsable.
Metadata is used by browsers (how to display content or reload page), search engines (keywords), and other web services.
There is a method to let web designers take control over the viewport (the user's visible area of a web page), through the <meta> tag (See 'Setting The Viewport' example below).
Browser Support
| Element | |||||
|---|---|---|---|---|---|
| <meta> | Yes | Yes | Yes | Yes | Yes |
Attributes
| Attribute | Value | Description |
|---|---|---|
| charset | character_set | Specifies the character encoding for the HTML document |
| content | text | Specifies the value associated with the http-equiv or name attribute |
| http-equiv | content-security-policy content-type default-style refresh | Provides an HTTP header for the information/value of the content attribute |
| name | application-name author description generator keywords viewport | Specifies a name for the metadata |
Global Attributes
The <meta> tag also supports the Global Attributes in HTML.
More Examples
Define keywords for search engines:
Define a description of your web page:
Define the author of a page:
Refresh document every 30 seconds:
Setting the viewport to make your website look good on all devices:
Setting the Viewport
The viewport is the user's visible area of a web page. It varies with the device - it will be smaller on a mobile phone than on a computer screen.
You should include the following <meta> element in all your web pages:
This gives the browser instructions on how to control the page's dimensions and scaling.
The width=device-width part sets the width of the page to follow the screen-width of the device (which will vary depending on the device).
The initial-scale=1.0 part sets the initial zoom level when the page is first loaded by the browser.
Here is an example of a web page without the viewport meta tag, and the same web page with the viewport meta tag:
Tip: If you are browsing this page with a phone or a tablet, you can click on the two links below to see the difference.
With the viewport meta tag
You can read more about the viewport in our Responsive Web Design - The Viewport Tutorial.
Related Pages
HTML tutorial: HTML Head
HTML DOM reference: Meta Object
Default CSS Settings
None.
Take the pain out of building site search with the Algolia hosted API. Start free now!
These days, almost every website encourages visitors to share its pages on social media. We’ve all seen the ubiquitous Facebook and Twitter icons, among others, just begging to be clicked. This comes as no surprise as sharing via social media, the internet incarnation of word-of-mouth, is one of the most effective ways for businesses and individuals to gain awareness.
When users choose to share these links, it is tasked to the web developer to make sure that the associated web pages are properly prepared, which is what we’ll look at now. Facebook and Twitter are, by far, the most popular social media platforms, so let’s focus on those two.
Sharing on Facebook and Twitter
Facebook offers developers various options on how a shared web page appears in its timeline depending on the website’s content. Unless otherwise specified, every website defaults to the type called, appropriately, “website”, which is the example we’ll use.
Let’s say someone has shared the home page of a fictional travel company – Facebook displays it like this:
Twitter, as well, has multiple ways to format shared web pages that appear in its feed, but we’ll look at the one that’s quite similar to the above example from Facebook, which Twitter calls the “Summary Card with Large Image”:
As we can see, each features multiple attributes of the shared Web page:
- a prominent image and title
- a description
- the domain name
Proprietary <meta> Tags
How do we specify these attributes? With <meta> tags. When a link is shared, both Facebook and Twitter scrape the associated web page and read its <meta> tags to display the appropriate information.
Facebook uses <meta> tags leveraging the Open Graph protocol, a classification system for Web pages that extends beyond those <meta> tags already defined in HTML5. A complete list of <meta> tags available can be found at the Open Graph Web site. There are so many from which to choose that it can be somewhat intimidating, but only four are actually required:
Twitter has its own <meta> tags that are similar to the Open Graph protocol, but uses the “twitter” prefix instead of “og”. As with Facebook, only a few are required. The type of display format we’re requesting from Twitter is also specified:
Both Facebook and Twitter offer guidelines on how to use the above <meta> tags. They are quite similar to each other, although they can be somewhat subjective in interpretation. Note that, for our purposes, Facebook is referring to the shared Web page when using the term “object”:
| Title | The title, headline or name of the object. | A concise title for the related content. [Maximum 70 characters.] |
| Description | A short description or summary of the object. [Between 2 and 4 sentences.] | A description that concisely summarizes the content as appropriate for presentation within a Tweet. You should not re-use the title as the description or use this field to describe the general services provided by the website. [Maximum 200 characters.] |
| Image | The URL of the image for your object. It should be at least 600×315 pixels, but 1200×630 or larger is preferred (up to 5MB). Stay close to a 1.91:1 aspect ratio to avoid cropping. | A URL to a unique image representing the content of the page. You should not use a generic image such as your website logo, author photo, or other image that spans multiple pages. Images for this Card should be at least 280px in width, and at least 150px in height. Image must be less than 1MB in size. |
| URL | The canonical URL for your page. This should be the undecorated URL, without session variables, user identifying parameters, or counters. |
Since these proprietary <meta> tags are, in the end, referring to the same elements, it would be ideal if there were somehow a way to reconcile the two. Fortunately, there is.
Reconciling <meta> Tags
There’s no harm with having multiple <meta> tags that appear redundant. Too much information never hurt anyone except by adding a few extra bytes to the HTML file.
But for our purposes, and for the sake of brevity, we can leverage the fact that Twitter allows us to substitute Open Graph <meta> tags for its own. In the end, except for the necessity of specifying a display format, none of the custom Twitter <meta> tags are needed. This gives us the following, which could be considered the bare minimum of <meta> tags necessary to make a web page amenable for sharing on social media:
Reconciling the guidelines for the image is simple: follow Facebook’s recommendation of a minimum dimension of 1200×630 pixels and an aspect ratio of 1.91:1, but adhere to Twitter’s file size requirement of less than 1MB.
Validating <meta> Tags
If there are any doubts about the legitimacy of paring down to these five tags, we can use the helpful Facebook Sharing Debugger and Twitter Card Validator. Both these tools will scrape any Web page hosted on a public server for relevant <meta> tags and display how it would look when shared. It will also list any errors and provide suggestions. So how did we do with our particular example? Twitter seems fine with things, but Facebook, on the other hand, lists one item as a warning:
This provides a perfect segue to talk about…
Social Media Analytics
What Facebook is indicating is that if you’re going to use their analytics tool, which they call Domain Insights, you must provide the unique ID number associated with your account. The <meta> tag would then look something like this:
Twitter has something similar that they call Twitter Card Analytics. To get the most out of this tool, Twitter recommends using the following <meta> tag that contains the Twitter username that you want associated with the shared Web page:
Keep in mind, though, that if you have no particular interest in using these analytic tools, then omitting the above two <meta> tags has no effect on how a shared Web page appears on a Facebook timeline or Twitter feed.
Anything Else?
Facebook documentation recommends one additional <meta> tag, though it’s not required. A <meta> tag that denotes the name of the Web site in which the shared page resides:
Twitter suggests one other <meta> tag as well that is recommended, but not required:
This provides an alternative image description for those who are visually impaired.
Final Markup
That should do it. To reiterate, when you look at documentation from Facebook and Twitter for sharing Web pages, there are many other <meta> tags available that can be used to specify different types of content. But, in general, the following will suffice:
Media Metadata Editor
Resources
Media Metals
- The Open Graph Protocol
Facebook: A Guide to Sharing for Webmasters