A Google Search Console Domain property collects search information
across the domain’s protocols and subdomains. Verification normally
requires adding a TXT record to DNS.
This is an additive change. Existing website, email, and
authentication records should remain in place.
Common versions of the question include ‘Google won’t verify my
website,’ ‘where do I paste the Google TXT code?’, and ‘why is Search
Console empty after verification?’ Verification proves control of the
domain; it does not instantly create performance history or guarantee
indexing.
Domain property
versus URL-prefix property
A Domain property can include variations such as http,
https, www, and other subdomains under the
verified domain. A URL-prefix property covers only the exact prefix
entered.
Domain properties are useful when you want broad coverage, but they
require DNS verification. URL-prefix properties offer additional
verification methods and can still be appropriate for a narrowly defined
site.
Before you begin
Confirm that you are signed into the intended Google account and that
you have access to the authoritative DNS provider. The registrar and DNS
provider may be different companies.
Document the existing DNS zone before editing it. A verification
request should not require removing MX, A, CNAME, or unrelated TXT
records.
Add the property
In Search Console, choose to add a property and select
Domain. Enter the domain itself without a protocol or
path. Google will provide a TXT value beginning with a site-verification
label.
Copy the entire value exactly. Do not publish screenshots containing
an active verification token.
Add the TXT record
In the DNS manager:
- Select TXT as the record type.
- Use the root-domain name format expected by the provider, often
@or a blank field. - Paste the complete Google verification value into the content or
value field. - Leave TTL at the provider’s default unless there is a documented
reason to change it. - Save the new record without modifying existing entries.
If the provider has a guided “Google verification” tool, confirm that
it creates an ordinary TXT record and does not replace unrelated DNS
configuration.
Verify ownership
Return to Search Console and select Verify. DNS visibility may be
quick, but caching and provider behavior can delay it. If verification
fails immediately, first recheck the record name and full value. Do not
keep creating duplicate records during the delay.
Once ownership is verified, leave the TXT record in place. Removing
it may cause ownership verification to be lost later.
Confirm the correct property
Use the property selector and verify that the selected entry is the
Domain property, typically displayed without https://. A
URL-prefix property may appear separately with the full URL.
This distinction matters when connecting an SEO plugin. Select the
property that corresponds to the intended coverage and verified
account.
Submit the sitemap
Find the XML sitemap URL produced by WordPress or the SEO plugin.
Common structures include a sitemap index at
/sitemap_index.xml or WordPress’s native
/wp-sitemap.xml, but you should open the actual URL before
submitting it.
In Search Console, use the Sitemaps section for the selected property
and submit the verified sitemap location. A successful submission
confirms that Google can retrieve it; it does not guarantee that every
URL will be indexed.
What to expect afterward
New properties frequently show little or no performance data at
first. Search Console needs time to process information. That delay does
not mean verification failed.
Review indexing reports, sitemap status, manual actions, security
issues, and search performance over time. Avoid making sitewide changes
based on a single day of limited data.
Common mistakes
- Adding the record at the registrar when DNS is hosted elsewhere
- Entering
https://domain.comas a Domain property - Pasting only part of the TXT value
- Deleting existing TXT or MX records
- Removing the verification record after success
- Connecting an SEO plugin to the wrong property
- Treating sitemap submission as guaranteed indexing
The entire procedure should add one verification record and leave the
rest of the domain infrastructure untouched.
Protect access after
verification
Review Search Console users and permissions periodically. Grant the
least access needed, remove obsolete users deliberately, and keep the
domain verification record. Ownership of Search Console data can reveal
valuable business information even though it does not provide direct
WordPress access.
If several websites are available in the same account, verify the
selected property before submitting a sitemap, inspecting a URL, or
connecting a plugin.
Frequently asked questions
Why does the new
property show no search data?
Verification proves control; it does not create historical traffic.
Processing can take time, and a new or low-traffic site may initially
show little information.
Should I submit both sitemap
URLs?
Submit the sitemap system the live site actually uses. Two
overlapping sitemap systems can create needless confusion. Open the
sitemap index and confirm it returns current canonical URLs.
Does submitting a URL
guarantee indexing?
No. Google decides whether and when to index a URL. Submission aids
discovery and diagnosis but does not override quality, duplication,
crawling, or indexing decisions.
Related guides
- DNS
Changes Without Breaking Your Website or Email - Rank Math Search Console and Analytics Setup