Google Search Console is a free tool that shows how your site appears in Google Search: which queries you rank for, how often people click, which pages are not indexed and why. To see that data you must prove the site is yours. Of the available verification methods, DNS verification of the whole domain is the strongest and gives the most complete picture.
Domain property vs URL-prefix property
A URL-prefix property covers one exact address, such as https://www.example.uz/. The http:// version, the non-www version and shop.example.uz are separate properties. It can be verified with an HTML file, a meta tag, Google Analytics or Google Tag Manager. A Domain property covers everything at once: HTTP and HTTPS, www and non-www, all subdomains, and its data survives protocol changes. In exchange, it can only be verified through DNS, because only whoever controls the DNS zone controls the whole domain.
Getting and adding the TXT record
In Search Console, add a new property, choose Domain and enter the name without protocol or www, for example example.uz. Google gives you a TXT value starting with google-site-verification=. If the domain is registered through sayt.uz and uses our nameservers, create the TXT record in the domain's DNS section of the cabinet; if the nameservers point elsewhere, such as Cloudflare, add it there. The name is @ or left empty, depending on the panel.
| Type | Name | Value | TTL |
|---|---|---|---|
| TXT | @ | google-site-verification=Xy12Ab...Qw | 3600 or default |
Keep existing SPF or Google Workspace records and add this one separately. Several google-site-verification records on one domain are fine, for example when two colleagues verified independently.
Clicking Verify and troubleshooting
Return to Search Console and click Verify. If it fails, the record has usually not propagated yet. Check it yourself:
dig +short TXT example.uz
nslookup -type=TXT example.uz 8.8.8.8If the string is there, retry in a few minutes. If not, check that you used the right panel, that the name field does not duplicate the domain (example.uz.example.uz), and that no stray spaces or quotes were added. Propagation sometimes takes a few hours, especially when the zone's old records had a long TTL, so a later retry is often all that is needed.
Keep the record afterwards
Do not delete the TXT record after verification. Google rechecks ownership periodically and access is lost if the record disappears. When moving DNS to another provider or changing nameservers, copy every TXT record into the new zone, or one day you may find yourself locked out of your own Search Console data.
Example: a hotel website in Bukhara
A family hotel in Bukhara has its main page at https://example.uz, bookings on book.example.uz, and an old blog still served via www. With a URL-prefix property they never saw booking-page statistics. The administrator added a Domain property, put the TXT record into the zone, and verification passed within an hour. Queries, indexing errors and mobile usability for every subdomain now appear in one report, while the old URL-prefix property was kept for section-level analysis.
First steps after verification
Submit your sitemap, such as https://example.uz/sitemap.xml, under Sitemaps, and check key pages with URL Inspection. Give teammates their own access under Users and permissions instead of sharing your password. Reports take time to fill, so empty charts in the first days are normal. Yandex Webmaster also supports TXT verification, and Bing Webmaster Tools can import verified Search Console properties directly.