Use a URL-prefix property when...
You control a website and want reporting for one exact protocol, hostname or directory scope.
URL-Prefix Property vs Platform Property
A URL-prefix property measures an exact website scope that you control. A Platform Property measures an eligible creator profile on a supported third-party service. The correct choice depends on whether the search asset is an owned group of URLs or an external creator account.
Related comparison guides
Choose the measurement tool or property type that matches the asset and question you are working with.
Key differences
| Area | First option | Second option |
|---|---|---|
| Asset covered | A specific URL prefix, including its chosen protocol and path scope. | A supported creator or social profile hosted on an external platform. |
| Verification | A supported website verification method for the precise URL-prefix property. | Authorization or connection through the eligible external platform account. |
| Coverage boundary | Only URLs beginning with the exact verified prefix. | The connected platform profile and eligible associated content. |
| Technical reports | Website indexing, page experience and other site-focused reports where available. | Creator-search performance reporting rather than control of the platform's technical infrastructure. |
| Best for | A site section, protocol, subdomain or property where narrow coverage is desired. | Creators who need Google Search performance data for supported third-party profiles. |
| Control required | Control of the website or verification method for the URL prefix. | Control or authorization of the external creator account. |
Exact scope matters: a URL-prefix property includes only URLs beginning with the precise prefix you verified, while a Platform Property follows the connected external profile rather than a website URL hierarchy.
When each option is most useful
Use a Platform Property when...
Your content is hosted on a supported external platform and you control the creator profile rather than the platform domain.
Use both when...
You operate an owned website and also publish through creator platforms that appear independently in Google Search.
Consider a Domain Property when...
You control DNS and want consolidated coverage across all protocols and subdomains.
How to use them correctly
- Write down the exact asset. Decide whether you are measuring owned URLs or an external creator profile.
- Check the desired scope. URL-prefix properties are exact; small differences in protocol, hostname or path matter.
- Verify with the correct method. Use website verification for the URL prefix and platform authorization for the creator profile.
- Keep reports separate. Do not combine totals until you understand the different coverage boundaries.
- Track shared business outcomes. Compare whether the website or creator profile is producing stronger search visibility and traffic.
Common mistakes
Comparing totals as though they cover the same activity
Different properties and analytics products measure different assets, events and user journeys.
Expecting verification to create traffic
Verification enables reporting; it does not guarantee rankings, impressions or clicks.
Ignoring filters and date ranges
Always compare equal periods and clear unnecessary filters before diagnosing a problem.
Using one report for every decision
Combine search visibility data with behavior and platform data when the decision requires more context.
Use each report for the question it was designed to answer. Similar-looking metrics can have different definitions and scopes.
Bring the signals into one operating record
Use SiteWatchlist to preserve baselines, track changes and connect Search Console visibility with the actions you take across websites and creator profiles.
Visit SiteWatchlist