Site verification

Make the task of site verification easy for search engines and other services, even for non-technical users and without needing access to the back-end hosting account.

Supported site verification methods

Meta tag verification

A meta tag included in the front page of the website. A verification service would provide this in the form:

<meta name="verification-name" content="unique-verification-content" />

Text or HTML File verification

A small text or HTML file served from the website root.

https://example.com/verification-name.html

A user requires the appropriate permission to use file based verifications.

Most verification services now use the meta tag method of verifying site ownership, but the file method is retained for specific cases like reclaiming a Google Analytics account.

While this module overlaps with some functionality from the Metatag project, in many cases users who are allowed to verify sites are not given the permissions required to modify other metatags. The two modules can co-exist.

3.0.x branch - New development

Verifications are stored as site configuration, which can be exported and migrated between sites. eg Between a development and production environment. In previous versions, they are stored in the site_verify database table.

All site verifications are created through the same generic interface. Multiple verifications can be added for the same service, and the admin can uniquely identity each one.

2.1.x branch - Supported legacy

Uses database storage for verifications and still uses specific engines when creating site verifications.

The 3.0.x branch is recommended for new and existing sites.

2.0.x branch - EOL mid-late 2026

Support for older releases of Drupal Core. For newer releases use 2.1.x or 3.0.x (preferable) branch.

Support will be dropped when users fall under 200 or Drupal 10 is no longer supported.

7.x-1.x branch - Unsupported

There is a Backdrop port: https://backdropcms.org/project/site_verify