Search Console Ownership Verification Errors and Vercel DNS Setup
What you’ll learn
- The difference between the company where a domain was purchased and the service managing its DNS
- How to find where a TXT record should be added
- How to add the TXT record in Vercel and check whether it is publicly available
- How to preserve existing TXT records when adding a new one
- What to check so the verification value does not appear in an article or shared log
The TXT Record Was Added at the Wrong DNS Provider
Google Search Console is a free tool for checking how a site appears in Google Search. I added the TXT record it provided for ownership verification, but the verification failed.
The domain seller and the service managing DNS were different. DNS manages information such as the destination associated with a domain name. One type of DNS entry is a TXT record, which stores text. Search Console asks a domain owner to publish a Google-issued string as a TXT record to prove control of the domain.
I had registered ailearnplay.com and ailearnplay.online through a Japanese domain registrar, so I initially added the TXT records in the registrar’s dashboard. Both domains had already been delegated to Vercel for DNS management. The registrar’s records therefore did not appear in public DNS and Search Console could not find them.
Search Console verified both domains after I added the same TXT records in Vercel. The experience showed that the record’s destination must be checked before focusing only on its value.
This article covers externally registered domains whose DNS is managed by Vercel. By the end, you will be able to identify the correct DNS control panel and work through the possible causes of failed verification in order. Domain transfers and moving the website itself to Vercel are outside the scope.
The Domain Seller and DNS Manager Have Different Roles
The company where a domain was purchased and the service managing its DNS can be the same or different. Their roles are as follows.
| Name | Role |
|---|---|
| Registrar | Registers and renews the domain |
| Authoritative nameserver | Returns the official DNS information, including the site’s destination and TXT records |
The current authoritative nameservers determine where a TXT record should be added. Once you identify them, you can choose the correct service dashboard.
Even if a domain was purchased from another registrar, Vercel manages its DNS records when its nameservers are:[2]
ns1.vercel-dns.com
ns2.vercel-dns.comIn that configuration, add the TXT record in Vercel. A record entered in the registrar’s separate DNS editor will not appear in public DNS. Records created in Vercel also take effect only when the domain uses Vercel’s nameservers.[4]
The registrar still handles renewal, registration details, and the nameserver assignment. Its dashboard has not become unnecessary; its separate DNS editor is simply not the active place for records in this configuration.
Vercel can host the website while another service manages DNS. The current nameservers, rather than the hosting provider, determine where the TXT record belongs.
Search Console Ownership Verification Procedure
1. Get the Domain Property and Verification TXT Value
Open Google Search Console and select “Add property.” A property is the unit used to manage a site in Search Console.
To cover the entire domain, select “Domain” and enter a value such as example.com. Do not include https:// or a path such as /blog/.[1]
Next, copy the verification TXT value shown by Search Console. It has the following format.
google-site-verification=REDACTEDThis is an invalid example for documentation. Use the exact string shown in your own Search Console session. Google compares that string with the value published in DNS.[3]
Handle the Verification TXT Value Carefully
The value is published in DNS and can be looked up by anyone. It is not an API secret used to operate an external service.
Even so, unnecessary copies can cause mistakes and mix-ups. Paste the value directly from Search Console into the DNS dashboard rather than reproducing it in a public article, screen share, issue, or chat.
2. Identify the Current DNS Manager
Before adding the TXT record, inspect the NS records, which name the servers responsible for the domain’s official DNS answers.
If you are not comfortable with terminal commands, use a web tool such as Google Admin Toolbox. Enter the domain and choose “NS” as the record type. Google also points readers to Google Admin Toolbox for checking public DNS results.[3]
If you have a terminal, use the dig command to look up DNS information. Replace example.com with your own domain.
dig NS example.com +shortUse the returned nameservers to choose where to add the TXT record.
| Result | Where to add the TXT record |
|---|---|
| Vercel nameservers | Vercel DNS dashboard |
| Nameservers from Cloudflare or another service | That service’s DNS dashboard |
| The registrar’s nameservers | The registrar’s DNS dashboard |
At this stage, the NS records are enough. Avoiding a TXT lookup also reduces the chance that the verification value will appear on screen or in a shared log.
Check NS Records over HTTPS
DNS over HTTPS sends a DNS query through an encrypted HTTPS connection. The following example uses curl, a command that retrieves data from a URL, and returns the NS records as JSON, a text format organized as named fields and values.[6]
curl --silent \
--header "accept: application/dns-json" \
"https://cloudflare-dns.com/dns-query?name=example.com&type=NS"3. Add the TXT Record in Vercel
When Vercel is the DNS manager, open “Domains” in the team dashboard, select the domain, and open “Advanced Settings.” If the DNS record form is not visible, select “Enable Vercel DNS.”[4]
A project’s “Settings → Domains” page assigns a domain to a project. It serves a different purpose from the team’s “Domains” page used here.
Add a new TXT record at the root domain, which means the domain itself, such as example.com, without a prefix such as www.
| Field | Value | Note |
|---|---|---|
| Type | TXT | Select the TXT record type |
| Name | Blank or @ | Use the notation for the root domain accepted by the form |
| Value | The string issued by Search Console | Do not add quotation marks or surrounding spaces |
| TTL | Default | Usually does not need to be changed |
TTL is the length of time a DNS answer can be cached. Vercel’s default is 60 seconds, so it can normally remain unchanged.[4]
After saving, confirm that the new TXT record appears in the list.
Add the TXT Record from the Command Line
Vercel also provides vercel dns add for adding DNS records through a CLI, or command-line interface.[5]
Depending on how it is used, the verification value can remain in command history or CI (an automated service that runs checks after code changes) logs. For a one-time ownership check, the dashboard is also an option.
4. Check Public DNS and Retry Search Console
Saving the record in Vercel does not mean Search Console can see it immediately. First, check whether the value is present in the DNS information available on the internet.
In a web-based DNS tool, request the domain’s TXT records. In a terminal, run:
dig TXT example.com +shortThe record is available to that query when the result contains an exact match for the value issued by Search Console.
The output may also contain verification values for other services and TXT records such as SPF, which identifies authorized email senders. Compare the value on your own screen rather than pasting the full result into an issue or chat.
After finding an exact match, return to Search Console and select “Verify.”
Allow Time for DNS Propagation
Google says manually added DNS records can take two or three days to appear. Vercel’s CLI documentation advises allowing up to 24 hours for a new record to propagate.[3][5]
My two domains verified within minutes, but the same timing is not guaranteed. If verification fails immediately, recheck the provider and entered values before waiting and trying again.
Keep the TXT Record After Verification
Leave the TXT record in place after ownership verification succeeds. Search Console periodically checks that the verification record is still present, and Google advises against removing it.[3]
Preserve Existing TXT Records When Adding a New One
A domain can have several TXT records. Examples include a Google Workspace verification record, SPF for email sending, and a verification record belonging to another Search Console owner.
Add the Search Console value as a new record without changing the existing entries. Google allows several people to verify the same property and warns against overwriting another owner’s verification token (the unique text string used to prove ownership).[3]
In particular, a TXT record beginning with v=spf1 controls email sending. It must not be replaced with a Search Console verification value.
In the basic DNS editor provided by the registrar I used, attempting to add another record with the same name and type replaced the existing value in the list. That was my experience with one interface, not a rule shared by every registrar.
After adding the record, check that existing entries remain in the dashboard and compare them with the information available in public DNS.
Checklist for Setup, Sharing, and Post-Verification Handling
When Search Console reports that it cannot find the verification value in the domain’s TXT records, check the destination and entered values before saving the same value again. The following nine items also cover information sharing and what to do after verification succeeds.
- “Domain” selected in Search Console and the correct domain entered
- NS records checked to identify the current DNS manager
- TXT record added in the current DNS manager’s dashboard
- Blank or
@notation accepted by that dashboard used for the root domain - Existing TXT records left unchanged and not overwritten
- Verification value not copied unnecessarily into an article, issue, chat, or screen share
- DNS response compared with the verification value locally without sharing the complete response
- Provider, domain, Name, and Value rechecked before waiting when the value does not match
- Verification TXT record left in place after Search Console succeeds
When the destination is unclear, first check the nameservers with a web-based DNS tool or dig NS. Use Vercel when the result shows Vercel’s nameservers; otherwise continue in the dashboard of the service shown by the result.
Summary: Check the Provider, Entered Values, and Published Record
The failed verification was caused by the location of the TXT record, not its value. When ownership verification does not complete, check the DNS provider identified by the current nameservers, the domain, Name, and Value entered in its dashboard, and whether the record appears in a public DNS response.
The work is complete when the value matches without overwriting existing TXT records, Search Console verifies the domain, and the verification record remains in place without unnecessary copies of the value or lookup output.
References
- Google Search Console Help, Add a website or platform property to Search Console
- Vercel Docs, Working with nameservers, September 16, 2026
- Google Search Console Help, Verify your site ownership
- Vercel Knowledge Base, How can I manage my Vercel DNS records?, July 27, 2026
- Vercel Docs, vercel dns, August 21, 2026
- Cloudflare Docs, Using JSON, May 5, 2026
For the latest releases and updates, check the official website and official documentation.