Why verification exists
Some Wrendex features (Slack alerts on private endpoints, share-link defaults, full audit history retention) are only available on sites where ownership has been verified. This prevents one workspace from claiming the audit history of a site they do not control.
Option 1: DNS TXT record
From the site settings page, copy the verification token. Add a TXT record at the apex of the domain with the value 'wrendex-verify=<token>'. Wrendex polls every fifteen minutes; verification typically completes within an hour of DNS propagation. TXT records work for sites where you cannot edit the page head.
Option 2: meta tag
From the site settings page, copy the verification meta tag and paste it into the head of the homepage. Wrendex re-fetches the homepage every fifteen minutes; verification typically completes on the next fetch. Meta tags work for sites where you can edit the template but not DNS.
Re-verification
Verification is a one-time check; once it succeeds, the verification record can be removed if you prefer. Wrendex does not poll the verification record after the initial success unless you explicitly re-verify.