Creating a landing page in Bitrix24.Websites

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.
Our competencies:
Development stages
Latest works
  • image_website-b2b-advance_0.png
    B2B ADVANCE company website development
    1175
  • image_bitrix-bitrix-24-1c_fixper_448_0.png
    Website development for FIXPER company
    811
  • 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
    564
  • image_bitrix-bitrix-24-1c_mirsanbel_458_0.webp
    Development based on 1C Enterprise for MIRSANBEL
    747
  • image_crm_dolbimby_434_0.webp
    Website development on CRM Bitrix24 for DOLBIMBY
    655
  • image_crm_technotorgcomplex_453_0.webp
    Development based on Bitrix24 for the company TECHNOTORGKOMPLEKS
    976

Creating a Landing in Bitrix24.Sites

Bitrix24.Sites is a built-in constructor available in cloud plans of Bitrix24 starting from "Basic". The tool is designed for one task: build a landing page connected to CRM without developer involvement. This is simultaneously its strength and its main limitation.

What the Constructor Can Do

The editor works on a block principle. A page is assembled from ready-made sections: cover, text with image, gallery, video, testimonials, price list, contacts, map. Each block is configured visually — colors, fonts, spacing, background images.

Key capabilities:

  • CRM forms — embedded in any block. An application creates a lead or deal, launches robots and triggers in the funnel
  • Online chat — Bitrix24 widget is connected with one setting, conversations appear in CRM as an open channel
  • Callback — return call button through built-in telephony
  • Analytics — connecting Yandex.Metrica, Google Analytics, Facebook Pixel through settings fields
  • Templates — library of ready-made designs for different industries (real estate, medicine, education, services)
  • SSL — free Let's Encrypt certificate when connecting your own domain
  • Domain — you can use the technical address *.bitrix24.site or bind your own domain via CNAME record

Constructor Limitations

Bitrix24.Sites is a SaaS environment with a strictly defined perimeter. Understanding limitations before starting saves time and budget.

Limitation Details
No PHP access Server-side logic is completely closed. You can't write a handler, connect a module, or change the core behavior
JavaScript limited A script can be embedded through the "HTML code" block, but it runs in a sandbox. Access to the page DOM is partial, REST API Bitrix24 is available
Third-party modules You can't connect external PHP libraries, composer packages, third-party payment systems directly
Responsiveness Automatic, but without manual breakpoint control. The mobile version is generated by the constructor
Number of pages Depends on the plan. On "Basic" — limitations on the number of sites
Loading speed Rendering on the Bitrix24 side, optimization is limited to constructor settings

SEO Capabilities

The constructor allows you to set title, description, and og-tags for each page. Robots.txt and sitemap.xml are generated automatically. You can set up a 301 redirect when changing a URL.

What's missing: managing Schema.org micromarkup, hreflang, canonical (set automatically), configuring server caching headers, AMP version.

For a landing that works on paid traffic, these tools are sufficient. For organic promotion in a competitive niche — may not be enough.

Workarounds for Limitations

Despite being closed, some limitations can be worked around using standard tools.

Integration via REST API. JavaScript code in the "HTML" block can call the REST API Bitrix24 to read and write CRM data. For example: loading a product catalog from CRM, submitting an application with additional fields, checking order status.

Webhooks for external services. A CRM form creates a lead — a robot is triggered on the event, which sends a webhook to an external system. Through this chain, you can connect almost any service: mailing, SMS notifications, ERP.

Google Tag Manager. Instead of directly embedding scripts, a GTM container is connected through analytics settings. Then any third-party pixels and scripts are managed from the GTM interface.

Embedded applications. Applications are installed through the Bitrix24 marketplace, expanding site functionality: additional blocks, widgets, integrations with payment systems.

Domain Connection

The process of binding your own domain:

  1. A CNAME record is created in the DNS zone of the domain, pointing to *.bitrix24.site
  2. The domain name is specified in the site settings
  3. An SSL certificate is issued automatically via Let's Encrypt (usually within 10–30 minutes)
  4. HTTP traffic is redirected to HTTPS using standard tools

Subdomains work similarly. You can bind multiple domains to one site — one will be primary, others will be redirected.

When Bitrix24.Sites is the Right Choice

The constructor solves the task if the landing exists in connection with CRM and doesn't require non-standard logic: collecting applications, signing up for a consultation, subscribing, registering for an event. A marketer manages the page independently, changes are made in minutes, and data is immediately in CRM.

If you need multi-step forms with dependent fields, integration with 1C, custom animations, or promotion in search engines — consider a landing on "1C-Bitrix: Website Management" or custom development.