Documentation

Verifying a domain

Why we ask for this

Anyone can type a domain into a form. We ask you to prove the site is yours. That is why a site marked as verified can be trusted.

It takes a few minutes. You do it once per site.

Choosing a method

There are three ways. Each one counts the same.

  • Work email. You have an email address on the site's domain. The quickest.
  • DNS record. You can change the domain's settings at your DNS provider.
  • Published page. You can publish a page or a post on the site.

Pick the one that is easiest for you. You can switch at any time without starting over.

None of them works for you? Then the site is not yours to verify. If you sell placements on sites you do not own, read about site manager inventory.

Work email

We send a 6-digit code to an address on the site's domain. You type the code in. Done.

  1. Enter an address on the domain, like you@yourdomain.com. An address on a subdomain, like you@mail.yourdomain.com, works too.
  2. Click Send code.
  3. Open the email and type the code on the verification screen.

Good to know:

  • The code works for 15 minutes.
  • After 5 wrong tries, ask for a new code.
  • You can ask for a new code once a minute, a few times a day.
  • Personal addresses do not work. Gmail, Outlook, Yahoo and the like are refused, because anyone can open one.
  • The domain needs a mail server. If it has none, the email could never arrive, so we do not send it. Use the DNS record or a published page instead.

No email after a minute or two? Look in your spam folder first.

DNS record

You add a text record (TXT) in the domain's DNS settings.

It is slower than the others. A new record can take a few minutes to show up, sometimes an hour or more. Add it and run the check. Not found yet? Come back later and run it again. Or just wait: we also check once a day on our own and email you when it passes.

Type
TXT
Name
@
Value
outreachpal-verification=YOUR-CODE

Your code is on the verification screen. Copy the whole value, including outreachpal-verification=.

The tricky part is the Name. @ means the domain itself. Every DNS panel writes it a bit differently. Most accept @. Some want the field empty. A few want your full domain name. If @ is refused, try empty, then the domain.

Where to find DNS settings:

  • Cloudflare: pick the domain, then DNS, then Records, then Add record.
  • GoDaddy: My Products, find the domain, DNS, then Add.
  • Namecheap: Domain List, Manage, Advanced DNS, then Add New Record.
  • Aruba: Pannello di controllo, Domini, Gestione DNS.

Published page

You publish a page with your code on it, then give us its address.

This one is for people who can write on the site but cannot touch anything else. Editors, in-house SEOs, and people who work at an agency often have exactly that. Only someone with access to the site can publish on it, so it proves enough.

It is also the only method for a site that lives on a builder's or a blog host's address, like yourname.wixsite.com, yourname.blogspot.com or yourname.wordpress.com. There the email and the DNS belong to the platform, so the verification screen offers the published page alone.

  1. Pick Published page on the verification screen and copy your code.
  2. Publish a page or post anywhere on the site. Any title works. It has to be live: a draft or a preview is not enough.
  3. Put the code in the text people can see. Not in a comment, not hidden, not in an image.
  4. Open the page, copy its address and paste it in the form.

We keep the address. If the check fails, you retry with one click.

The page must be on the domain you are verifying. yourdomain.com and www.yourdomain.com work. Other subdomains, like blog.yourdomain.com, do not. If your blog is on a subdomain, use another method.

Meta tag and file (older sites only)

We no longer offer these two for new sites. A site that already uses one of them keeps it, and it still works.

Meta tag. One line in the <head> of your homepage, visible to visitors who are not logged in:

<meta name="outreachpal-verification" content="YOUR-CODE">

File. A text file at https://yourdomain.com/.well-known/outreachpal-verification.txt, with your code and nothing else in it. It must load at that exact address, with no redirect.

For both, we try https and http, with and without www.

When the check does not find it

The DNS record is there but nothing happens. Give it time. New records can be slow to show up. Then check how your panel wanted the @ written.

You just published the page and the check does not see it. Caching plugins and CDNs can keep showing the old version for a while. Clear the site's cache if you can, then try again. Often waiting a few minutes is enough.

The page is there and it still fails. Some sites sit behind a security layer, Cloudflare most often. Your visitors see the site, our check gets an error. Nothing is wrong on your side. Use the DNS record or your work email instead: neither needs to open the page.

The code email does not arrive. Check spam. Check the address for typos. Then ask for a new code. If it still does not come, use another method.

Someone already verified this domain. A domain has one owner. If another member verified it first, it is taken. If you think that is wrong, contact us and we will look.

You need a break. Click Continue later. Your progress is saved, and your dashboard takes you back to this step.

After it succeeds

You can remove the record or the page. The site stays verified.

We then measure the site with DataForSEO, usually in a few seconds. If that fails, we measure it the same night. The numbers decide whether the site is listed. See Site requirements.

Each new site needs its own verification.