# How to verify a site in Google Search Console, and which property to pick Verify your site in Search Console the right way, first time. Pick the right property, use the matching verification method, avoid the traps, and check the three reports that matter on day one. Updated 2026-09-14 · Source: https://porteur.ai/guides/how-to-verify-google-search-console ## Pick the right property type Pick a Domain property by default. It covers every subdomain and both http and https in one place. Pick a URL-prefix property when you only own or manage one exact prefix. For example, https://docs.yourproduct.com/ or https://www.yourproduct.com/blog/. | Property | Scope it covers | Best when | Verification method | | --- | --- | --- | --- | | Domain property | All subdomains and both protocols for your domain | You run the whole domain and want every variant in one view | DNS TXT record | | URL-prefix property | One exact prefix like https://www.example.com/ | You only control a folder, a subdomain or need a quick prefix-only setup | HTML file, meta tag, GA tag or GTM container | > Rule: use a Domain property unless there is a clear reason not to. ## Verification methods and when to use which - DNS TXT record: required for a Domain property. Also works for a URL-prefix if you prefer DNS changes. Use this when you control DNS for the domain. - HTML file upload: fast for a URL-prefix on a site where you can add a file to the web root, for example /google000000000000000.html. - HTML meta tag: fast for a URL-prefix on a site where you can edit the of the home page, for example /index.html or the template. - Google Analytics tag: works for a URL-prefix that already has the GA tag live. Fine if you keep GA installed. - Google Tag Manager container snippet: works for a URL-prefix that already has GTM live. Fine if you keep GTM installed. Verification can lapse if the token is removed. Keep the method you used in place. Add extra verified owners if you need redundancy. ## Verify a Domain property with a DNS TXT record You need access to your DNS. That is your registrar or DNS host. The record goes on the root of your domain, not on a subdomain, unless told so in the step. 1. **Create the Domain property** Open Search Console, Add property, pick Domain, enter your domain like yourproduct.com, then copy the TXT record value Google shows. 2. **Add the TXT record in DNS** In your DNS manager, add a TXT record on the root. The host is @ or blank, depending on the provider. Paste the exact token from Search Console. 3. **Save and wait a little** DNS can take a short while to be seen. Click Verify in Search Console. If it fails, wait and try again. 4. **Keep the record** Do not delete the TXT record. Search Console checks ownership and can mark verification as lapsed if the token goes missing. A successful Domain property covers https://yourproduct.com/, https://www.yourproduct.com/, and any subdomain like https://docs.yourproduct.com/. That avoids a split view later. > Warning: a CAA, A or CNAME change is not needed. Only add the TXT record Google gives you. ## Verify a URL-prefix with an HTML file Use this when you can upload files to the web root for that prefix. You only verify the exact prefix. For example, https://www.yourproduct.com/ is a different property from https://yourproduct.com/. 1. **Create the URL-prefix property** Add property, choose URL-prefix, enter the full prefix including https and www if present. 2. **Download the HTML verification file** Search Console gives a file like google000000000000000.html. Do not rename it or change its contents. 3. **Upload to the web root of the prefix** Place it at https://www.yourproduct.com/google000000000000000.html. Check you can open that exact URL in a browser. 4. **Click Verify** If your deploy process deletes unknown files, add the file to your repo so it persists across redeploys. A fixed page stays verified across releases. For example, redeploying your Next.js site should not delete /google000000000000000.html. ## Verify a URL-prefix with a meta tag Use this when you can edit the of the home page for that prefix. It is fast and works on static and dynamic sites. It only verifies that exact prefix. 1. **Create the URL-prefix property** Add property, choose URL-prefix, enter the full prefix exactly as it resolves. 2. **Copy the meta tag** Search Console shows a tag. Copy it in full. 3. **Paste into the home page head** Add the tag inside on the URL-prefix home page template. Do not place it in the body. 4. **Deploy and verify** Publish, load the home page, view source and confirm the tag is present, then click Verify in Search Console. > Warning: SPA frameworks that render head tags only client side can cause verification to fail. Ensure the tag is in the initial HTML. ## Verify with Google Analytics or Google Tag Manager Use this only if the tag or container is already live on the exact prefix and you plan to keep it. Removing GA or GTM later can lapse verification. - Google Analytics: pick the GA option in Search Console for the URL-prefix. The GA tag must be present and working on the home page of that prefix. - Google Tag Manager: pick the GTM option. The GTM container snippet must be present and working on the home page of that prefix. If you later migrate analytics or remove a tag, add a second verification method first. For example, keep the meta tag alongside GA-based verification. ## Avoid the common pitfalls - Verifying the wrong variant: https and http, www and non-www are different for a URL-prefix. A Domain property avoids this split. - Forgetting subdomains: docs.yourproduct.com and blog.yourproduct.com need their own URL-prefix properties unless you use a Domain property. - Losing the token on deploy: a site rebuild that overwrites the head or the root can remove the meta tag or HTML file. Keep it in source control. - Tag-based verification broken: removing GA or GTM, or a consent banner blocking tags on first paint, can break verification. - Not enough access: you cannot add DNS if you do not control the zone. Ask the domain owner to add the TXT record or add you as an owner in Search Console. - Checking the wrong property: you verified https://www.yourproduct.com/ but your site resolves to https://yourproduct.com/. Add the right one or use a Domain property. > Rule: once verified, add at least one more verified owner and one more verification method as backup. ## What to check first after verification Do three checks on day one. Sitemaps, Performance and Core Web Vitals. Each one confirms a basic that saves you weeks later. 1. **Sitemaps report** Submit your sitemap index URL, for example https://www.yourproduct.com/sitemap.xml. The report shows Status, the date last read and URLs discovered. Google reads lastmod when it is consistently accurate. It ignores changefreq and priority. A sitemap may hold up to 50,000 URLs or 50 MB uncompressed. It can only list URLs on its own host or an approved cross host. Fix any Has errors or Couldn't fetch. 2. **Performance report** Confirm data starts to fill across 16 months once Google records visits. Use filters by query, page, country, device, appearance and date. Average position is the mean of the highest position across impressions. Early on, check branded queries work as expected. For example, "yourproduct" should map to your home page. 3. **Core Web Vitals report** Check mobile and desktop groups. URLs sit in Poor, Needs improvement or Good based on field data from Chrome UX Report. New or low traffic pages can show no data. If your key template is Poor, plan fixes before you scale content. If you verified a root-level property, open Settings, Crawl stats. Check host status, total crawl requests, total download size and average response time over 90 days. Spikes in 5xx or timeouts signal hosting issues to fix now. ## How to structure properties for a small product site Keep it simple. One Domain property for your main domain. Add URL-prefix properties only for areas that need separate monitoring, like a docs subdomain or a country site. - yourproduct.com as a Domain property: your default workspace. - https://docs.yourproduct.com/ as a URL-prefix if a separate team runs it. - https://www.yourproduct.co.uk/ as a URL-prefix if you have a country domain with different content. Grant access by role, not by token. Add extra owners and full users in Search Console for the people who ship each area. That is safer than sharing DNS access. ## Troubleshooting a failed verification - DNS TXT record not found: confirm the record is on the root, not on www. Use your DNS host’s record viewer. Try again after a short wait. - HTML file 404: confirm the file is at the exact URL Search Console expects. Check your build does not strip unknown files. - Meta tag missing: view source on the home page and check the tag is inside . Server side render the tag, not only client side. - GA or GTM not detected: load the home page and confirm the tag or container snippet fires. Fix consent mode or blockers if they prevent the tag on first load. - Wrong prefix: if your site redirects to a different prefix, verify that final destination or use a Domain property. If all else fails, switch method. For example, use the meta tag for a URL-prefix instead of the HTML file, or use DNS for a Domain property. ## Questions ### How do I pick between a Domain property and a URL-prefix? Choose a Domain property if you control the domain and want one view for all subdomains and both protocols. Choose a URL-prefix when you only manage a single prefix or need to verify a subfolder or subdomain without DNS access. ### How long does DNS verification take? It can work quickly once the record is live. If Verify fails at first, wait a little and try again. You only add one TXT record, exactly as Search Console shows it. ### Can I remove the verification method after I am verified? Keep it. Verification can lapse if the token is removed. If you need to change methods, add the new one, verify, then remove the old one. Keep at least one backup method in place. ### Do I need to verify both www and non-www? Not if you use a Domain property. It covers both. If you use URL-prefix properties, each variant is separate, for example https://yourproduct.com/ and https://www.yourproduct.com/. ### What should I check first in Search Console? Submit your sitemap in the Sitemaps report, skim the Performance report for branded queries and obvious mismatches, and review the Core Web Vitals report. If you have a root-level property, check Crawl stats for errors or timeouts. ### Does Bing need a separate verification? Yes. Use Bing Webmaster Tools. You can import from Search Console with one click or verify by XML file, meta tag, DNS CNAME or other methods. It covers Bing, Microsoft Copilot, Yahoo Search and part of DuckDuckGo. ## Read next - [How to use Google Search Console in ten minutes a week](https://porteur.ai/guides/how-to-use-google-search-console): A quick weekly routine: set four filters, compare 28 days, check pages then queries, and fix three findings, without getting lost in noise. - [The Sitemaps report: what Success, Has errors and Couldn’t fetch mean](https://porteur.ai/guides/search-console-sitemaps-report): How to submit your sitemap URL, read Success, Has errors and Couldn’t fetch, and fix invalid XML, 404s, cross‑host URLs and missing child sitemaps. - [The Search Console performance report, column by column](https://porteur.ai/guides/search-console-performance-report): Every column in the Google Search Console performance report explained with the traps that trip small sites, and how to act on each. - [The Core Web Vitals report in Search Console, page group by page group](https://porteur.ai/guides/search-console-core-web-vitals-report): Understand where the Core Web Vitals data comes from, how page groups work, what to fix by template, and how to move groups to Good. - [How to use the URL Inspection tool in Search Console](https://porteur.ai/guides/url-inspection-tool): Read each panel, run Test live URL, and know when to request indexing. Fix new pages, dropped pages, and canonicals Google ignores. - [Bing Webmaster Tools for a small site: what it gives that Google does not](https://porteur.ai/guides/bing-webmaster-tools): Set up Bing Webmaster Tools in minutes. Import from Search Console, reach Copilot and Yahoo, use Backlinks, Keyword Research, Site Scan and IndexNow. - [The Removals tool: how to take a page out of Google, properly](https://porteur.ai/guides/search-console-removals-tool): Use the Removals tool without breaking your site: hide results for about six months, clear cached snippets, and make removals permanent the right way. Not sure which property to add or what to check first, paste your URL into the free check and get three findings on your site and the searches around it in about thirty seconds. Free check: https://porteur.ai/