Google Search Console setup: Domain vs. URL-prefix properties
· PION
Choose a Domain or URL-prefix property, find an ownership verification method that works for your site, and understand DNS verification delays and TTL.
When you click the Add property button, two input fields appear side by side: Domain and URL prefix. The screen doesn't tell you which field to enter your address into, and your choice determines which ownership verification options appear next. We receive many inquiries about Google Search Console registration getting stuck on this screen.
The deciding factor is the ownership verification method. The domain property supports only DNS record verification, while the URL prefix property lets you choose from HTML file, meta tag, Analytics, and Tag Manager. That's why choosing a type comes down to whether you have login access to your domain management console. This article covers property types and ownership verification. The final section links to the steps for indexing and search visibility.
1. How to choose between the two property types
If you can log in to your domain management console, choose the domain property; if not, choose the URL prefix property. When PION audits brand sites, we advise creating a domain property first for sites that have multiple subdomains. Your properties appear in the selector at the top left of Search Console. Choose Add property from that menu to create one.
| Item | Domain property | URL prefix property |
|---|---|---|
| Help description (original) | "A domain-level property that includes all subdomains (m, www, etc.) and multiple protocols (http, https, ftp)" | "Includes only URLs with the specified prefix, including the protocol (http/https)" |
| Verification | "Supports only DNS record verification" | "Multiple methods available" |
| Input format | Like example.com, without protocol or path | Like https://example.com/, down to the trailing slash |
| Data coverage | "Includes all data about the property's subdomains, protocols, and subpaths" | Only addresses starting with the specified prefix |
The definitions of the two types are in the Add a website or platform property to Search Console help article. In Korean, the screen and help text spell it jeopdusa, while searches also surface it under the synonym jeopdueo, both meaning URL prefix.
To track performance separately for per-country or per-service folders, a single domain property won't split them out, so the help article advises creating additional URL prefix properties for the subsections.
2. Verification methods for each hosting setup
Your hosting setup narrows the five methods to one or two. Verify your site ownership help article attaches the same restriction to four of the tag- and file-based methods. It states, "HTML file upload can be used for URL prefix properties but not for domain properties," and the same sentence is attached to the HTML tag, Analytics, and Tag Manager methods.
| Operating environment | Methods to rule out | Methods that remain |
|---|---|---|
| Direct deployment to your own server | None | All five (HTML file upload preferred) |
| WordPress-type CMS | None | Plugin (officially supported Site Kit) |
| Hosted website builder | HTML file upload | The verification code field provided by the builder, meta tag, Analytics, Tag Manager |
| Multiple subdomains | The four tag- and file-based methods | DNS record |
If you can't find the file upload field on a site that uses a hosted builder, it's not because something is misconfigured. The help article states, "If you use a website hosting platform such as WordPress, Wix, or SquareSpace, you may not be able to use some of the methods described below," and advises checking the verification method in your platform's help documentation first.
3. DNS verification delays and TTL
DNS changes do not propagate as soon as you save them. They must wait for cached records to expire. When PION sets up ownership verification, we use the record's TTL to decide when to retry. Cloudflare's Time to Live (TTL) document (updated April 16, 2026) states, "A TTL of Auto is set to 300 seconds (five minutes)", and describes the manually specifiable range as "For DNS only records, you can choose a TTL between 30 seconds (Enterprise) or 60 seconds (non-Enterprise) and 1 day". If a record has a one-day TTL, the retry interval is that long too.
| Step | What to do | Value to note down |
|---|---|---|
| 1 | From the table above, pick one verification method that remains for your operating environment | The method you chose, the methods you ruled out and why |
| 2 | Enter the TXT string issued by Search Console into the value field of your domain management console. Leave the name field empty | Record type, the value you entered |
| 3 | Look up the TTL value of the record you saved. If you leave the default as is, it's usually Auto (300 seconds) | TTL value |
| 4 | After waiting the length of the TTL value, click the Verify button just once more | Retry time, result message |
The input format for step 2 is described in the help article as, "For a TXT record, leave the name/host field empty and put the TXT string in the value field of the DNS record". You can tell whether the record is actually being served by looking up the domain's TXT in the Admin Toolbox that the help article points to. Even after verification is complete, you should leave the record in place. The help article states, "To keep your verified status, do not delete the DNS record you received from your provider even after verification is complete".
4. What to do for each verification error
Read the exact error message to determine whether propagation is still pending, the value is wrong, or the verification resource cannot be reached. Only the first category is resolved by repeatedly clicking the same button.
| Failure message | Meaning | Action |
|---|---|---|
| Verification DNS TXT record could not be found | The record isn't being served yet | As the help article advises, "wait a day or two and try again" |
| Verification record does not match | The value differs from the string you were issued | Leave the name field empty and put only the TXT string in the value field |
| Meta tag not found or in the wrong location | It's outside the head section or on a different page | Check the tag's position in the rendered source of the logged-out home page |
| Verification file redirected to a disallowed location | It goes to a different domain | Point the redirect target to the same domain |
| Analytics code could not be found | The snippet isn't on the logged-out home page | Check whether the snippet is in the head section and whether it's the latest version |
For the case where a verification file is redirected, the help article states, "If the verification file is redirected to a different domain, it won't be followed, but redirects within the same domain are followed". Even ownership that was once verified can be lost if you swap out the site template, so the help article recommends, "It's a good idea to add two or more verification methods in case one of your existing verification methods fails".
5. What appears after registration and what to do next
Even after ownership verification is complete, the screen stays empty for several days. The help article states, "Data about a property is collected as soon as someone adds the data to Search Console, even before ownership verification takes place", and adds that it takes a few days for data to accumulate. Google Search Central's Get started with Search Console (updated December 18, 2025) also advises, regarding operations after registration, "You don't need to log in to the tool every day".
The sequence for looking up a page's status in the Google Search Console indexing menu and picking the action that fits the status is laid out in a status-by-status table in Google Search Registration and Verifying Site Registration: What to Check When You're Registered but Not Showing Up. For the ChatGPT and Gemini answers that Search Console doesn't track, 5 Checklist Items for Diagnosing Brand AI Visibility covers what to check.
For the work and contract terms covering property setup through AI answer visibility, see the GEO Agency Service Overview. You can compare where a registered site stands on both the Google crawler and AI search bots using the eight items in the 5-Minute GEO Readiness Assessment.
Frequently asked questions
When registering with Google Search Console, should I choose the domain property or the URL prefix property?
If you can log in to your domain management console, choose the domain property; if not, choose the URL prefix property. The domain property holds subdomains and both http and https in a single property, but in exchange it supports only DNS record verification, while the URL prefix property offers a wider set of options including HTML file, meta tag, Analytics, and Tag Manager. When PION audits brand sites, we advise creating a domain property first for sites that have multiple subdomains.
Of the five Google Search Console verification methods, how do I pick the one that works for my site?
Choose based on the permissions you have. If you have permission to upload a file to the root, use HTML file upload; if you can edit the head section of your home page, use the meta tag; if you can log in to your domain management console, use the DNS record. Google's help article notes that some methods are blocked on sites using hosting platforms, and it names Site Kit as the one officially supported WordPress plugin.
I followed the Google Search Console setup steps, but ownership verification is failing.
Take the failure message verbatim and sort out the cause. If the TXT record can't be found, that's a propagation wait, and the guidance is to try again after a day or two; if the record doesn't match, check whether you left the name field empty. The meta tag method requires the tag to be in the head section of the logged-out home page, and if the verification file is redirected to a different domain, Google won't follow it.
In the process for registering a website with Google Search Console, do I have to register the www and https addresses separately?
With a single domain property, you don't need to register them separately. Google's help article explains that if you specify www.example.com as the property URL, the property is created as example.com and includes the data for both addresses. If you chose a URL prefix property, you have to add a separate property for each protocol and each subdomain.
Once I finish registering, when does data start appearing in Search Console?
It takes a few days. Google's help article explains that property data collection begins the moment you add the property, and that it takes a few days for data to accumulate. A property saved before ownership verification is also subject to collection, so there's no need to redo registration while the screen is empty.