Opened 11 months ago

Closed 11 months ago

Last modified 11 months ago

#32782 closed task (fixed)

Add google search DNS verification TXT record for

Reported by: hellais Owned by: anarcat
Priority: Medium Milestone:
Component: Internal Services/Tor Sysadmin Team Version:
Severity: Normal Keywords:
Cc: anarcat Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


Following we would like to start setting up 301 redirects from to, so that we can improve our SEO a bit (see:

In order to get the google search data for we need to prove ownership of the domain name via DNS.

This requires adding the following TXT record for the domain:


Child Tickets

Change History (7)

comment:1 Changed 11 months ago by anarcat

i'm slightly confused... you want to setup a 301 redirect, but first you want google to start searching it? why do you need to do that step? can't you just do the redirect first and then google won't have to search it?

comment:2 Changed 11 months ago by hellais

Google is already searching that site, but it's not telling us the metrics of how it has been indexed. By proving we own the domain, they will give us all the metrics they already have for the so we are able to evaluate the SEO impact of setting up the redirect.

comment:3 Changed 11 months ago by anarcat

Owner: changed from tpa to anarcat
Status: newaccepted

that makes sense, of course... will do this right away, thanks for the update!

comment:4 Changed 11 months ago by anarcat

Status: acceptedneeds_information

ah. hum. well there's already a problem here: having other data on a CNAME record is not allowed (see also RFC1912 section 2.4).

right now we have this:

ooni			IN	CNAME

so even if i can add such a record, it's not actually legal and might break stuff...

are you sure this is actually what google is asking you?

i could turn the CNAME into a A record (pointing to what?) and be able to add that TXT record though...

comment:5 Changed 11 months ago by hellais

Ah ok I see.

Then let's go for the A record and TXT record option.

You should setup the A record to point to one of the netlify IP addresses, such as:


BTW we have already started 301 redirecting visits to to, but this is still useful so we can get a better picture of how this is going to affect our search engine rankings.

comment:6 Changed 11 months ago by anarcat

Resolution: fixed
Status: needs_informationclosed


commit 400d6eef1017687fc441737f199a4372631b1058 (HEAD -> master, origin/master, origin/HEAD)
Author: Antoine Beaupré <>
Date:   Wed Dec 18 13:49:26 2019 -0500

    add google verification token for ooni SEO (Closes: #32782)

diff --git a/ b/
index b032210..9416db1 100644
--- a/
+++ b/
@@ -101,7 +101,8 @@         IN      CNAME   listera
 metrics                        IN      CNAME   meronense
 munin                  IN      CNAME   schmitzi
 nagios                 IN      CNAME   hetzner-hel1-01
-ooni                   IN      CNAME
+ooni                   IN      A
+ooni                   IN      TXT     google-site-verification=8q628kou8EXLTU-ggciHl7E4tYvwLqiapH2kdJoO3vk
 get.ooni               IN      CNAME
 measurements.ooni      IN      CNAME
 explorer.ooni          IN      CNAME

i assume this is temporary and the TXT record can eventually be removed? if so, please reopen when it's time to change back to a CNAME otherwise i'm worried the domain will start failing once/if netlify move stuff around.

comment:7 Changed 11 months ago by hellais

Thanks for this!

According to the docs on google, we should keep the TXT record forever in order to stay validated.

That said, I think we can probably revert it to just being a CNAME once we have learned what we need to learn from the google search console and finalised the migration to

I will be sure to update this issue when that is the case.

Thanks a bunch!

Note: See TracTickets for help on using tickets.