The site profile
Identity, domains, and data for each brand
Multiple brands on a single platform
Different brands, domains, and languages on one installation, each with its own identity and settings. It is the layer the catalog, case studies, SEO, and contact forms rely on to know which brand each item belongs to.
The site profile: each brand's identity, entered once
Identity data is entered in one place and used by every module: the sitemap, robots.txt, llms.txt, page metadata, and the site footer.
Name, logo, and favicon
Name and description per language, plus the logo and favicon the brand presents itself with.
Domains and base URL
One or more domains per brand, plus the canonical address used to build links, the sitemap, and structured data.
Site root section
Which part of the platform's content belongs to this brand and which does not.
Organization data
Organization type, phone number, and official profiles, which feed the structured data Google reads.
Default social image
Used when any page of the brand is shared and does not define an image of its own.
Automatic resolution: nobody picks the brand by hand
When a visitor arrives, or when the site requests content through the API, the platform works out the brand on its own, from the incoming domain or from the content section.
The right catalog
The products, case studies, and clients on display are the ones that belong to that brand.
That brand's SEO
The sitemap, robots.txt, and llms.txt are generated from its own data, not from the parent company's.
Inquiries with their origin
Every contact inquiry is recorded along with the brand it came in from.
Autonomy for each team
Each team manages its own content without seeing or affecting that of the other brands.
Multi-language: every site, in as many languages as it needs
The platform handles the hard part, and the team enters the content for each language in the same forms it always uses.
URLs per language
Consistent across the whole site, with no exceptions to redirect later on.
hreflang signals
In the sitemap, so Google does not read the language versions as duplicate content.
A single form
Content for each language is entered in the same record. There are no separate records to maintain in parallel.
Other modules on the platform
The brand is the axis for everything else: the product catalog, case studies, the sitemap, llms.txt, and the inquiries that reach the CRM all take their data from here and stay separated by brand.
All the modules
The platform's full lineup: design, SEO, catalog, case studies, CRM, and AI.