How is Google planning to consolidate your Search Console properties and why does it matter?

Why is Google looking to group Search Console properties?

Currently, each URL variant requires a separate property in Search Console. A site accessible via http, https, with or without www creates up to 4 separate properties. Property sets already exist, but they remain limited and not user-friendly.

The automatic grouping aims to consolidate data under a single interface. There's no need to juggle multiple properties to analyze the same site. Google would automatically recognize that a series of URLs points to the same web entity and merge the metrics.

Which configurations would be affected by this grouping?

The obvious candidates are protocol and subdomain variants: http vs https, www vs root, but also potentially separate mobile versions (m.example.com) and CDNs with dedicated domains. The statement remains vague on the exact scope.

For multi-country sites with ccTLDs or language subdomains, the impact could be significant. A site with fr.example.com, en.example.com, and de.example.com could see its data aggregated or kept separate depending on Google's logic. There's no indication of whether the grouping will be configurable or enforced.

What is the expected timeline for this feature?

None. Mueller explicitly states that there is “nothing to announce at this time”. This typical Google phrasing signals that the project exists internally but remains in development or testing with no fixed deployment date.

SEOs should not modify their current configurations in anticipation of a hypothetical feature. The timeframe could range from a few months to several years, considering Google's pace with Search Console changes.

• The current property sets remain the only official solution for consolidating multiple URLs of the same site
• The automatic grouping would eliminate the need for manual configuration and maintenance of sets
• Complex architectures (multi-domains, multi-languages, CDNs) could see their management radically simplified
• No timeline is provided, making any anticipation premature
• The impact on international and multi-domain sites remains completely uncertain

Does this vague announcement hide real technical complexity?

Probably. Automatically identifying that a domain and its variants constitute “the same site” is not trivial. Google needs to cross-check 301 redirects, canonicals, DNS, SSL certificates, and crawl history to avoid false positives.

A problematic scenario: a site in gradual migration where old and new URLs coexist temporarily. The automatic grouping could prematurely merge data from two distinct versions, skewing analysis during the transition. Without manual control, this becomes risky.

Why is Google not giving any timeline?

Two plausible reasons. Either the project is in an exploratory phase without definitive internal validation, or the tests reveal problematic edge cases that delay deployment. Search Console features have a history of lengthy and chaotic development.

The lack of a time commitment also allows Google to silently withdraw the project if technical obstacles prove insurmountable. Announcing a date would create expectations the team cannot guarantee. [To be verified]: no information on beta tests or feedback from early adopters.

What real risks do SEOs face if the grouping is misconfigured?

The most serious risk: loss of granularity in data. If Google automatically merges properties you want to analyze separately, you lose the ability to compare performance by subdomain or variant.

Another risk: confusion in alerts and error reports. An indexing issue on a specific variant could be diluted in an aggregated report, delaying diagnosis. Current configurations allow for at least total control, even at the cost of increased complexity.

What should you do with your Search Console properties while waiting for this update?

Strictly nothing. Continue using property sets to consolidate your http/https and www/non-www variants. This method remains the only officially supported and functional option.

If you manage multi-domain or international architectures, document precisely which properties you want to analyze together and which should remain distinct. This mapping will be useful if Google rolls out a configurable system.

How can you prepare for potential automatic grouping?

Audit your 301/302 redirects and your canonical tags. An automatic grouping will likely rely on these signals to identify variants of the same site. Inconsistent redirects or misconfigured canonicals could lead to erroneous groupings.

Also, ensure that your current Search Console properties have correctly configured administrators and users. If Google merges the properties, permissions may be inherited or reset, temporarily creating access issues.

What mistakes to avoid in light of this vague announcement?

Do not delete your existing properties thinking that grouping will make them obsolete. You would lose the data history, irreplaceable for long-term trend analysis.

Also, avoid creating overly broad property sets including truly distinct domains. If Google automatically groups based on this erroneous basis, you will end up with mixed data that is impossible to untangle. Stay conservative in your current configurations.

• Keep your current functional and updated property sets
• Document precisely the architecture of your domains and subdomains
• Audit redirects and canonical tags to ensure their consistency
• Check user permissions across all your properties
• Do not delete any existing properties in anticipation
• Monitor official announcements from Google Search Central regarding deployment