Use a website property when...
You own or manage a website and need page-level Search Console data, indexing information and technical diagnostics.
Website Property vs Platform Property
A website property measures an owned web asset. A Platform Property measures eligible creator content hosted on a supported third-party platform. The right choice depends on what you control and which search journey you need to understand.
Property comparison guides
Use these pages to choose the Search Console property type that matches what you actually control and want to measure.
Key differences
| Feature | Website or domain property | Platform Property |
|---|---|---|
| Asset covered | A website or a URL-based web property you control. | A supported external creator or social profile. |
| Typical verification | Website ownership through a supported Search Console verification method. | Authorization or connection through the supported external platform account. |
| Data scope | Google Search performance for pages on the verified website. | Google Search performance associated with the connected platform profile and content. |
| Best for | Site owners, publishers, businesses and creators with an owned website. | Creators who want Google Search visibility data for supported third-party platforms. |
| Control level | You generally control the site, hosting, markup and technical SEO. | You control the profile and content but not the platform's underlying website. |
| Can coexist? | Yes. It can be used alongside Platform Properties. | Yes. It complements rather than replaces a website property. |
Which property should you use?
Use a Platform Property when...
You need Google Search performance data for a supported creator profile hosted on another platform.
Use both when...
Your website and creator profiles are separate search assets that send users to different destinations.
Prioritize the website when...
The owned site is the main conversion, product, revenue or authority destination.
How to decide
- List your search assets. Write down the website, channel and social profiles that matter.
- Identify what you control. A website property requires control of the site; a Platform Property relies on the supported external account.
- Match each question to a property. Use website reports for owned pages and Platform Property reports for connected creator content.
- Verify both where useful. Do not force one property type to stand in for the other.
- Compare trends, not raw totals. Different properties cover different assets, so totals are not directly interchangeable.
Can you use both?
Yes. A creator or business can benefit from a website property for its owned site and a Platform Property for supported external profiles. The reports answer different questions and should be viewed together rather than treated as substitutes.
Common mistakes
Assuming every property measures the same thing
Website and Platform Properties cover different assets and should not be expected to produce matching reports.
Choosing by convenience alone
Select the property that reflects what you control and what you need to measure.
Ignoring verification requirements
Website ownership and external-platform authorization use different verification paths.
Comparing Search Console with platform analytics directly
Google Search performance and internal-platform performance measure different discovery systems.
Property type does not create rankings. Adding or verifying a property enables reporting; it does not guarantee impressions, clicks or better positions.
Track every search asset in one operating view
Use SiteWatchlist to record changes across your website and creator profiles so you can see which search assets are gaining visibility over time.
Visit SiteWatchlist