Google introduced Domain Properties, that feature lets you see data from a domain in one view within Google Search Console. This can consolidate your HTTP, https, www, non-www, m-dot, etc into a single property to get an aggregate view of your site’s performance & errors/warnings in a single Google Search Console property.
What is this?
Domain properties is a route for Google Search Console to let site owners, webmasters, developers, and SEOs see a whole view of a domain name in one area. Google use to handle this with property sets, but Google announced on Tuesday that property sets are going away. So today Google announced domain properties to replace it — a feature it tested back in November.
How it functions: “Domain properties show data for all URLs under the domain name, including all protocols, subdomains, & paths,” said Google. An omaind property combines data for all subdomains, protocols, & subpaths. Let me tell you one example if you describe a domain property as “example.com”, the data includes example.com, any subdomains of example.com (for example, m.example.com, support.m.example.com, www.example.com, and so on), & any subpaths of any of those domains, on both HTTP & https.
How do I use it?
Still may be rolling out right now, so if you do not see it yet, tomorrow you check back. what Google saying is, “if you already have DNS verification set up, Search Console will automatically create new domain properties for you over the next couple of weeks, with data entire reports.” Suppose If you do not have DNS verification set up, which I doubt is most of you, Google said you click on the add new domain property, go to the property selection, then add a new domain property, & use DNS verification.
I don’t want it: Since this is automated, Google said if you don’t want Google to combine the data and you want to segment Domain property data by subdomain, path, / protocol, use one of the following techniques:
(1) Add a page filter in the Performance report to see data for specific protocols/subdomains
(2) Create additional URL-prefix properties for segments of the Domain property; for example for the Domain property example.com, create additional properties for m.example.com, http://example.com, https://example.com/spain/, and so on.
Why it matters: It brings back a feature that was going out with the old Search Console, specifically property sets. Then, since this is automated via DNS verification, it requires you to have access to your DNS records & understand how to change those records. You may need to talk to your hosting provider when making DNS record changes.