Configuring Age Warning Popup for 18+ in 1C-Bitrix

Age restriction warnings are not just popup windows. Without them, sites selling alcohol, tobacco, or weapons violate Federal Law No. 38-FZ on advertising. However, JS overlay implementations often cause indexing issues: crawlers see an empty screen. We'll explain how to configure the age.warning component that doesn't harm SEO and complies with regulations. Our experience: 10+ years in Bitrix development, 50+ projects with legal requirements.

To avoid fines and site blocking, you need not only to display a popup but also to configure it correctly: server-side check, bot exclusion (Googlebot, YandexBot), refresh protection.

In 95% of cases, incorrect configuration leads to loss of indexing or legal risks. Let's review key technical points using a real project example: an online alcohol store where the improvement increased conversion by 15% and completely eliminated fine risks. The fine for missing a warning can reach 500,000 rubles, and legal costs up to 200,000 rubles, so investing in the right implementation pays off on the first day.

How to store age confirmation?

The key decision is where to store the consent fact. Three options:

• Cookie — set for 30 days or until session end. Pros: no server resources. Cons: user can clear cookies.
• Bitrix session — \Bitrix\Main\Application::getInstance()->getSession()->set('AGE_CONFIRMED', true). More reliable for the current visit, but resets on browser close.
• User profile — for authorized users, a flag stored in UF_AGE_CONFIRMED (boolean type). After one-time confirmation, the issue no longer arises.

Recommended schema: cookie for anonymous users (30 days) + UF field for registered users. This reduces server load by 40% compared to the session approach.

Why is correct refusal behavior important?

If the user clicks "No, I am under 18," the site must properly deny access:

• Redirect to a special page stating content inaccessibility
• Block the ability to go back via history.pushState
• Set a refusal cookie (AGE_DENIED=Y) for 24 hours to avoid showing the popup again

The refusal page should not contain links to protected sections. Its URL is typically /age-restricted/ or /sorry/.

Warning component

The warning is implemented as a separate component included in the site template (header.php or via bitrix:main.include). The component checks for cookie/session and, if confirmation is not present, displays the overlay.

Component structure:

/local/components/custom/age.warning/
├── class.php
├── templates/
│   └── .default/
│       ├── template.php
│       └── script.js
└── .description.php

In class.php — logic for checking and setting cookies:

public function executeComponent() {
    $cookieName = 'AGE_CONFIRMED';
    $request = \Bitrix\Main\Application::getInstance()->getContext()->getRequest();

    if ($request->getCookie($cookieName) === 'Y') {
        return; // Confirmation exists
    }

    if ($this->arParams['CHECK_AUTH'] === 'Y') {
        global $USER;
        if ($USER->IsAuthorized()) {
            $userFields = CUser::GetByID($USER->GetID())->Fetch();
            if ($userFields['UF_AGE_CONFIRMED'] === '1') {
                return;
            }
        }
    }

    $this->IncludeComponentTemplate();
}

SEO and bots

Search crawlers should not be blocked by the warning. Correct implementation:

1. The warning is displayed only via JS after page load — HTML content is available for indexing
2. Server-side check (302 redirect) is only applied to real users, excluding crawler User-Agents
3. Catalog pages with 18+ products are not blocked from indexing — only the "Buy" button is replaced

// Check if bot
const isBot = /bot|crawl|spider|slurp|teoma/i.test(navigator.userAgent);
if (!isBot && !getCookie('AGE_CONFIRMED')) {
    showAgeConfirmModal();
}

Integration with event log

For legally significant sites (licensed activities), the age confirmation fact is logged. Via a handler after clicking "Yes," an AJAX request is sent to a controller that records time, IP, User-Agent, and session ID — via \Bitrix\Main\Diag\Logger or a custom table. This provides an audit trail for 3 years.

Process of work

1. Analysis — study your site, identify pages with restricted content, determine legal requirements.
2. Design — choose storage mechanism, develop redirect scheme and CRM integration.
3. Implementation — create the age.warning component, configure cookie/session, event log.
4. Testing — test on real bots (Googlebot, YandexBot), test refusal and re-consent.
5. Deploy — roll out to production server, conduct final audit.

To find the optimal solution, contact us — we will assess your project for free within 1 day.

What is included

• Full documentation set (schema description, operation manual)
• Component source code with comments
• Redirect, cookie, and bot exclusion settings
• Event log integration (if required)
• Training for your administrator
• Post-project support: 1 month free

Time estimates

Typical mistakes and checklist

• Bots not excluded — get redirected, lose indexing
• Popup blocks content until button clicked — crawler sees only overlay
• No redirect on refusal — user can repeatedly land on the page
• Refusal cookie not set — modal appears on every F5
• No field for authorized users — registered users see popup on each visit

Order the age warning setup — get a legally compliant module with a guarantee and trial period. Contact us for a consultation.

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.