How to Verify Domain Property in Google Search Console via DNS

Yesterday, Google announced that Domain properties are coming to the new Google Search Console. It means that now you will have a full picture of what’s happening with all versions of your website: https, http, m., www, non-www…

As you know, Google treats such versions as separate websites. It makes sense from a technical point of view, but for users and webmasters this involved too many unneeded steps. So it’s really great Google added this feature.

To verify your domain ownership in Google Search Console, you will need access to your hosting and add a txt DNS record there. And by the end of this post, you’ll do this even if you have no idea what a DNS record is.

Verifying Domain Property in Google Search Console

Here’s a video of the process in case you prefer visual content:

In order to verify domain ownership, complete the following steps:

  1. Go to Google Search Console.
  2. Click ‘Add Property’.
  3. Choose Domain and enter your domain name:
  4. Click ‘Continue’, you’ll be redirected to the next step.
  5. Copy the domain verification TXT record you’ll get:
  6. Log into your hosting. I’ll be using cPanel as an example as I’m on GreenGeeks hosting. You can find specific info for your hosting here.
  7. Find Zone Editor under Domains:
  8. Choose the domain you need to verify in Google Search Console and click ‘Manage’.
  9. Add a record and select TXT as a record type.
  10. Fill in the rest of the fields with the following information:
    • Valid zone name – your domain name
    • TTL – 3600
    • Text – your verification text copied in step 3.

  11. Once you’ve filled in all the fields, click ‘Add record’ to save it.
  12. Go back to Google Search Console and click ‘Verify’.

Don’t worry if your domain ownership will not be verified right away in Search Console. At first, I got this:


It may take your DNS records time to update and Google to pick them up. In my case, the domain was verified in 2-3 minutes. I just tried clicking ‘Verify’ a few more times and here’s what I finally got:

Now instead of 4 different websites, I see one domain added as a property. In my GSC it looks like this:

Google Search Console is one of the 24 Core SEO Skills that a successful SEO professional should have. Want to learn about the other 23? Get your free checklist 👇👇👇


    Notes and Tips on Domain Properties

    • It is possible to add a domain property to GSC which already has separate versions of the same website added. So these versions will not be united, they will co-exist with your new domain property. You can see it on the screenshot above.
    • If you want to verify domain properties for multiple GSC accounts, you will need to add a separate DNS record for each of these accounts.
    • The verification process requires advanced skills and access to DNS records, which means you’ll need to have some back and forth with the clients to get a domain property verified.
    • User management for domain properties works the same way as for regular websites: you can add users with different permissions. These users will not need to verify the domain properties they were granted access to.
    • If you already have your website versions added to GSC, you will not need to wait for indexation and other info to appear. After verifying your domain property, all data will be immediately available in it.
    • You will see different URL variations in all Google Search Console reports. For example, here’s a Performance report:
    Pro Tips:
    • Keep the old variations of the website in Google Search Console. They might help to debug issues with displaying wrong website variations in Google search. For example, you might notice, that people click to your non-www version of the website while your canonical version has www.
    • If you’re migrating from HTTP to HTTPS, have both variations added separately in addition to the domain property. Again, it will make your life easier when you need to see how Google picks up your redirects.

    Improve your traffic and revenue from SEO within 60 days!

    Your Turn

    Have you already played with domain properties in Google Search Console? Have you faced any problems in verifying them? Share your thoughts in the comments!

    Google Search Console is one of the 24 Core SEO Skills that a successful SEO professional should have. Want to learn about the other 23? Get your free checklist 👇👇👇


      60 thoughts on “How to Verify Domain Property in Google Search Console via DNS

      1. Wow that was strange. I just wrote an really long comment but after I clicked submit my comment didn’t show
        up. Grrrr… well I’m not writing all that over again. Anyways, just
        wanted to say fantastic blog!

      2. Can I use the same DNS verify code (with same email adress) on multiple domains to verify them? Or do I need to create a code for each domain?

      3. Hi Thanks for the great sharing. Do you still need to set the preferred domain name using the domain property method? And
        for URL prefix method, you can zoom into each individual URL in say performance report but with property domain method, all URL variations will be mixed in the report, right?

        1. Hey!

          • No, you don’t need to set the preferred domain name
          • Each URL variation will be available in the Domain Property, you can see a screenshot above.
      4. Thanks, best info I found on how to do this. I was confused about the TTL value as well but learned elsewhere that it is time measured in seconds.

        1. Yeah, it’s ‘time til live’, I also learned it in the process of writing this post 😀

        1. I’d still recommend keeping the individual properties for now. You don’t need to maintain them, they just live on their own 🙂

      5. I am still getting the error,i also made two records and change one’s TTL to 3600 and other to same in my record,But no luck even after hours…

        {Verification method:
        Domain name provider
        Failure reason:
        Could not find your domain. Confirm that you provided the correct domain for your property.
        Please fix your implementation and reverify, or use another verification method.}

      6. Hello! Thank you so much for writing this post, it is one of the most helpful ones that I have found on this new search console feature. I have a question and want to know your thoughts. If I add the DNS verification on my existing search console (http version) of my property, will it eventually automatically update to be a domain property? Or do I have to create a new property and then do DNS verification? Thanks so much!

        1. Hey Naomi 🙂

          I’m happy to hear that the post was useful to you.
          I’d create a separate domain property and verify it 🙂

      7. Hi mam. My site start with https and www. So you tell me which url i add in webmaster tool?.

        With https and www


        Without https or www?. Please help me.

      8. I already have a domain name TXT record from Google listed for GSuite business email. Will an additional domain name TXT record for different purposes (ie. Google Search Console verification) conflict with GSuite? Will it conflict with verifying Google Search Console? Thank you in advance.

      9. Please I can’t find my domain provider on the dashboard of verification of domain via DNS record. Please what do I need to do?

      10. this is what it says. In quote.

        ‘Failure reason:
        We couldn’t find your verification token in your domain’s TXT records.
        We found these DNS TXT records instead:
        v=spf1 +a +mx +ip4: +ip4: -all
        Sometimes DNS changes can take a while to appear. Please wait a few hours, then reopen your property in Search Console. If verification fails again, try adding a different DNS TXT record.’

        Any help ?

        1. Hey Olumide,
          It basically says you have another TXT record added, and this is not the one that GSC gave you in order to verify your domain property.

            1. I have the same issue. There is already a text file starting with v=spf1, can I add the google code behind this record, as mentioned by Estibi? Would this not create any errors? Thanks for your help and for all this useful info!

      11. I had the same issue. I was adding the TXT verification DNS record to their domain that was registered with iPage and couldn’t get it to verify. I finally discovered that the client had Cloudflare setup which essentially takes over the DNS records. When I added the verification record there it finally validated.

      12. Hey why are you adding 5 different URL of same domain name instead of only 2 URL one for https and other domain name. What’s the benefit and disadvantages?

      13. I was looking for this—I have Greengeeks and couldn’t figure it out! Thank you VERY much

      Leave a Reply

      Your email address will not be published. Required fields are marked *