Verification proves you control a website before it goes live on Engado. It is how the network stays real: every site you see belongs to someone who proved it was theirs. Verifying is one step. After it, you activate the website by choosing a plan (free while the founding tier is open), and only then does it appear in Discover and search and start receiving requests.
You only verify once per website. There are four ways to do it, and any one is enough, so pick the one you can do fastest on your setup.
Pick a method
| Method | Best when | What you add |
|---|---|---|
| HTML Meta Tag | You can edit your site’s HTML or theme head | One <meta> tag in <head> |
| DNS TXT Record | You can’t edit the HTML, or your site sits behind a CDN | One TXT record at your DNS host |
| Google Tag Manager | You already run GTM on the site | A Custom HTML tag in your container |
| Google Search Console | The site is already in your Search Console | Nothing. You sign in with Google |
The meta tag is the fastest if you can edit your site. If you can’t, or if the verify screen warns that it can’t reach your site, use DNS or GTM instead. They are not second-class, they just prove the same thing a different way. The verify screen checks whether it can reach your site first, and will point you to DNS or GTM before you try the tag if your site blocks it.
Method 1: HTML Meta Tag
- In Engado, open the website and choose Verify, then HTML Meta Tag.
- Copy the
<meta>tag it shows you. - Paste it inside the
<head>of your site’s home page, alongside the other meta tags. On WordPress, most themes and SEO plugins have a “header scripts” or “custom head” field for exactly this. - Publish the change, then come back to Engado and press Verify.
Engado fetches your home page and looks for the tag. Keep the tag in place.
Method 2: DNS TXT Record
Use this when you can’t edit the HTML, or your host returns a challenge page to anything that isn’t a browser (see Troubleshooting below).
Quickest, if your DNS is at Cloudflare. On the DNS TXT Record step, if your domain’s DNS is managed by Cloudflare, the top option is “Quickest: let Cloudflare add it”. Choose it, and Cloudflare opens an approval screen showing Engado’s name. Approve it, and Cloudflare adds the record for you (root or subdomain) and sends you back to Engado, which checks it straight away. There is no record to copy or paste.
If your DNS is not at Cloudflare, you won’t see that option, so add the record yourself:
- In Engado, choose Verify, then DNS TXT Record (and, below the divider,
“or add it yourself”). Copy the value, which looks like
engado-verification=<code>. - Sign in to wherever your domain’s DNS lives (your registrar or your CDN, for example Cloudflare).
- Add a new record: type TXT; name/host @ (or left blank, depending on your host) for a root domain. If your site is on a subdomain, the name is the subdomain part, and Engado shows you the exact name to use. Paste the value Engado gave you.
- Save it. DNS can take a few minutes to an hour to propagate, sometimes longer. Then press Verify in Engado.
If it doesn’t verify straight away, wait a little and try again. You are waiting on your DNS host, not on Engado.
Method 3: Google Tag Manager
Use this if GTM already runs on the site. It verifies from a real browser visit, so it works even when a server-side fetch of your page would be blocked.
- In Engado, choose Verify, then Google Tag Manager, and copy the snippet it gives you.
- In your GTM container, add it as a Custom HTML tag, then publish the container.
- Visit your own website in a browser tab so the tag fires.
- Press Verify in Engado.
If it doesn’t pass, the usual cause is one of those steps: make sure you have published the container and visited your site after publishing.
Method 4: Google Search Console
- In Engado, choose Verify, then Google Search Console, then Continue with Google.
- Sign in with the Google account that has the site in Search Console as an owner or full user. Restricted users don’t count.
- On Google’s screen, tick the box for Search Console and continue. Google sends you back to Engado, which checks straight away.
The property has to cover the whole site: either a Domain property (for
example example.com, which also covers its subdomains) or a URL-prefix
property for the home page (like https://www.example.com/). A URL-prefix
property is matched loosely here, so you don’t need an exact string match: the
www and bare-domain versions count as the same site, and http or https both
work. A property for https://example.com/ also covers www.example.com.
What Engado sees: the list of properties on that Search Console account, and only to find your site. We don’t look at clicks, impressions, queries or rankings. Google’s screen says Engado can view Search Console data, because that is the narrowest permission Google offers. We revoke our own access straight after the check, so Engado has no ongoing access to your account, and we don’t keep your list of sites.
Troubleshooting
Your security settings blocked our check (a tag-method failure). Some hosts and CDNs show a challenge page or block anything that isn’t a real browser, so Engado’s meta-tag check cannot see your tag no matter how correctly you placed it. Engado will tell you: “Your website’s security settings blocked our check, so we couldn’t see the tag. This is common with hosts like Hostinger and Cloudflare. Use DNS or Google Tag Manager instead: neither needs us to load your site.” Do that. It is not something wrong on your end.
We couldn’t load your website. If Engado says it couldn’t load your site (with the status it got back), the page may be down, private, or blocking the check. Confirm the home page is public, or use DNS or GTM.
The tag is on the page but verification still fails.
Check that the tag is in the <head> of the home page specifically (not a
subpage), that the page is public, and that you published the change. A caching
layer can also serve an old copy of the page for a while, so clear your site or
CDN cache and try again.
DNS verification isn’t picking up. Confirm the record type is TXT, the host is correct for your domain (root or the subdomain Engado shows), and the value matches exactly with no extra quotes or spaces. Then give it time, propagation is the usual cause.
Search Console says it couldn’t find your site. Check you signed in with the right Google account, that you are an owner or full user on the property (not a restricted user), and that the property covers the whole site: a Domain property, or a URL-prefix property for the home page. A property for a single folder or page is not enough.
Google didn’t give us access to your Search Console site list. The box for Search Console was left unticked on Google’s screen. Start again and tick it.
That Google sign-in took too long or came from an old link. Google’s sign-in screen is only good for about 15 minutes. If it sat open longer than that, or you came back to it from an old link, the check won’t complete. Start the Search Console step again from Engado.
What happens after
Verification proves the site is yours. To go live, activate it by choosing a plan (free while the founding tier is open). Once a site is verified and activated it can appear in Discover and search, and send and receive connection requests. Verification is per website, so if you manage several, verify each one. You can use a different method for each.