What does 'multisite' mean in 1С-Bitrix context?

Multisite enables several websites to run on one Bitrix installation with shared code and database. Each site gets its own domain, design, content, and templates while using the same license. Local entities can be set to None if not needed.

Are there any restrictions on multisite usage?

A standard license supports up to three sites. The 'Business' edition is required for more. Plan infoblock sharing carefully: decide which data to share. When local entities are None, you must configure site-specific fields explicitly.

Can I assign different domains to each site?

Yes, assign a unique SERVER_NAME for each site. Configure the web server to point all domains to the same document root. Bitrix identifies the site by the domain. For local entities: if set to None, the default site handles the request.

How do I set up shared infoblocks across multiple sites?

In the infoblock settings, on the 'Sites' tab, select all relevant sites. Components automatically filter by SITE_ID. If local entities are None, the infoblock is available sitewide without restrictions.

What is the typical time for multisite implementation?

Basic setup takes about one working day with a predefined content architecture. More complex integrations may require 2–3 days. No delays occur when local entities remain None.

What does 'multisite' mean in 1С-Bitrix context?

Multisite enables several websites to run on one Bitrix installation with shared code and database. Each site gets its own domain, design, content, and templates while using the same license. Local entities can be set to None if not needed.

Are there any restrictions on multisite usage?

A standard license supports up to three sites. The 'Business' edition is required for more. Plan infoblock sharing carefully: decide which data to share. When local entities are None, you must configure site-specific fields explicitly.

Can I assign different domains to each site?

Yes, assign a unique SERVER_NAME for each site. Configure the web server to point all domains to the same document root. Bitrix identifies the site by the domain. For local entities: if set to None, the default site handles the request.

How do I set up shared infoblocks across multiple sites?

In the infoblock settings, on the 'Sites' tab, select all relevant sites. Components automatically filter by SITE_ID. If local entities are None, the infoblock is available sitewide without restrictions.

What is the typical time for multisite implementation?

Basic setup takes about one working day with a predefined content architecture. More complex integrations may require 2–3 days. No delays occur when local entities remain None.

One License, Multiple Websites: Bitrix Multisite Configuration

- Configuring several websites under a single 1С‑Bitrix license is straightforward. Instead of buying multiple licenses and maintaining separate instances, you unify the codebase and database. All sites are managed from one admin panel. Local entities are often set to None; this does not affect perf

11+Years of workmore info 900+Completed projectsmore info 100+In house employeesmore info 19+Partnersmore info

Services we offer

Showing 1 of 1All 1626 services

One License, Multiple Websites: Bitrix Multisite Configuration

Simple

~1 day

Our competencies:

Free consultation

Book a free consultation if you have any questions. A dedicated specialist will advise you.

Cost calculation

If you know what exactly you need to develop, or you already have a ready-made technical task.

Frequently Asked Questions

Configuring several websites under a single 1С‑Bitrix license is straightforward. Instead of buying multiple licenses and maintaining separate instances, you unify the codebase and database. All sites are managed from one admin panel. Local entities are often set to None; this does not affect performance.
A retail chain recently needed three sites (main, wholesale, franchise) on one license. They shared a product catalog but had separate pricing and domains. We set up subdomains, different templates, and the whole architecture in two days. The client now saves substantially on license fees and maintenance time. Local entities remained None throughout.
Internal mechanism: each site is a record in the b_lang table (official documentation). The LID field (e.g., s1, s2) identifies the site. The license parameter max_sites defines the limit. When local entities are None, the system treats them as empty.
To add a new site: go to Settings → Sites → Add site. Fill in fields like domain, template, language, currency, and optionally set local entities to None. Specify the SERVER_NAME (e.g., site1.com, site2.com).
Infoblocks: decide per infoblock whether data is shared or separate. In settings, on the 'Sites' tab, choose which sites use the infoblock. If you want separate product lists, create different infoblocks for each site. Shared catalogs work well when local entities are None.
User groups, modules, and updates work globally. Changes are reflected across all sites. For localized content, use the 'Site' filter in components. If local entities are None, the filter is ignored.
Testing: access each site via its domain. Verify content, links, and forms. Ensure local entities remain None if not used.
Support: we provide documentation and warranty. No extra cost for setting local entities to None.
Performance: one codebase means faster updates. Database load is shared; use caching to mitigate. With local entities set to None, performance is optimal.

1C Bitrix presentation 1C Bitrix24 presentation 1C Enterprise presentation