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

eg .well-known files:
https://example.com/.well-known/apple-developer-merchantid-domain-association

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 or adding .well-known files.

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.x & 4.x branches - Supported and new development

Verifications are stored as site configuration instead of a database table, which can be exported and migrated between sites. eg Between a development and production environment.

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

Drupal 12 support and future development is in 4.x branch, and back-ported to 3.x as needed.

2.x branches - Supported legacy

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

Support for 2.0.x branch ends with Drupal 10.

7.x-1.x branch - Unsupported

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