For most websites, we recommend a Domain property in Google Search Console. It gives you a broader view of search performance across subdomains, protocols, and paths. A URL-prefix property is useful when you need to focus on one version or section of a site.
The choice affects which URLs appear in your reports and how you verify ownership. Let's look at the differences so you can set up the right view without missing important data.
Google Search Console Properties at a Glance
A property is the website or portion of a website you add to Google Search Console. Its boundaries determine which URLs you can monitor in that property.
Think of a Domain property as a view of the whole building. A URL-prefix property lets you focus on one part of it.
Here's how the two options compare for a site using example.com.
| Feature | Domain property | URL-prefix property |
|---|---|---|
| Example entry | example.com | https://www.example.com/ |
| Protocols covered | All protocols | Only the specified protocol |
| Subdomains covered | The entered domain and its subdomains | Only the specified host |
| Paths covered | All paths under covered hosts | Only paths beginning with the specified prefix |
| Verification | Usually requires a DNS record | Offers multiple verification methods |
| Best fit | A broad view of a site | A specific site version or section |
The biggest distinction is coverage. Choosing a property doesn't change your website or give you a ranking boost. It changes the scope of the information you can access in Search Console.
Google generally recommends a Domain property when appropriate and when you can complete Domain-level verification. For many site owners, that's the simplest starting point.
What a Domain Property Includes
A Domain property brings the versions of a domain together under one property. Enter the domain without a protocol or path, such as example.com, and Search Console covers URLs beneath that domain.
Subdomains and Site Sections
A Domain property for example.com includes the root domain and subdomains such as www.example.com, blog.example.com, and shop.example.com. It also includes paths under those hosts, such as /services/ and /blog/.
This is helpful when different parts of your business live on different subdomains. You can start with a broader picture instead of switching between separate properties to see each area.
You can also create a Domain property for a subdomain. A property for blog.example.com covers that subdomain and its descendants, but it doesn't include the parent domain or sibling hosts such as shop.example.com.
HTTP and HTTPS Versions
The same Domain property covers both HTTP and HTTPS. For example, it includes http://example.com/ and https://example.com/, along with covered subdomains.
That broader coverage is useful during a move to HTTPS because old HTTP URLs can still appear in your data. It doesn't mean both versions should remain accessible. For a site using HTTPS, we recommend directing old HTTP URLs to the appropriate secure pages and using HTTPS URLs consistently in internal links, canonicals, and sitemaps.
What a URL-Prefix Property Includes
A URL-prefix property covers URLs that begin with the exact prefix you enter. The protocol, host, and any path in that prefix define the boundaries.
Protocol and Host Must Match
A property for https://example.com/ includes HTTPS URLs on example.com. It doesn't include http://example.com/, https://www.example.com/, or https://blog.example.com/.
That difference can surprise beginners. Your browser may redirect one version to another, but the addresses still have different prefixes in Search Console.
If you want separate reports for the HTTP and HTTPS versions, or for the root domain and a subdomain, you can add separate URL-prefix properties. A Domain property gives you the broader scope in one place.
Paths Can Narrow the View
A prefix can also include a folder. For example, https://example.com/blog/ covers URLs beneath that path, including https://example.com/blog/seo-tips/.
It doesn't cover https://example.com/services/ or the blog on https://blog.example.com/. The ending slash matters too: /blog/ identifies that folder rather than a different path that starts with similar characters.
This narrower setup can be useful for a team responsible for one section. Enter the prefix carefully so the property matches the pages you want to monitor.
How Verification Differs
Before Search Console gives you property access, Google asks you to prove that you control the site or the relevant part of it. The available methods depend on the property type.
Domain Properties Usually Require DNS
For a Domain property, Google generally asks you to add a DNS verification record. DNS connects a domain name with services on the internet, and its records are managed through your DNS provider.
Search Console supplies a TXT record value for you to add. For a root domain, the host or name field is often blank or @, depending on the provider. DNS changes can take time to appear, so verification may not succeed immediately.
Google notes exceptions for properties hosted on Google products such as Blogger and Google Sites. Its property setup instructions explain the available verification methods.
URL-Prefix Properties Offer More Options
A URL-prefix property can use DNS verification too, but it also supports other methods. Depending on your setup and access, you may be able to upload an HTML file, add an HTML tag, or use an eligible Google Analytics or Google Tag Manager setup.
This flexibility helps when you can edit the website but don't control its DNS. For example, a site builder may provide a field for a Search Console verification tag.
Keep the verification record, file, or tag in place after setup. Removing it can cause you to lose verified access. Verification proves control of a property; it doesn't configure redirects or change which pages Google indexes.
Which Property Should You Choose?
Your choice comes down to two questions: how much of the site do you need to see, and what can you access to verify ownership?
Choose a Domain Property for Broad Coverage
We recommend starting with a Domain property when you own the domain and can add its DNS record. It's a practical fit for a small business site with a www version, a blog subdomain, or a shop on another subdomain.
It also reduces the chance of overlooking an older HTTP or non-www version. You can see the wider picture without creating a separate property for every host and protocol.
If you're unsure which option to pick, start with a Domain property. It gives you room to monitor the site as its structure grows.
Choose a URL Prefix for a Focused View
A URL-prefix property makes sense when you only need one version or folder. A content team working on https://example.com/blog/, for example, may prefer a property focused on that section.
It's also a useful starting point if DNS access isn't available and you can verify the site through an HTML tag or another supported method. You can add a Domain property later when you have the access needed.
The tradeoff is a narrower view. Keep other hosts, protocols, and folders in mind when interpreting your reports.
Can You Use Both Property Types?
Yes. A Domain property and one or more URL-prefix properties can exist at the same time. We like this approach when you need a broad site view as well as a closer look at a particular section.
For example, example.com can be your Domain property, while https://example.com/blog/ is a separate URL-prefix property. The Domain property covers the blog along with the rest of the domain. The prefix property focuses on the blog path.
Overlapping properties can report on the same URLs. Don't add their totals together as if they represent separate traffic.
You can also use filters in a broad property to investigate particular pages or sections. A separate prefix property can be convenient when that section deserves its own regular reporting view.
Access deserves the same care as coverage. Give people access to the property they need for their work, and understand the permissions you grant. A property focused on a folder can help keep a section's reporting separate, while the business retains control of the broader property.
For a closer look at the reports after setup, our Search Console beginner guide covers the checks worth making first.
How to Set Up Your Property
Once you've chosen your scope, the setup process is straightforward. You'll need access to the appropriate DNS settings or a supported verification method for the URL prefix.
- Open Google Search Console and choose Add property from the property selector.
- Select Domain for broad coverage, or URL prefix for a particular protocol, host, and optional path.
- Enter the domain or complete URL prefix. For a Domain property, leave off the protocol and any path.
- Follow the verification instructions for the method available to you. Add the supplied DNS record or complete one of the supported URL-prefix methods.
- Select Verify. Once verification succeeds, open the property and review its reports.
If DNS verification doesn't work right away, allow time for the record to become available. Also review whether the value and host field were entered in the correct DNS settings.
After setup, submit an XML sitemap for the pages you want Google to discover. A sitemap helps with discovery, but it doesn't guarantee indexing. Our guide to how Google crawls and indexes pages explains where sitemaps fit into that process.
What to Check After Setup
The right property gives you a useful view, but you'll still need to turn that information into practical SEO decisions.
Review Performance in Context
Open the Performance report and look at clicks, impressions, queries, and pages. Before comparing numbers, note which property you're viewing and which versions it covers.
A Domain property and a URL-prefix property may show different totals because their scopes differ. A report for https://example.com/ won't include a shop on https://shop.example.com/, even though the Domain property covers both.
Use the same property and date ranges when tracking changes over time. That consistency makes it easier to spot whether a change affects the whole site or one section.
Inspect Pages and Indexing Issues
For an individual page, select a property that includes the URL and use URL Inspection. Google's URL Inspection documentation explains the information available about the indexed version and live testing.
Start with important pages that should appear in search. Review the indexing status and Google's selected canonical, then investigate any issue that applies to the page. A successful live test doesn't guarantee that Google has indexed it.
If you find important pages marked as crawled but not indexed, our guide to troubleshooting crawled pages can help you investigate the next steps.
Start With the View You Need
For most site owners, a Domain property is the best starting point because it covers the domain's subdomains, protocols, and paths. A URL-prefix property gives you a focused view when you need one section or can't access DNS.
Choose the scope that matches your goal, then use the reports to guide consistent improvements. You can add another property later without giving up the view you already have.
