How to Verify a Site in Google Search Console (Step-by-Step)

Verifying a site in Google Search Console is the first thing you do — and the verification method you pick has implications you'll feel later. Domain property (DNS-based) is the more thorough option but requires DNS access. URL prefix property (file or tag-based) is faster to set up but less comprehensive.

Both are legitimate; the choice depends on your access situation and what you want to track.

The Five Verification Methods

Step-by-Step: DNS Verification (Recommended)

DNS verification creates a Domain property — which covers all subdomains and both HTTP and HTTPS versions under a single property. This is the option Google recommends and the one most agencies should use.

1. Go to search.google.com/search-console and sign in
2. Click "Add property" → select "Domain" (the left option)
3. Enter your root domain (e.g., example.com — no protocol, no www)
4. GSC generates a TXT record string. It looks like: google-site-verification=abc123...xyz789
5. Copy that string
6. Log into your DNS provider (Cloudflare, GoDaddy, Route 53, Namecheap, etc.)
7. Add a new TXT record. Set the host/name to @ (root domain) and the value to the verification string
8. Save the DNS record
9. Wait for DNS propagation (5 minutes to 24 hours, usually under an hour)
10. Return to GSC and click "Verify"

Once verified, leave the TXT record in place permanently. Removing it after verification causes Google to revoke the property's verification on the next periodic check, potentially removing your access.

Step-by-Step: HTML File Upload

Creates a URL prefix property — covers only the specific URL prefix you verify (e.g., only HTTPS, only www subdomain).

1. In GSC, click "Add property" → select "URL prefix" (the right option)
2. Enter the full URL including protocol (e.g., https://example.com/)
3. Under verification methods, select "HTML file"
4. GSC generates an HTML file (named something like google1234567890abcdef.html)
5. Download the file
6. Upload it to your site's root directory so it's accessible at https://example.com/google1234567890abcdef.html
7. Verify the file is publicly accessible by visiting that URL directly
8. Click "Verify" in GSC

Like the DNS record, this file needs to stay on your server permanently. Removing it causes loss of verification.

Step-by-Step: HTML Meta Tag

Also creates a URL prefix property. Useful when you have CMS access but not file system access.

1. Add property → URL prefix → select "HTML tag" method
2. GSC generates a meta tag like: <meta name="google-site-verification" content="abc123xyz" />
3. Copy the tag
4. Add it to the <head> section of your homepage. In WordPress, this can be done via the theme's functions.php, a plugin like Yoast SEO, or the theme customizer. In other CMSes, add via the global header template.
5. Publish / deploy the change
6. Verify the tag is present by viewing the page source on your homepage
7. Click "Verify" in GSC

Step-by-Step: Google Analytics

Fastest method if you already have GA4 installed on the site.

1. Add property → URL prefix
2. Select "Google Analytics" verification method
3. Make sure you're signed into a Google account that has Edit-level permissions on the GA4 property associated with the site
4. Make sure the GA4 property's tracking code is installed on your homepage with theanalytics.js or gtag.js snippet
5. Click "Verify"

This is the easiest path for sites with existing GA4 setup. The verification will break if the GA4 tag is later removed from the homepage or if your account loses permissions on the GA4 property — so it's slightly more fragile than DNS or file-based verification.

Step-by-Step: Google Tag Manager

Similar to GA4 verification but uses an existing GTM container.

1. Add property → URL prefix
2. Select "Google Tag Manager" verification method
3. Make sure you have Manage-level permissions on the GTM container
4. Make sure the GTM container snippet is installed correctly on the homepage, including the <noscript> portion
5. Click "Verify"

Like GA4 verification, this can break if GTM access changes or if the GTM snippet is removed from the site.

Which Method to Pick

• You have DNS access: Use DNS verification. Most comprehensive, most stable, covers all subdomains and protocols.
• You only have FTP/file access: Use HTML file upload. Stable, doesn't depend on third-party tools.
• You have CMS access but no DNS or file access: Use HTML meta tag. Works on any CMS that lets you edit head HTML.
• You already have GA4 or GTM running and want fast setup: Use those methods, but plan to add a more permanent method later.
• You're verifying for a client and the client controls everything: Ask them to use DNS verification on their account, then add you as a Full user via User Management.

Common Verification Failures

• DNS not propagated yet: Wait longer. Cloudflare propagates within minutes; some registrars take up to 24 hours.
• Wrong record type or location: TXT record must be on the root domain (@), not on www or another subdomain.
• HTML file uploaded to the wrong directory: Must be at the root, accessible directly via the verification URL with no redirects.
• Meta tag in the wrong section: Must be in <head>, not in <body>.
• Meta tag modified during deployment: Some CMSes auto-escape or modify the tag. Verify by viewing page source after publishing.

After Verification

Data starts appearing within 24-48 hours for most properties. For brand new sites with no existing search presence, it may take longer — Google has to start showing your site in results before there's any data to report.

The first thing to do after verification: submit a sitemap. We have a separate post on sitemap submission and troubleshooting. After that, set up the BigQuery bulk export immediately — covered here — so you start accumulating historical data from day one rather than losing the first 16 months of your site's keyword history.

Verification is a one-time setup task, but the method you choose affects how comprehensive your tracking is and how stable your access remains over time. DNS-based domain property is the right default for most situations; the URL prefix methods are appropriate when DNS access isn't available.