Setting up separate domains for 1C-Bitrix partner storefronts

Setting up Separate Domains for Partner Storefronts on 1C-Bitrix

Partner storefronts are working, but they all live on subdomains of the main site: partner-a.main-site.ru, partner-b.main-site.ru. Partners are unhappy—they want their own domains: partner-a-shop.ru, partnerbstore.by. To a customer, a storefront on someone else's subdomain looks like a page on a different website, not an independent shop. Separate domains solve this problem: each storefront is on its own domain, with its own SSL, with its own SEO.

Multi-Site Architecture and Domain Binding

1C-Bitrix supports binding multiple domains to a single installation through the multi-site mechanism. Each site (storefront) in the system has:

• Site identifier — unique code (e.g., s1, s2, partner_a).
• Domain — one or more domains attached to the site.
• Directory — folder on the server with site files (template, pages).

Domain binding to a storefront: in site settings (Settings → Sites), the domain name is specified. When accessing this domain, Bitrix automatically loads the right site—with its own template, catalog, and prices.

Web Server Configuration

At the web server level (nginx / Apache), each partner domain should point to the same 1C-Bitrix directory. Configuration:

• Nginx — separate server block for each partner domain. root points to the common Bitrix directory. The domain is passed in $host, Bitrix determines the site by it.
• Apache — via VirtualHost or .htaccess. All domains point to one directory.
• Wildcard configuration — if there are many partners, a single server block can handle all domains. Bitrix will figure out which site to show.

DNS: for each partner domain, an A record is created pointing to the server IP. If the partner's domain is registered with another registrar—the partner adds the A record in their DNS panel.

SSL Certificates

Each domain requires its own SSL certificate. Options:

• Let's Encrypt — free certificate for each domain. Automatic renewal via certbot. With many partners—automate issuance via script when adding a new storefront.
• Wildcard certificate — only for subdomains of one domain (*.main-site.ru). Not suitable for separate partner domains.
• Commercial certificate — if the partner wants EV or OV certificate with their own legal entity.

Automation: when adding a new partner, a script obtains a Let's Encrypt certificate, configures nginx, and reloads the server. Time to add a new domain—minutes, not days.

SEO for Separate Domains

Each storefront on its own domain is an independent site from the search engines' perspective. This matters:

• Canonical URLs — rel="canonical" points to the storefront domain, not the main site. Prevents content duplication.
• Sitemap.xml — generated for each domain separately. Contains only URLs of that storefront.
• Robots.txt — individual for each domain. Allows indexing of storefront pages, blocks service sections.
• Meta tags — title, description, og-tags are generated with the partner brand: "{Product} — buy at {Partner Name}".
• Hreflang — if storefronts are in different languages or regions.

Important: products in the catalog are the same across all storefronts. To avoid content duplication issues, each storefront should have unique descriptions or use canonical pointing to the partner's main domain.

Process of Adding a New Partner

1. Domain registration (partner or platform owner).
2. DNS setup — A record to server IP.
3. Create site in 1C-Bitrix: identifier, domain, directory.
4. Issue SSL certificate (Let's Encrypt).
5. Nginx configuration: server block for new domain.
6. Bind template, price type, catalog.
7. Generate sitemap.xml and robots.txt.
8. Verification: open storefront by domain, test order placement, check SSL.

What We Configure

• Binding separate domains to storefronts in 1C-Bitrix
• Web server configuration (nginx/Apache) for multi-domain operation
• SSL certificates for each domain (Let's Encrypt, automation)
• SEO: canonical, sitemap, robots.txt, meta tags for each storefront
• DNS instructions for partners
• Automation of adding new domains
• Testing: domain accessibility, SSL, correct catalog and pricing