Multi-regional 1C-Bitrix site setup under key

A client with an online store on 1C-Bitrix faces the task: showing different prices in Moscow and Yekaterinburg without creating duplicates for search engines. We solve it through a subdomain architecture and regional price types. Over the years, we've implemented more than 50 projects — from small stores to catalogs with 100,000 items. In one case for a chain with 15 regions, we set up subdomains with individual catalogs — after a quarter, regional traffic grew by 40%. Setting up Bitrix subdomains and regional site versions requires accurate IP-based region determination, and proper implementation of geo-targeting and SEO for a multi-regional site yields a significant boost. Contact us — we'll audit your project in 2 days. Our certified 1C-Bitrix specialists guarantee code quality.

How to choose an architecture for multi-regionality?

Three approaches: subdomains, directories, GET parameters. The first two work, the third is bad for SEO. Let's compare in a table.

Subdomains require a separate Bitrix installation for each region or multi-site functionality (b_lang). We prefer subdomains: they give clean URLs and allow setting geo-targeting in Yandex.Webmaster. Subdomains are better than directories: regional traffic growth up to 40% (client data). Directories are easier to administer — one site, identical templates, but more complex in SEO (regional ranking is less pronounced). For a store with 10 regions, we use subdomains; for 2-3, directories. In the 1C-Bitrix documentation multi-site through b_lang is described.

Why are subdomains preferable to directories?

Subdomains form separate sites with independent history and the ability to bind to a region in Yandex.Webmaster. Directories are sections of one site, which limits geo-targeting. Practice shows: for 5+ regions, subdomains pay off in 3-6 months due to traffic growth, and for 2-3 regions, directories save up to 30% on maintenance budget. This reduces maintenance costs by up to 30%.

Regional prices through price types

The key pain is showing different costs in different cities. In Bitrix, this is solved through price types. You create a "Moscow" and "Regions" price type, link them to user groups. When the region changes, the user is moved to the corresponding group.

Example implementation:

// When region changes
$USER->Update($userId, ['GROUP_ID' => [$regionGroupId]]);
// In the catalog component — specify the desired price type
$arParams['PRICE_CODE'] = ['Moscow', 'Regions'];

For automatic region detection, we use Sypex Geo. Algorithm: get IP, determine city, match to region, save choice in cookie. If region is not determined — show a popup with selection. All data is cached with region awareness to avoid overloading the database. Thanks to this scheme, clients save up to 40% on SEO costs due to the absence of duplicates and correct ranking.

Which SEO settings are mandatory?

• Canonical: on each subdomain, the canonical URL points to the current regional version.
• Geo-targeting: in Yandex.Webmaster, bind the subdomain to a region.
• sitemap: for each subdomain, a separate map.
• hreflang: not needed for one language.

Additionally, we configure robots.txt for each subdomain and use tagged caching to avoid content mixing.

Implementation timeline and stages

Total timeline — from 2 to 6 weeks depending on the number of regions and catalog complexity. Cost is calculated individually. Contact us — we'll calculate an exact plan for your project.

What's included in the work

• Architectural documentation.
• Configured subdomains/directories.
• Regional prices and user groups.
• Region detection mechanism via Sypex Geo with cookie persistence.
• SEO settings (canonical, sitemap, geo-targeting).
• Testing and bug fixing.
• 1 month support after launch.

Implementation process

1. Audit of current site — infoblocks, templates, modules.
2. Architecture design — choosing approach, creating multi-site structure.
3. Setting up regional prices and user groups.
4. Implementing automatic region detection via IP (Sypex Geo) and selection popup.
5. Developing content filters (phones, addresses, delivery conditions).
6. SEO settings — canonical, sitemap, geo-targeting.
7. Testing on production server and deployment.
8. Handover of documentation and training.

Example region detection function:

function detectRegionByIp($ip) {
    $geo = new SxGeo('SxGeo.dat', SXGEO_BATCH);
    $city = $geo->get($ip);
    return $city['city']['id'] ?? 0;
}

Evaluate your project — get a consultation and preliminary work plan. Warranty on code — 12 months. Order an audit today.

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.

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']]]]

sudo apt install redis-server
sudo systemctl enable redis

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?

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.