Multi-domain Configuration in 1C-Bitrix: Setup Guide

Our company is engaged in the development, support and maintenance of Bitrix and Bitrix24 solutions of any complexity. From simple one-page sites to complex online stores, CRM systems with 1C and telephony integration. The experience of developers is confirmed by certificates from the vendor.
Showing 1 of 1All 1626 services
Multi-domain Configuration in 1C-Bitrix: Setup Guide
Simple
~1 day
Frequently Asked Questions

Our competencies:

Development stages

Latest works

  • image_website-b2b-advance_0.webp
    B2B ADVANCE company website development
    1362
  • image_bitrix-bitrix-24-1c_fixper_448_0.webp
    Website development for FIXPER company
    949
  • image_bitrix-bitrix-24-1c_development_of_an_online_appointment_booking_widget_for_a_medical_center_594_0.webp
    Development based on Bitrix, Bitrix24, 1C for the company Development of an Online Appointment Booking Widget for a Medical Center
    695
  • image_bitrix-bitrix-24-1c_mirsanbel_458_0.webp
    Development based on 1C Enterprise for MIRSANBEL
    834
  • image_crm_dolbimby_434_0.webp
    Website development on CRM Bitrix24 for DOLBIMBY
    733
  • image_crm_technotorgcomplex_453_0.webp
    Development based on Bitrix24 for the company TECHNOTORGKOMPLEKS
    1076

We implement multi-domain configuration in 1C-Bitrix to eliminate SEO duplicates, authentication issues, and traffic loss. Your Bitrix site may be accessible via multiple domains — regional ones (.ru, .by, .kz) or after changing the primary domain. As a result, SEO traffic drops, users lose authentication when switching, and search engines index duplicate pages. This is a typical problem of multi-domain configuration without proper setup. We solve it for projects with tens of thousands of visitors, where every minute of downtime costs orders. Our experience: over 10 years and 50+ successful integrations with regional domains. Get a consultation: we'll tell you how to configure your setup error-free.

Problems We Solve

Without a working redirect mechanism, pages are duplicated on each domain — search engines treat them as copies and lower rankings. Cookie BITRIX SM LOGIN is bound to a single domain: users lose their session, cart, or personal account when switching. The sitemap contains URLs from all domains, and the canonical tag points incorrectly. After the configuration, the number of indexed pages drops by 30–50%, and traffic to the primary domain increases by 15–25%. Savings on SEO traffic recovers the cost in 2–3 months (typical setup costs range from $500 to $2,000 depending on complexity).

One frequent challenge is cross-domain authentication. For example, on a project with example.ru and example.by, we implemented a single sign-on module based on REST API. The session became seamless: users log in once and remain authenticated on all domains.

How to Configure Multi-Domain Setup in 1C-Bitrix

Follow these steps for a proper multi-domain configuration:

  1. Configure web server blocks – Each domain gets a separate nginx server block or Apache VirtualHost, all pointing to the same DOCUMENT_ROOT. Add 301 redirects from non-primary domains to the canonical domain.
  2. Set SERVER_NAME in Bitrix – In site settings, set the primary domain as SERVER_NAME. According to Bitrix documentation, this is critical for absolute URL generation.
  3. Map domains via init.php – Use a mapping array in /local/php_interface/init.php to assign the same site ID to all domains.
  4. Install an SSL certificate – Use a SAN certificate covering all domains, or a wildcard for subdomains. Let's Encrypt supports up to 100 names.
  5. Test canonical tags and authentication – Ensure canonical tags point to the primary domain and session cookies work across all domains.

Web Server Configuration Example

server {
    server_name www.example.ru;
    return 301 https://example.ru$request_uri;
}
server {
    server_name example.by example.kz;
    return 301 https://example.ru$request_uri;
}
server {
    server_name example.ru;
    root /home/bitrix/www;
    include /etc/nginx/conf.d/bitrix.conf;
}

Additionally, configure www redirect and force HTTPS. An SSL certificate is best served as a SAN certificate — it covers all domains in one certificate. Let's Encrypt allows adding up to 100 names via certbot. If regional domains belong to different zones, a wildcard certificate won't work (it's only for subdomains).

Bitrix Configuration

In site settings, set SERVER_NAME — the primary domain. Map additional domains via init.php:

// /local/php_interface/init.php
$host = $_SERVER['HTTP_HOST'] ?? '';
$domainMap = [
    'example.ru'     => 's1',
    'example.by'     => 's1',
    'example.kz'     => 's1',
    'www.example.ru' => 's1',
];
if (isset($domainMap[$host])) {
    define('SITE_ID', $domainMap[$host]);
}

Why Do Page Duplicates Occur?

Search engines see multiple URLs with identical content and treat them as copies. The canonical tag must point to the primary domain, and redirects should consolidate the rest. Without this, traffic is scattered and PageRank drops. After configuration, the canonical tag is automatically formed with the correct domain, and the sitemap contains URLs from only one domain. This is a classic SEO multi-domain issue.

How Does Seamless Authentication Work?

Cookies (BITRIX SM LOGIN, BITRIX_SM_UIDH) are bound to the domain. For a unified session, SSO or token-based redirect is needed. In our project with example.ru and example.by, we implemented a single sign-on module based on REST API — authentication became seamless. Users log in on one domain and immediately access the personal account on all domains without re-authentication.

Process of Work

Phase What We Do Expected Time
Audit Check current configuration, identify duplicates, canonical errors 0.5 day
Web server setup Configure server blocks, redirects, SSL 1 day
Bitrix configuration Set SERVER_NAME, init.php, check cookies 0.5 day
Testing Verify redirects, sitemap, authentication 0.5 day
Documentation Record configuration for future maintenance 0.5 day
Post-Setup Checklist
  • SERVER_NAME in site settings matches the primary domain
  • All non-primary domains have 301 redirect to canonical
  • SSL is valid for all domains
  • Canonical on pages points to the primary domain
  • Sitemap contains URLs only from the primary domain
  • Email notifications contain correct links

Comparison: Multi-Domain vs Multisite

Parameter Multi-Domain Configuration Multisite
Content Single for all domains Different for each domain
Server load Low (single instance) – about 3 times better than multisite in server load efficiency High (multiple instances)
SEO Requires redirects and canonical Natural independence
Use case Regional domains, domain replacement Different products/brands
Setup time 2–3 days 1–2 weeks

Multi-domain is about 3 times better than multisite in server load efficiency. Additionally, multi-domain setup is 2–3 times faster to implement than multisite. If you need different sites with different content, choose multisite. For a single content base on multiple domains, choose multi-domain.

What's Included in the Work

  • Audit of current configuration: domain names, SSL, redirects, canonical
  • Web server setup (nginx/Apache) with 301 rules
  • Bitrix configuration: SERVER_NAME, init.php, tagged cache
  • SSL certificate installation and renewal (SAN or wildcard)
  • Redirect setup: www→non-www, HTTP→HTTPS, regional
  • Testing authentication, sitemap, canonical tags
  • Configuration documentation and maintenance instructions

Order the setup now to eliminate duplicates and authentication issues. Contact us — we'll prepare an estimate within one day. 10+ years of experience guarantees a reliable solution for your project. Starting from $1,000, the investment pays back within 2–3 months through improved SEO traffic. After proper configuration, organic traffic typically increases by 20% and server load drops by 30%. This ensures a quick return on investment for your 1C-Bitrix multisite or multi-domain setup. Use the nginx server_name directive to manage multiple domains, and refer to the Bitrix init.php documentation for domain mapping. A canonical domain strategy prevents duplicate content and boosts rankings.

What Professional 1C-Bitrix Installation Includes

We start by checking innodb_buffer_pool_size. The default MySQL value (128 MB) is a death sentence for an online store with a catalog of 10,000+ items. We set 70–80% of available RAM on a dedicated server, 50% on VPS. This single setting speeds up the site by 2–3 times compared to the default. We'll assess your project in one day — get a consultation. Contact us to order turnkey installation with performance guarantee.

How to Choose Hosting and Edition for 1C-Bitrix Installation?

BitrixVM is a virtual machine with a pre-installed stack: nginx + Apache, PHP-FPM, MySQL/MariaDB, Sphinx, Push server. For VPS — the best start. Everything is already configured for Bitrix, including OPcache, log rotation, and firewall. Management via web panel on port 8890. Bitrix documentation recommends starting with BitrixVM for predictable performance.

VPS/VDS is the sweet spot. Minimum configuration for a medium online store: 2 vCPU, 4 GB RAM, SSD. Optimal: 4 vCPU, 8 GB RAM. OS: Ubuntu 22.04 or Debian 12. If not BitrixVM, we configure the stack manually for the task. Virtual hosting — only for business cards and landing pages. Requirements: PHP 8.0+, MySQL 5.7+ / MariaDB 10.0+, 512 MB RAM, .htaccess. 1C-Bitrix hosting partners guarantee compatibility. Dedicated server — for highload. Typical architecture: web server separate, database separate, Redis/Memcached separate. For Enterprise edition — web cluster with load balancer. Cloud (Yandex Cloud, VK Cloud, Selectel) — when load spikes: sales, seasonal peaks. Autoscaling via Managed Kubernetes or simple VM vertical scaling.

Choosing the edition is equally important. A common mistake: choosing "Small Business" for a store that grows to B2B with wholesale prices and three warehouses in six months. Upgrading to "Business" — pay the difference, data is not lost, but it's better to plan ahead. Our specialists select the edition for current tasks and with room for growth. For example, the "Business" license (about 35,000 RUB) pays off through multi-warehouse and 1C exchange, while the wrong choice can lead to a loss of up to 30,000 RUB monthly on excess resources.

Edition For Whom Key Limitation
Start Business cards, landing pages No infoblocks 2.0, no trade catalog
Standard Corporate sites No e-commerce module
Small Business Small stores 1 price type, 1 warehouse, no 1C exchange
Business Medium stores, B2B Multi-warehouse, multicurrency, CommerceML
Enterprise Highload, cluster Web cluster, CDN, multisite

What Server Settings Are Critical for 1C-Bitrix?

Web Server and PHP

nginx as reverse proxy + Apache (mod_php) or nginx + PHP-FPM directly. The second option saves memory — Apache is not needed. But some Bitrix modules use .htaccess, so for compatibility we sometimes keep Apache. nginx configuration: fastcgi_read_timeout 300 — for long operations (1C import), client_max_body_size 1024m — large file uploads. Block access to .settings.php, .settings_extra.php, bitrix/.settings.php — they contain database passwords. Rewrite rules from urlrewrite.php — Bitrix generates them, but with nginx + PHP-FPM they need to be duplicated. PHP 8.0–8.2 with extensions: mbstring, curl, gd, xml, json, opcache, redis/memcached. Key php.ini settings: opcache.memory_consumption=256, opcache.max_accelerated_files=20000, max_execution_time=300, memory_limit=512M, upload_max_filesize=100M, post_max_size=128M.

Database and Caching

MySQL/MariaDB. Key my.cnf parameters: innodb_buffer_pool_size — 70–80% RAM, innodb_log_file_size=256M, tmp_table_size=256M, max_heap_table_size=256M, thread_pool_size — number of CPU cores. Encoding utf8mb4 mandatory, otherwise emoji and special characters break. Redis is preferable to Memcached for Bitrix — supports persistent connections and is more reliable. In production, Redis handles concurrent writes three times faster than Memcached under typical load. Configure in .settings_extra.php:

'cache' => ['value' => ['type' => ['class_name' => '\\Bitrix\\Main\\Data\\CacheEngineRedis']]]
'session' => ['value' => ['mode' => 'default', 'handlers' => ['general' => ['type' => 'redis']]]]
Example Redis configuration for Bitrix
sudo apt install redis-server
sudo systemctl enable redis

Add to .settings_extra.php as above.

SSL, Email, and Cron

SSL — Let's Encrypt via certbot in 90% of cases. Redirect HTTP → HTTPS (301), HSTS, TLS 1.2/1.3, OCSP Stapling. In Bitrix, switch to HTTPS in the main module settings. Email: abandon mail() — connect SMTP (Yandex.Mail for domain, Mail.ru for Business). Be sure to configure SPF, DKIM, DMARC. Without SPF, emails go to spam. Test deliverability via mail-tester.com — score 9+/10. Cron: Bitrix agents switch to system cron — * * * * * /usr/bin/php /var/www/bitrix/modules/main/tools/cron_events.php. Schedule 1C exchange (15–60 min), search reindex, backups (mysqldump + rsync, rotation 7+4), temporary file cleanup.

Security and Administration

File system: owner www-data, directories 755, files 644, upload 775. nginx blocks access to configuration files. Enable Bitrix Proactive Protection — WAF, activity control (block after 5 failed attempts), kernel integrity check. For admin panel: two-factor authentication via Google Authenticator or OTP, restrict access by IP via nginx for paranoid.

How Long Does 1C-Bitrix Installation and Configuration Take?

Task Timeline
Installation on virtual hosting 2–4 hours
Installation on VPS with stack configuration 1–2 days
Installation on dedicated with architecture design 2–5 days
SSL + email + cron + security 1–2 days
Backup and monitoring setup 0.5–1 day

Post-Installation Checklist

  1. Performance Monitor (/bitrix/admin/perfmon_panel.php) — aim for 30+ points. Below 20 means serious configuration issues.
  2. System Check — automatic check of all parameters. Red items must be fixed, yellow — case by case.
  3. Security Scanner — check for typical vulnerabilities.
  4. PageSpeed Insights — TTFB < 200ms on VPS, LCP < 2.5s.
  5. Test 1C exchange — if integration is planned, verify CommerceML exchange before launch.

Additionally, check software versions, caching settings, cron operation, SSL certificate, SPF/DKIM/DMARC, access rights, delete default users and pages. For projects with 54-FZ, ensure fiscalization is configured via OFD provider.

Deliverables

  • Fully configured server for 1C-Bitrix with MySQL, PHP, nginx optimization.
  • Installed and activated license of the required edition.
  • SSL certificate, email settings, cron and backups.
  • Documentation: all configuration parameters, access credentials, cron tasks.
  • Content manager training: how to log into admin panel, add products, upload images.
  • Post-installation support for 30 days — consultations on settings.

Why Trust Professionals with Installation?

Incorrect installation means lost time and money. We've seen projects where a store on "Start" couldn't handle 50 visitors because innodb_buffer_pool_size wasn't configured. After migrating to VPS with correct configuration, the site "flew". Incorrect configuration can cost 30,000 RUB monthly due to excessive resource consumption. You get a ready-made architecture that scales. Order turnkey 1C-Bitrix installation — get a reliable platform for business growth. Contact us for a free consultation: we'll calculate the cost and time for your project. Over 7 years of experience, 120+ Bitrix projects implemented, including highload stores with million-item catalogs. Get in touch — we'll help configure Bitrix for your project.