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.
Contact settings
Allow other users to contact you via a personal contact form which keeps your email address hidden. Note that some privileged users such as site administrators are still able to contact you even if you choose to disable this feature.
Your virtual face or picture.
One file only.
125 KB limit.
Allowed types: png gif jpg jpeg webp.

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.
A location's two-letter international country code, with an optional two-letter region, e.g. 'US-NH' for New Hampshire in the USA.
Geo-spatial information in 'latitude, longitude' format, e.g. '50.167958, -97.133185'; see Wikipedia for details.
Geo-spatial information in 'latitude; longitude' format, e.g. '50.167958; -97.133185'; see Wikipedia for details.
A location's formal name.
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
A link to the preferred page location or URL of the content of this page, to help eliminate duplicate content penalties from search engines.
A brief URL, often created by a URL shortening service.
Used for paginated content by providing URL with rel='prev' link.
Used for paginated content by providing URL with rel='next' link.
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.
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.
Define the author of a page.
Describes the name and version number of the software or publishing tool used to create the page.
Details about intellectual property, such as copyright or trademarks; does not automatically protect the site's content or intellectual property.
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
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.
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.
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.
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.
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.
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.
A set of meta tags specially for controlling the summaries displayed when content is shared on Twitter.
Notes:
  • no other fields are required for a Summary card
  • Media player card requires the 'title', 'description', 'media player URL', 'media player width', 'media player height' and 'image' fields,
  • Summary Card with Large Image card requires the 'Summary' field and the 'image' field,
  • App Card requires the 'iPhone app ID' field, the 'iPad app ID' field and the 'Google Play app ID' field,
The @username for the website, which will be displayed in the Card's footer; must include the @ symbol.
A description that concisely summarizes the content of the page, as appropriate for presentation within a Tweet. Do not re-use the title text as the description, or use this field to describe the general services provided by the website. The string will be truncated, by Twitter, at the word to 200 characters.
The page's title, which should be concise; it will be truncated at 70 characters by Twitter. This field is required unless this the 'type' field is set to 'photo'.
The numerical Twitter account ID for the website, which will be displayed in the Card's footer.
The @username for the content creator / author for this page, including the @ symbol.
The numerical Twitter account ID for the content creator / author for this page.
The URL to a unique image representing the content of the page. Do not use a generic image such as your website logo, author photo, or other image that spans multiple pages. Images larger than 120x120px will be resized and cropped square based on longest dimension. Images smaller than 60x60px will not be shown. If the 'type' is set to Photo then the image must be at least 280x150px. This will be able to extract the URL from an image field if the field is configured properly.
The alternative text of the image being linked to. Limited to 420 characters.
If your application is not available in the US App Store, you must set this value to the two-letter country code for the App Store that contains your application.
The name of the iPhone app.
String value, should be the numeric representation of your iPhone app's ID in the App Store.
The iPhone app's custom URL scheme (must include "://" after the scheme name).
The name of the iPad app.
String value, should be the numeric representation of your iPad app's ID in the App Store.
The iPad app's custom URL scheme (must include "://" after the scheme name).
The name of the app in the Google Play app store.
Your app ID in the Google Play Store (i.e. "com.android.app").
The Google Play app's custom URL scheme (must include "://" after the scheme name).
The full URL for loading a media player, specifically an iframe for an embedded video rather than the URL to a page that contains a player. Required when using the Player Card type.
The width of the media player iframe, in pixels. Required when using the Player Card type.
The height of the media player iframe, in pixels. Required when using the Player Card type.
The full URL for an MP4 video (h.264) or audio (AAC) stream, takes precedence over the other media player field.
The MIME type for the media contained in the stream URL, as defined by RFC 4337.