our satisfied customers

Testimonials

The service is exceptional. Very knowledgeable staff!

Tracy Martin

Leave us your comments

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.

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. It is common to append '[site:name]' to the end of this, so the site's name is automatically added.

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.
Geo-spatial information in 'latitude, longitude' format, e.g. '50.167958, -97.133185'; see Wikipedia for details.
Robots
A comma-separated list of keywords about the page. This meta tag is used as an indicator in Google News.
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!
Indicate to search engines and other page scrapers whether or not links should be followed. See the W3C specifications for further details.

The Open Graph meta tags are used control how Facebook, Pinterest, LinkedIn and other social networking sites interpret the site's content.

The URL of an image which should represent the content. For best results use an image that is at least 1200 x 630 pixels in size, but at least 600 x 316 pixels is a recommended minimum. Supports PNG, JPEG and GIF formats. Should not be used if og:image:url is 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.
The URL of an video which should represent the content. For best results use an image that is at least 1200 x 630 pixels in size, but at least 600 x 316 pixels is a recommended minimum. Supports PNG, JPEG and GIF formats. Should not be used if og:image:url is used. Multiple values may be used, separated by a comma. Note: Tokens that return multiple values will be handled automatically.
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.
The secure URL (HTTPS) of an image which should represent the content. The image must be at least 50px by 50px and have a maximum aspect ratio of 3:1. Supports PNG, JPEG and GIF formats. All 'http://' URLs will automatically be converted to 'https://'. This will be able to extract the URL from an image field. Any links containing http:// will be converted to https://
The secure URL (HTTPS) of an video which should represent the content. The video must be at least 50px by 50px and have a maximum aspect ratio of 3:1. Supports PNG, JPEG and GIF formats. All 'http://' URLs will automatically be converted to 'https://'. Any links containing 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/gif' for a GIF video, 'video/jpeg' for a JPG/JPEG video, or 'video/png' for a PNG video. Note: there should be one value for each video, and having more than there are videos may cause problems.
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.
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.

A set of meta tags specially for controlling the summaries displayed when content is shared on Google Plus.

The URL of an image which should represent the content. For best results use an image that is at least 1200 x 630 pixels in size, but at least 600 x 316 pixels is a recommended minimum. 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.

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, a Photo card requires the 'image' field, a Media player card requires the 'title', 'description', 'media player URL', 'media player width', 'media player height' and 'image' fields, a Summary Card with Large Image card requires the 'Summary' field and the 'image' field, a Gallery Card requires all the 'Gallery Image' fields, an App Card requires the 'iPhone app ID' field, the 'iPad app ID' field and the 'Google Play app ID' field, a Product Card requires the 'description' field, the 'image' field, the 'Label 1' field, the 'Data 1' field, the 'Label 2' field and the 'Data 2' field.
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 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. This will be able to extract the URL from an image field.
The MIME type for the media contained in the stream URL, as defined by RFC 4337.

A set of meta tags specially for controlling advanced functionality with Facebook.

These meta tags are used to confirm site ownership for search engines and other services.

A string provided by Baidu.
A string provided by Bing, full details are available from the Bing online help.
A string provided by Google, full details are available from the Google online help.
A string provided by Norton Safe Web, full details are available from the Norton Safe Web online help.
A string provided by Pinterest, full details are available from the Pinterest online help.
A string provided by Yandex, full details are available from the Yandex online help.

These meta tags are designed to point visitors to versions of the current page in other languages.

Meta tags used to control the mobile browser experience. Some of these meta tags have been replaced by newer mobile browsers. These meta tags usually only need to be set globally, rather than per-page.

Meta tags used to control the mobile browser experience. Some of these meta tags have been replaced by newer mobile browsers. These meta tags usually only need to be set globally, rather than per-page.

Using the value 'width' tells certain mobile Internet Explorer browsers to display as-is, without being resized. Alternatively a numerical width may be used to indicate the desired page width the page should be rendered in: '240' is the suggested default, '176' for older browsers or '480' for newer devices with high DPI screens. Multiple values may be used, separated by a comma. Note: Tokens that return multiple values will be handled automatically.
Some older mobile browsers will expect this meta tag to be set to 'true' to indicate that the site has been designed with mobile browsers in mind. Multiple values may be used, separated by a comma. Note: Tokens that return multiple values will be handled automatically.

Custom meta tags used by Apple's software, iOS, Safari, etc.

Custom meta tags used by the Android OS, browser, etc.

A URL to a manifest.json file that describes the application. The JSON-based manifest provides developers with a centralized place to put metadata associated with a web application.

Custom meta tags used by the Windows and Windows Mobile OSes, IE browser, etc.

A semi-colon -separated string that must contain the 'polling-uri=' value with the full URL to a Badge Schema XML file. May also contain 'frequency=' value set to either 30, 60, 360, 720 or 1440 (default) which specifies (in minutes) how often the URL should be polled.
Should contain the full URL to a Browser configuration schema file that further controls tile customizations.
A semi-colon -separated string containing 'polling-uri=' (required), 'polling-uri2=', 'polling-uri3=', 'polling-uri4=' and 'polling-uri5=' to indicate the URLs for notifications. May also contain a 'frequency=' value to specify how often (in minutes) the URLs will be polled; limited to 30, 60, 360, 720 or 1440 (default). May also contain the value 'cycle=' to control the notifications cycle.
A semi-colon -separated string defining the 'jump' list task. Should contain the 'name=' value to specify the task's name, the 'action-uri=' value to set the URL to load when the jump list is clicked, the 'icon-uri=' value to set the URL to an icon file to be displayed, and 'window-type=' set to either 'tab' (default), 'self' or 'window' to control how the link opens in the browser.