Child sites & global brand setup

Subdomains are not a special case in GeoBubbles — they are treated like any other domain. If you want to track shop.example.com separately from example.com, just add it as its own site.

What is a special case is the parent / child site structure, which exists for brands that operate across multiple countries or languages.

When to use parent / child sites

Use this structure when one global brand runs in several countries or languages, and you want to:

• Keep each country/language as its own site (with its own locale, cities, competitors and prompts).
• Roll all of them up under one global brand for an aggregated view.

How it works

• The parent site represents the global brand — typically the main domain in its primary language (e.g. domain.com in English).
• Child sites represent the country/language variants. A child site can live on:
  • A path (e.g. domain.com/de)
  • A subdomain (e.g. de.domain.com)
  • A completely different domain (e.g. domain123.com)

Example:

Parent: domain.com           (EN)
 ├─ Child: domain.com/de     (DE)
 ├─ Child: de.domain.com     (DE-AT)
 └─ Child: domain123.com     (FR)

Each child site has its own metrics, prompts and competitors. The parent site provides the aggregated, global brand view.

When not to use child sites

• For purely technical subdomains of the same brand in the same country (www., shop., blog., app.) — these don't need a separate site at all. Entity matching strips subdomains, so mentions are credited to the same brand.
• For different brands — those are independent sites, not parent/child.