← Docs

Tag Watch: getting started

  1. Sign in, open Tag Watch and start the trial (or subscribe).
  2. Add a site by its hostname, for example www.example.com.
  3. Verify that you control it. Either add a DNS TXT record with the value lindenkit-verify=<your token> on the hostname (or on a parent name such as example.com), or add <meta name="lindenkit-verify" content="<your token>"> to the home page. We look up the TXT record through Cloudflare's DNS-over-HTTPS service. The meta tag must be in the page's <head>. The meta-tag option fetches the site's robots.txt and then the home page when you press Verify (redirects followed only within the site; at most 5 such checks per domain per hour). Nothing else is fetched from a site before it is verified. We re-check the record or tag about once a week; if it is missing twice, or cannot be checked four weeks in a row, monitoring pauses. You also confirm that you control the site or are authorised by its owner to monitor it.
  4. Add up to 5 key URLs on that hostname: pages whose tags matter, such as the home page, a landing page and a lead form. Checkout and payment pages are not accepted.
  5. Each URL is checked about once a day. The first check records what is there; after that, changes go into a daily digest. A missing tag also triggers an immediate email, once it is seen on two consecutive checks (the second check runs about two hours after the first).

What counts as a change

Tag Watch reads the HTML your server returns. It does not run the page, so it cannot see tags that other scripts add later, tags a consent tool holds back until a visitor agrees, tags added by custom or server-side loaders without the standard install code, what a Partytown worker loads, or tags on pages it is not watching.