Content split across new subdomains or microsites instead of the established host (siteAuthority)

The 2024 leak documents a site-level siteAuthority attribute applied in Qstar and a hostAge attribute used to sandbox fresh spam, and Google confirms site-wide signals exist. New hosts start without accumulated site-level standing. This is a proxy based on leaked documentation; Google has not confirmed how siteAuthority is used.

Where the content serves the same audience, consolidate it into subfolders of the main host and 301 redirect each old URL to its equivalent. Keep separate hosts only where there is a genuine brand, legal or technical reason.

1. List every hostname the organisation publishes on, from DNS records, Search Console properties and a crawl of outbound links from the main site.
2. For each extra host, note its first-seen date (for example from the Wayback Machine) and what audience its content serves.
3. Flag hosts whose content targets the same audience and queries as the main site.
4. Compare Search Console impressions per page on the extra hosts against equivalent sections of the main host.

Written for the Site authority (siteAuthority) page (evidence: Trial or leak evidence). Google has not documented this system in a way a site can test directly, so this check measures a proxy for it, not the system itself.

Indirect. Estimate only: consolidation typically concentrates links and site-level signals on one host, but the effect of siteAuthority specifically cannot be measured.

CompressedQualitySignals and PerDocData modules of the 2024 Content Warehouse leak; iPullRank analysis; Google's ranking systems guide on site-wide signals.