
Google Search Console properties represent your site in the platform. The setup choice between domain property and URL prefix property affects what data you see.
Covers all subdomains and protocols of the domain. example.com property includes www.example.com, blog.example.com, app.example.com, all variants of HTTP and HTTPS.
Verification requires DNS access (TXT record).
Advantage: complete view of the domain.
Covers specific URL prefix. https://www.example.com/ is one property; https://example.com/ is another; https://blog.example.com/ is another.
Verification can use multiple methods (HTML file, meta tag, Google Analytics).
Advantage: targeted view of specific subdomain or path.
For most sites: set up domain property as primary. Complete view of the domain in one place.
Additional URL prefix properties for specific subdomains can supplement.
DNS verification (for domain property) requires hosting access to set TXT records. Some users find this intimidating.
For URL prefix, HTML file upload or meta tag verification works with WordPress easily. The verification options are flexible.
Switching property types doesn't carry over data. The new property starts fresh.
For sites with significant Search Console history, the existing property is worth keeping. New properties accumulate their own data.
Multiple users can access the same property at different permission levels. Owners, editors, viewers.
The permissions support team operations. Different team members see Search Console at appropriate access levels.
Search Console setup is initial work that supports years of SEO operation. The right setup makes future data useful.
For sites without proper Search Console setup, this is foundational work worth doing.
Site
Tools
We do not sell your email. We do not spam.
© 2026 RevealTheme. All rights reserved.