Skip to main content

Create new account

The email address is not made public. It will only be used if you need to be contacted about your account or for opted-in notifications.
Several special characters are allowed, including space, period (.), hyphen (-), apostrophe ('), underscore (_), and the @ sign.
Provide a password for the new account in both fields.
Newsletter
Subscriptions
Check the newsletters you want to subscribe to.
Locale settings
Select the desired local time and time zone. Dates and times throughout this site will be displayed using this time zone.
Your virtual face or picture.
One file only.
800 KB limit.
Allowed types: png gif jpg jpeg.
Images larger than 1024x1024 pixels will be resized.

Configure the meta tags below.

Use tokens to avoid redundant meta data and search engine penalization. For example, a 'keyword' value of "example" will be shown on all content using this configuration, whereas using the [node:field_keywords] automatically inserts the "keywords" values from the current entity (node, term, etc).

Browse available tokens.
Basic tags
Simple meta tags.
The text to display in the title bar of a visitor's web browser when they view this page. This meta tag may also be used as the title of the page when a visitor bookmarks or favorites this page, or as the page title in a search engine result. It is common to append '[site:name]' to the end of this, so the site's name is automatically added. It is recommended that the title is no greater than 55 - 65 characters long, including spaces.
A brief and concise summary of the page's content that is a maximum of 160 characters in length. The description meta tag may be used by search engines to display a snippet about the page in search results.
A brief and concise summary of the page's content, preferably 150 characters or less. Where as the description meta tag may be used by search engines to display a snippet about the page in search results, the abstract tag may be used to archive a summary about the page. This meta tag is no longer supported by major search engines.
A comma-separated list of keywords about the page. This meta tag is no longer supported by most search engines.
Advanced
Meta tags that might not be needed by many sites.
Geo-spatial information in 'latitude; longitude' format, e.g. '50.167958; -97.133185'; see Wikipedia for details.
A location's formal name.
Geo-spatial information in 'latitude, longitude' format, e.g. '50.167958, -97.133185'; see Wikipedia for details.
A location's two-letter international country code, with an optional two-letter region, e.g. 'US-NH' for New Hampshire in the USA.
A link to the preferred page location or URL of the content of this page, to help eliminate duplicate content penalties from search engines.
Robots
Provides search engines with specific directions for what to do when this page is indexed.
Use a number character as a textual snippet for this search result. "0" equals "nosnippet". "-1" will let the search engine decide the most effective length.
Use a maximum of number seconds as a video snippet for videos on this page in search results. "0" will use a static a image. "-1" means there is no limit.
Set the maximum size of an image preview for this page in a search results.
Do not show this page in search results after the specified date
DEPRECATED. Used to define this page's language code. May be the two letter language code, e.g. "de" for German, or the two letter code with a dash and the two letter ISO country code, e.g. "de-AT" for German in Austria. Still used by Bing.
A brief URL, often created by a URL shortening service.
Used for paginated content by providing URL with rel='next' link.
A comma-separated list of keywords about the page. This meta tag is used as an indicator in Google News.
Used for paginated content by providing URL with rel='prev' link.
Highlight standout journalism on the web, especially for breaking news; used as an indicator in Google News. Warning: Don't abuse it, to be used a maximum of 7 times per calendar week!
An image associated with this page, for use as a thumbnail in social networks and other services. This will be able to extract the URL from an image field if the field is configured properly.
Describes the name and version number of the software or publishing tool used to create the page.
Define the author of a page.
Used to indicate the URL that broke the story, and can link to either an internal URL or an external source. If the full URL is not known it is acceptable to use a partial URL or just the domain name.
Sets a cookie on the visitor's browser. Can be in either NAME=VALUE format, or a more verbose format including the path and expiration date; see the link for full details on the syntax.
The number of seconds to wait before refreshing the page. May also force redirect to another page using the format '5; url=https://example.com/', which would be triggered after five seconds.
This meta tag communicates with Google. There are currently two directives supported: 'nositelinkssearchbox' to not to show the sitelinks search box, and 'notranslate' to ask Google not to offer a translation of the page. Both options may be added, just separate them with a comma. See meta tags that Google understands for further details.
Indicate to search engines and other page scrapers whether or not links should be followed. See the W3C specifications for further details. Note: this serves the same purpose as the HTTP header by the same name.
Used to rate content for audience appropriateness. This tag has little known influence on search engine rankings, but can be used by browsers, browser extensions, and apps. The most common options are general, mature, restricted, 14 years, safe for kids. If you follow the RTA Documentation you should enter RTA-5042-1996-1400-1577-RTA
Details about intellectual property, such as copyright or trademarks; does not automatically protect the site's content or intellectual property.
Tell search engines when to index the page again. Very few search engines support this tag, it is more useful to use an XML Sitemap file.
Used to control whether a browser caches a specific page locally. Not commonly used. Should be used in conjunction with the Pragma meta tag.
Control when the browser's internal cache of the current page should expire. The date must to be an RFC-1123-compliant date string that is represented in Greenwich Mean Time (GMT), e.g. 'Thu, 01 Sep 2016 00:12:56 GMT'. Set to '0' to stop the page being cached entirely.
Used to control whether a browser caches a specific page locally. Not commonly used. Should be used in conjunction with the Cache-Control meta tag.
Meta tags for displaying favicons of various sizes and types. All values should be either absolute or relative URLs. No effects are added to the "precomposed" icons.
The traditional favicon, must be either a GIF, ICO, JPG/JPEG or PNG image. This will be able to extract the URL from an image field if the field is configured properly.
A grayscale scalable vector graphic (SVG) file.
Color attribute for SVG (mask) icon in hexadecimal format, e.g. '#0000ff'. Setting it will break HTML validation. If not set macOS Safari ignores the Mask Icon entirely, making the Icon: SVG completely useless.
A PNG image that is 16px wide by 16px high. This will be able to extract the URL from an image field if the field is configured properly.
A PNG image that is 32px wide by 32px high. This will be able to extract the URL from an image field if the field is configured properly.
A PNG image that is 96px wide by 96px high. This will be able to extract the URL from an image field if the field is configured properly.
A PNG image that is 192px wide by 192px high. This will be able to extract the URL from an image field if the field is configured properly.
A PNG image that is 60px wide by 60px high. Used with the non-Retina iPhone, iPod Touch, and Android 2.1+ devices. This will be able to extract the URL from an image field if the field is configured properly.
A PNG image that is 72px wide by 72px high. Used with the iPad mini and the first- and second-generation iPad (@1x display) on iOS <= 6. This will be able to extract the URL from an image field if the field is configured properly.
A PNG image that is 76px wide by 76px high. Used with the iPad mini and the second-generation iPad (@1x display) on iOS >= 7. This will be able to extract the URL from an image field if the field is configured properly.
A PNG image that is 114px wide by 114px high. Used with iPhone with @2x display running iOS <= 6. This will be able to extract the URL from an image field if the field is configured properly.
A PNG image that is 120px wide by 120px high. Used with iPhone with @2x display running iOS >= 7. This will be able to extract the URL from an image field if the field is configured properly.
A PNG image that is 144px wide by 144px high. Used with iPad with @2x display running iOS <= 6. This will be able to extract the URL from an image field if the field is configured properly.
A PNG image that is 152px wide by 152px high. Used with iPad with @2x display running iOS >= 7. This will be able to extract the URL from an image field if the field is configured properly.
A PNG image that is 180px wide by 180px high. Used with iPhone 6 Plus with @3x display. This will be able to extract the URL from an image field if the field is configured properly.
A PNG image that is 57px wide by 57px high. Used with the non-Retina iPhone, iPod Touch, and Android 2.1+ devices. This will be able to extract the URL from an image field if the field is configured properly.
A PNG image that is 72px wide by 72px high. Used with the iPad mini and the first- and second-generation iPad (@1x display) on iOS <= 6. This will be able to extract the URL from an image field if the field is configured properly.
A PNG image that is 76px wide by 76px high. Used with the iPad mini and the second-generation iPad (@1x display) on iOS >= 7. This will be able to extract the URL from an image field if the field is configured properly.
A PNG image that is 114px wide by 114px high. Used with iPhone with @2x display running iOS <= 6. This will be able to extract the URL from an image field if the field is configured properly.
A PNG image that is 120px wide by 120px high. Used with iPhone with @2x display running iOS >= 7. This will be able to extract the URL from an image field if the field is configured properly.
A PNG image that is 144px wide by 144px high. Used with iPad with @2x display running iOS <= 6. This will be able to extract the URL from an image field if the field is configured properly.
A PNG image that is 152px wide by 152px high. Used with iPad with @2x display running iOS >= 7. This will be able to extract the URL from an image field if the field is configured properly.
A PNG image that is 180px wide by 180px high. Used with iPhone 6 Plus with @3x display. This will be able to extract the URL from an image field if the field is configured properly.
Open Graph
The Open Graph meta tags are used to control how Facebook, Pinterest, LinkedIn and other social networking sites interpret the site's content.

The Facebook Sharing Debugger lets you preview how your content will look when it's shared to Facebook and debug any issues with your Open Graph tags.
The word that appears before the content's title in a sentence. The default ignores this value, the 'Automatic' value should be sufficient if this is actually needed.
A human-readable name for the site, e.g., IMDb.
The type of the content, e.g., movie.
Preferred page location or URL to help eliminate duplicate content for search engines, e.g., https://www.imdb.com/title/tt0117500/.
The title of the content, e.g., The Rock.
A one to two sentence description of the content.
The URL of an video which should represent the content. For best results use a source that is at least 1200 x 630 pixels in size, but at least 600 x 316 pixels is a recommended minimum. Object types supported include video.episode, video.movie, video.other, and video.tv_show. Multiple values may be used, separated by a comma. Note: Tokens that return multiple values will be handled automatically.
The URL of an image which should represent the content. The image must be at least 200 x 200 pixels in size; 600 x 316 pixels is a recommended minimum size, and for best results use an image least 1200 x 630 pixels in size. Supports PNG, JPEG and GIF formats. Should not be used if og:image:url is used. Note: if multiple images are added many services (e.g. Facebook) will default to the largest image, not specifically the first one. Multiple values may be used, separated by a comma. Note: Tokens that return multiple values will be handled automatically. This will be able to extract the URL from an image field if the field is configured properly.
A alternative version of og:image and has exactly the same requirements; only one needs to be used. Multiple values may be used, separated by a comma. Note: Tokens that return multiple values will be handled automatically. This will be able to extract the URL from an image field if the field is configured properly.
The secure URL (HTTPS) of an video which should represent the content. Any URLs which start with "http://" will be converted to "https://".
The secure URL (HTTPS) of an image which should represent the content. The image must be at least 200 x 200 pixels in size; 600 x 316 pixels is a recommended minimum size, and for best results use an image least 1200 x 630 pixels in size. Supports PNG, JPEG and GIF formats. Multiple values may be used, separated by a comma. Note: Tokens that return multiple values will be handled automatically. This will be able to extract the URL from an image field if the field is configured properly. Any URLs which start with "http://" will be converted to "https://".
The type of image referenced above. Should be either 'image/gif' for a GIF image, 'image/jpeg' for a JPG/JPEG image, or 'image/png' for a PNG image. Note: there should be one value for each image, and having more than there are images may cause problems.
The type of video referenced above. Should be either video.episode, video.movie, video.other, and video.tv_show. Note: there should be one value for each video, and having more than there are videos may cause problems.
The width of the above image(s). Note: if both the unsecured and secured images are provided, they should both be the same size.
The height of the above video(s). Note: if both the unsecured and secured videos are provided, they should both be the same size.
The height of the above image(s). Note: if both the unsecured and secured images are provided, they should both be the same size.
The height of the above video(s). Note: if both the unsecured and secured videos are provided, they should both be the same size.
The date this content was last modified, with an optional time value. Needs to be in ISO 8601 format. Can be the same as the 'Article modification date' tag.
A description of what is in the image, not a caption. If the page specifies an og:image it should specify og:image:alt.
The length of the video in seconds
URLs to related content
The locale these tags are marked up in, must be in the format language_TERRITORY. Default is 'en_US'.
Other locales this content is available in, must be in the format language_TERRITORY, e.g. 'fr_FR'. Multiple values may be used, separated by a comma. Note: Tokens that return multiple values will be handled automatically.
Links an article to an author's Facebook profile, should be either URLs to the author's profile page or their Facebook profile IDs. Multiple values may be used, separated by a comma. Note: Tokens that return multiple values will be handled automatically.
Links an article to a publisher's Facebook page.
The primary section of this website the content belongs to.
Appropriate keywords for this content. Multiple values may be used, separated by a comma. Note: Tokens that return multiple values will be handled automatically.
The date this content was published on, with an optional time value. Needs to be in ISO 8601 format.
The date this content was last modified, with an optional time value. Needs to be in ISO 8601 format.
The date this content will expire, with an optional time value. Needs to be in ISO 8601 format.
Links a book to an author's Facebook profile, should be either URLs to the author's profile page or their Facebook profile IDs. Multiple values may be used, separated by a comma. Note: Tokens that return multiple values will be handled automatically.
The Book's ISBN
The date the book was released.
Appropriate keywords for this content. Multiple values may be used, separated by a comma. Note: Tokens that return multiple values will be handled automatically.
The URL to an audio file that complements this object.
The secure URL to an audio file that complements this object. All 'http://' URLs will automatically be converted to 'https://'. Any URLs which start with "http://" will be converted to "https://".
The MIME type of the audio file. Examples include 'application/mp3' for an MP3 file.
The first name of the person who's Profile page this is.
The person's last name.
Any of Facebook's gender values should be allowed, the initial two being 'male' and 'female'.
A pseudonym / alias of this person.
Links to the Facebook profiles for actor(s) that appear in the video. Multiple values may be used, separated by a comma. Note: Tokens that return multiple values will be handled automatically.
The roles of the actor(s). Multiple values may be used, separated by a comma. Note: Tokens that return multiple values will be handled automatically.
Links to the Facebook profiles for director(s) that worked on the video. Multiple values may be used, separated by a comma. Note: Tokens that return multiple values will be handled automatically.
The date the video was released.
The TV show this series belongs to.
Tag words associated with this video. Multiple values may be used, separated by a comma. Note: Tokens that return multiple values will be handled automatically.
Links to the Facebook profiles for scriptwriter(s) for the video. Multiple values may be used, separated by a comma. Note: Tokens that return multiple values will be handled automatically.
Provides the fifteen Dublin Core Metadata Element Set 1.1 meta tags from the Dublin Core Metadata Institute
The name given to the resource.
An entity primarily responsible for making the resource. Examples of a Creator include a person, an organization, or a service. Typically, the name of a Creator should be used to indicate the entity.
The topic of the resource. Typically, the subject will be represented using keywords, key phrases, or classification codes. Recommended best practice is to use a controlled vocabulary. To describe the spatial or temporal topic of the resource, use the Coverage element.
An account of the resource. Description may include but is not limited to: an abstract, a table of contents, a graphical representation, or a free-text account of the resource.
An entity responsible for making the resource available. Examples of a Publisher include a person, an organization, or a service. Typically, the name of a Publisher should be used to indicate the entity.
An entity responsible for making contributions to the resource. Examples of a Contributor include a person, an organization, or a service. Typically, the name of a Contributor should be used to indicate the entity.
A point or period of time associated with an event in the lifecycle of the resource. Date may be used to express temporal information at any level of granularity. Recommended best practice is to use an encoding scheme, such as the W3CDTF profile of ISO 8601 [W3CDTF].
The nature or genre of the resource. Recommended best practice is to use a controlled vocabulary such as the DCMI Type Vocabulary [DCMITYPE]. To describe the file format, physical medium, or dimensions of the resource, use the Format element.
The file format, physical medium, or dimensions of the resource. Examples of dimensions include size and duration. Recommended best practice is to use a controlled vocabulary such as the list of Internet Media Types [MIME].
An unambiguous reference to the resource within a given context. Recommended best practice is to identify the resource by means of a string conforming to a formal identification system.
A related resource from which the described resource is derived. The described resource may be derived from the related resource in whole or in part. Recommended best practice is to identify the related resource by means of a string conforming to a formal identification system.
A language of the resource. Recommended best practice is to use a controlled vocabulary such as RFC 4646 [RFC4646].
A related resource. Recommended best practice is to identify the related resource by means of a string conforming to a formal identification system.
The spatial or temporal topic of the resource, the spatial applicability of the resource, or the jurisdiction under which the resource is relevant. Spatial topic and spatial applicability may be a named place or a location specified by its geographic coordinates. Temporal topic may be a named period, date, or date range. A jurisdiction may be a named administrative entity or a geographic place to which the resource applies. Recommended best practice is to use a controlled vocabulary such as the Thesaurus of Geographic Names [TGN]. Where appropriate, named places or time periods can be used in preference to numeric identifiers such as sets of coordinates or date ranges.
Information about rights held in and over the resource. Typically, rights information includes a statement about various property rights associated with the resource, including intellectual property rights.
A set of meta tags specially for controlling advanced functionality with Facebook.

The Facebook Sharing Debugger lets you preview how your content will look when it's shared to Facebook and debug any issues with your Open Graph tags.
Facebook Instant Articles claim URL token.
A comma-separated list of Facebook user IDs of people who are considered administrators or moderators of this page.
A comma-separated list of Facebook Platform Application IDs applicable for this site.