Domain property vs URL prefix in Search Console
Read the conclusion first
Choose the property that contains the URLs you need to measure. Use a Domain property for a domain-wide view, or a URL-prefix property for one protocol, host or directory. Keeping both is useful when their roles are explicit; adding their totals together is not.
Applicable conditions
Suitable for multiple subdomains, HTTP to HTTPS migration, independent directory operations, and multiple team divisions. DNS permission determines whether a domain property can be verified.
Before you open the report
The canonical host and protocol, all relevant subdomains, and the exact property strings being compared.
Use one concrete URL or report first. Keep account credentials and private visitor data out of shared notes.
Steps and verification
Make a URL coverage sheet before choosing
Copy the final homepage URL and examples from your shop, blog, language directories and other subdomains. Include any old HTTP addresses that still matter during migration. Next to each URL, write the business owner and whether it belongs in the report. This turns a vague request for ‘the whole website’ into an explicit scope.
For a teaching example, https://example.com/en/help/ and https://shop.example.com/item/ belong to the same domain-wide view, but a prefix for https://example.com/en/ includes only the first. A separate domain such as example.net needs a separate property. Do not infer coverage from similar branding.
Use a broad view and a focused view for different jobs
A Domain property is appropriate for monitoring the domain across its protocols and subdomains. It requires DNS verification. A URL-prefix property is useful for a team responsible for a specific host or path; enter its complete protocol and prefix. Verification options differ between these types.
Choose one broad property as the regular business baseline, then use focused properties or report filters for investigation. Record which view is authoritative for each report. If DNS access is unavailable, use an authorized existing property or verify an appropriate prefix; do not describe that smaller scope as the whole domain.
Reconcile differences using one shared slice
When two property totals differ, first list URLs that are included in one but excluded from the other. Then compare the same completed dates, search type and filters. A domain view can contain old HTTP URLs and multiple hosts that a current HTTPS prefix excludes. That difference alone is not an analytics failure.
For an overlap check, filter the broader report to the same URL scope and preserve the filter expression. Canonical attribution, aggregation and hidden query detail can still affect comparisons. Treat the comparison as an investigation with a stated scope rather than forcing every exported row to sum to a property total.
Keep scope selection separate from website changes
Adding a property does not redirect users, select a canonical URL or make Google prefer HTTPS. If the wrong host appears in search, investigate redirects and canonical signals on the pages themselves. If a team's report is wrong, correct the chosen reporting scope. These are different repairs.
Finish with a small coverage record: property string, verification or access owner, included URL examples, excluded examples and the monitoring purpose. Keep the old property available during a move so you can examine old URLs. A successful result is a repeatable view of the intended pages, not a larger headline traffic number.
Common mistake: Assuming a domain property is the canonical setting
A property is only a reporting scope; it does not set page canonical URLs, redirects, or the version shown in search results.
How to decide when you encounter different situations
Match your actual observation to a row before changing the page. If it does not match, collect the missing evidence first.
| What you see | Next step | How to confirm |
|---|---|---|
| Operating both www and the root domain | Use a scope matrix to confirm whether the two versions are included | Do not directly add overlapping properties |
| Responsible only for a certain directory | Create a prefix observation scope covering that directory | Spot-check URLs inside and outside the directory |
| HTTP and HTTPS data differ | Check old protocol redirects and property scope separately | Compare after unifying the window |
Two properties can be valid and still measure different scopes
Teaching scenario. Names, URLs and numbers illustrate the method; they are not customer or measured site results.
- What you observe
- Example: example.com is a Domain property; https://example.com/shop/ is a URL-prefix property. Their totals differ even over identical dates.
- What it establishes
- The Domain property combines supported protocols and subdomains. The prefix limits the URL scope to that prefix. Neither total is a substitute for the other.
- What to do next
- Write a scope map before investigating a discrepancy: main host, www, language subdomains and the shop path. Use the property that covers the question, then filter a specific page if needed.
What counts as a checked result
Compare a known URL inside both scopes and a URL outside the shop scope. Preserve the date and search-type filters with the export.
If a required check fails, keep the error and return to the matching decision branch. A blank record means unverified, not passed.
Leave with a checked result, not another vague instruction
- Your deliverable
- A URL-to-property coverage sheet and one declared main monitoring scope.
- Stop and resolve this first
- Do not compare totals until protocols, hosts and directories included by each property are understood.
Record missing evidence in the worksheet below. An unresolved test is useful information; a blank field is not a pass.
Checklist for this page
Fill in your own check results, then decide the next step. Blank means not yet verified, not normal. Content is saved only in the current local session and is not submitted to the server or AI.
Frequently asked questions
Do I need to delete the old property after migration?
Do not rush to delete it. Keeping the old property helps observe old URLs, redirects, and migration trends.
Which property should I choose for one subdirectory?
Use a prefix covering that path, or a broader property with an explicit page filter. Record the choice so your next comparison uses the same scope.
Official materials and usage boundaries
This page provides operational judgment and checking methods, and does not show customer success cases. Calculation examples and request samples are teaching materials, not actual website metrics. Google's reports, conditions, and interfaces may change; please refer to the current official documentation.
Read the corresponding Google official documentationContinue with the relevant tool
Use AISEO Site to read the property you selected here. Keep its protocol and subdomain coverage in your notes before comparing totals.
See how it works →