How do I set default meta tags in Drupal's Metatag module?

Definition: As of October 2026, Drupal's Metatag module manages default metadata through global settings, entity-type defaults and bundle defaults. Each more specific configuration inherits from the broader one, with a Metatag field allowing overrides for an individual entity.

Key facts

• The module's README identifies admin/config/search/metatag as the configuration path and describes global defaults as the base inherited by other defaults.
• The shipped Global configuration uses [current-page:title] | [site:name] for the title.
• The shipped Content configuration supplies [node:title] | [site:name] for the title and [node:summary] for the description.

Where are global defaults configured?

A meta tag supplies metadata about a page. The module's configuration instructions direct administrators to install Metatag and open this path:

/admin/config/search/metatag

Global defaults form the base configuration. Editing these values sets the shared starting point for the more specific configurations that inherit them. The defaults form saves the configured tags.

A token is a placeholder that supplies a value dynamically. The README permits tokens in defaults, so a shared title template can use page-specific values. The shipped Global configuration uses this title value:

[current-page:title] | [site:name]

How do entity-type and bundle defaults differ?

An entity is a Drupal content object; a node is a content entity. A bundle is a subtype, such as a content type for nodes or a vocabulary for taxonomy terms. The README's inheritance instructions explain that entity-type defaults inherit from Global. Content pages and taxonomy term pages can therefore have separate defaults.

For a particular bundle, the documented action is Add default meta tags. Selecting the bundle and completing the form creates defaults that override the entity-type configuration. The README gives a concrete use: a content type can use its own image field for image metadata.

The shipped Content configuration illustrates entity-specific token values:

title: '[node:title] | [site:name]'
description: '[node:summary]'
canonical_url: '[node:url]'

These are values for Content defaults; the broader Global configuration uses current-page tokens.

How are individual page overrides enabled?

The README's field setup instructions require a Metatag field before metadata can be adjusted for a specific entity. In the bundle's Manage fields screen, the administrator selects Meta tags under Add a new field, supplies a label and machine name, then selects Save and continue.

For translated entities, the instructions also identify Users may translate this field. The README explains that individual values merge with defaults before output, so an individual record only needs its customized values.

Which configuration applies to special pages?

The README identifies separate defaults for the front page and the 403 and 404 error pages. These configurations belong in the review when those pages need their own metadata. The same documentation states that Metatag outputs no meta tags while the site is in maintenance mode.

Related terms

• How do I use tokens in Drupal meta tag templates?
• How do I set canonical links with Drupal Metatag?
• How do I restrict who can edit meta tags in Drupal?

FAQ

Can I give a content type its own default tags?

Yes. The README instructs you to select Add default meta tags, choose the bundle and complete the form. Its values override the entity-type defaults.

Do I need a Metatag field to configure global defaults?

The same README treats global configuration and individual entity editing separately. You add a Metatag field when you want editors to override metadata on individual entities.

Sources

1. Drupal Metatag project, "Metatag README", undated
2. Drupal Metatag project, "metatag.metatag_defaults.global.yml", undated
3. Drupal Metatag project, "metatag.metatag_defaults.node.yml", undated
4. Drupal Metatag project, "MetatagDefaultsForm.php", undated

---

Check how a page reads to answer engines. Open the GEO score analyzer