To verify a Domain property in Google Search Console, add the DNS verification record Google supplies at your domain’s active DNS host. For a typical TXT verification, publish the exact token at the root of the domain and then ask Google to verify it. This proves control of the domain; it does not automatically index your website or improve its rankings.
Before you begin
- A Google account controlled by the business owner.
- Access to the domain’s authoritative DNS records.
- The exact verification record from Search Console, not a tutorial’s sample token.
- The address of your live website and its sitemap, if available.
1. Choose Domain or URL-prefix
A Domain property covers the domain across protocols and subdomains. For example, a Domain property for example.co.uk includes its www and shop subdomains. Enter the domain without https://, a path or a trailing page name. This is a useful starting point when you want one overview of your business domain.
A URL-prefix property covers the specified URL prefix instead. It can be useful for a particular version or section of a website and offers additional verification methods. Choose the scope you actually control. A hosting company’s shared platform address is not the same property as your own custom domain.
2. Publish Google’s exact verification token
Start adding the property in Search Console and select its DNS verification instructions. Copy the TXT value exactly. In NameUK, open the domain and its DNS records, then add a TXT record at the root using the form’s root-host convention. Paste the verification token in the value field; do not put it in the hostname field.
Add a separate verification TXT entry rather than replacing your email’s SPF text. Multiple unrelated TXT records can exist at the root. Save the record, return to Google and select Verify. If you use external nameservers, publish the token with that DNS host instead of in an inactive NameUK zone.
Sources: Google: verify site ownership ↗
3. Troubleshoot a verification failure methodically
Keep the successful verification record published. Google can recheck ownership later. If a designer or agency needs access, use Search Console’s user permissions instead of sharing your Google password. Keep the business owner’s access in place when a contractor finishes work.
| Check | What to look for |
|---|---|
| Correct domain | No spelling error or accidental subdomain in the property. |
| Active DNS host | Nameservers point to the service where you added the TXT record. |
| Correct field | Root hostname in Host; the entire Google token in Value. |
| Saved record | The public TXT answer contains the token, not only the dashboard form. |
| Time to update | Allow cached DNS answers to expire before another check. |
Sources: Google: verify site ownership ↗
4. Submit the sitemap for the live website
Once verified, find the sitemap produced by your website platform. It is commonly available at /sitemap.xml, but use the actual address supplied by your host. In Search Console’s Sitemaps report, submit that address and check whether Google can fetch it.
A sitemap helps discovery; submission does not guarantee that every page will be indexed. Include the canonical public pages you want found, rather than account screens, basket pages or internal search results. If the sitemap is rejected, check its public HTTP response and contents before repeatedly submitting the same address.
Sources: Google: build and submit a sitemap ↗
5. Inspect important pages and read the reports
Use URL Inspection for the homepage and an important service or product page. Check the reported canonical, crawling and indexing information. A new site may have little performance data initially. Record the publication date and inspect what Google reports before deciding that something is wrong.
As impressions appear, compare relevant queries and landing pages. A local plumber, a ceramic shop and a national software business need different search content. Write pages that answer their customers’ specific questions, show the service clearly and give visitors a useful next step. Search Console is a measurement and diagnostic tool, not a substitute for that work.
Does verification make a .co.uk domain rank higher?
Verification proves access; it is not a ranking payment or a priority queue. Neither registering a domain nor publishing a TXT token guarantees traffic, orders or a particular search position. Keep useful pages publicly accessible, use accurate titles and descriptions, and make important pages easy to reach through ordinary links.
Track practical business outcomes alongside search visibility: enquiries, qualified calls and completed purchases. If a page earns impressions but few clicks, check whether its title matches the page and the question being asked. If visitors arrive but cannot find prices or contact details, improve the page itself.
You can keep domain costs predictable while building the site’s content. Compare NameUK’s current low-cost UK registration and annual renewal below. Search Console itself does not require buying an extra SEO package from your domain registrar.
Provider instructions checked on 15 October 2026. Use the current values shown in your own provider account when making changes.
Further readingGoogle: add a Search Console property ↗Google: verify site ownership ↗Google: build and submit a sitemap ↗Google: get started with Search Console ↗Extension rules and provider processes can change. Check the current registrar instructions before a registration, transfer or renewal.
Low-cost registration. Affordable UK renewals.
Register .co.uk for £9.99 for one year, with annual renewal currently £9.99. Or choose a new three-year .co.uk registration for £25.99. Check the selected name and term before payment. Future renewal prices can change.