Use a Domain Property when...
You control DNS and want one Search Console property covering protocols and subdomains across your domain.
Domain Property vs Platform Property
A Domain Property covers an entire domain you control through DNS verification. A Platform Property covers an eligible creator profile on a third-party platform. They solve different ownership and measurement problems.
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 |
|---|---|---|
| Coverage | All protocols and subdomains under the verified domain. | Only the supported external platform profile and associated content. |
| Verification | DNS verification at the domain level. | External account authorization or supported platform verification. |
| Examples | www.example.com, shop.example.com and other subdomains under the domain. | A connected YouTube, TikTok, Instagram or X profile when supported. |
| Technical reports | Broad website indexing and technical Search Console reports. | Focused performance reporting for the external platform asset. |
| Best for | Organizations that control the entire domain and want consolidated coverage. | Creators who do not control the platform's domain but control their profile. |
| Ownership boundary | The verified organization controls DNS for the domain. | The creator controls the external profile, not the platform's DNS. |
Which property should you use?
Use a Platform Property when...
Your content lives on a supported third-party platform whose domain you do not own.
Use both when...
You operate an owned website while also building visibility through creator platforms.
Use a URL-prefix property instead when...
You need narrower website coverage and cannot or do not want to verify the full domain through DNS.
How to decide
- Check DNS control. A Domain Property requires access to the domain's DNS settings.
- Define the desired coverage. Choose domain-wide coverage for all protocols and subdomains, or a narrower property where appropriate.
- Treat creator profiles separately. Do not try to verify a third-party platform domain that you do not own.
- Connect supported profiles. Use Platform Properties for eligible creator accounts.
- Build a combined dashboard. Track the website and external profiles as separate but complementary search assets.
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