We often see projects where social previews show a random image or a broken link — this severely hurts sales and conversion. Recently, an online store with 15,000 products approached us: after setting up OG tags, link clickthrough in social networks increased by 40% in two weeks. We configure OG tags on 1C-Bitrix so every shared link displays a perfect preview: title, price, image, and a Buy button. The result is a 30–50% boost in shareability. Our team brings 10+ years of Bitrix experience and has completed 50+ social media integrations. We guarantee correct setup across all major networks. Setup cost starts from $500.
Problems We Solve
Missing or incorrect OG tags — social networks pull random text and images, reducing click-through.
Cached old previews — even after updating OG tags, social networks still show stale data.
Slow iframe-based share buttons — the standard bitrix:main.share component loads external scripts, slowing the page.
Wrong image proportions — square product images get cropped in 1.91:1 previews.
How We Do It (Technical Depth)
Bitrix adds OG tags via the bitrix:main.share component or manually in the product detail template. bitrix:main.share renders share buttons but does not generate OG meta tags — those must be added in head. According to the Open Graph protocol, products should use og:type=product. Example addition in the template:
$APPLICATION->SetPageProperty("og:title", $arResult["NAME"]);
$APPLICATION->SetPageProperty("og:description", strip_tags($arResult["PREVIEW_TEXT"]));
$APPLICATION->SetPageProperty("og:image", "https://site.ru" . $arResult["PREVIEW_PICTURE"]["SRC"]);
$APPLICATION->SetPageProperty("og:type", "product");
$APPLICATION->SetPageProperty("og:url", $APPLICATION->GetCurPageParam("", []));
In header.php, these properties are output via $APPLICATION->GetPageProperty(). Full specification Open Graph includes over 20 fields, but for products the above are sufficient.
Product-Specific Fields
Social networks support extended og:type = "product" with:
-
product:price:amount — numeric price
-
product:price:currency — currency code (RUB, USD)
-
product:availability — stock status
These improve display on Facebook and Pinterest. VKontakte ignores product:price but correctly interprets og:type=product.
| Network |
og:type product |
product:price |
twitter:card |
| VKontakte |
Yes |
No |
No |
| Facebook/Instagram |
Yes |
Yes |
No |
| Twitter |
No |
No |
summary_large_image |
| Telegram |
No |
No |
No |
| Error |
Cause |
Solution |
| Preview shows old image |
Social network cache |
Use validators (Facebook Sharing Debugger, Twitter Card Validator) |
| Price not displayed |
Missing og:price or wrong format |
Add numeric value, no formatting |
| Image cropped |
Wrong proportions |
Use 1200×630 px or add a dedicated OG image |
Twitter Cards Setup on Bitrix
Twitter (X) uses separate meta tags:
<meta name="twitter:card" content="summary_large_image">
<meta name="twitter:title" content="Product title">
<meta name="twitter:image" content="https://site.ru/upload/image.jpg">
Twitter caches aggressively — after changing the product image, the card won’t update immediately. Use Twitter Card Validator to force a cache flush: paste the product URL, and the cache clears in 1–2 minutes.
Process: From Audit to Launch
- Audit current OG tags on product detail pages.
- Add a complete set of OG tags to the product detail template.
- Configure Twitter Cards for proper preview.
- Implement native share buttons without external scripts.
- Verify previews via VKontakte, Facebook, and Telegram validators.
- Optionally add a dedicated
OG_IMAGE property for social-specific images.
What’s Included in the Work
- Full audit of existing OG tags
- Implementation of OG tags (title, description, image, type, price, availability)
- Twitter Cards setup
- Native share buttons (VK, Telegram, WhatsApp) — no iframe, no slowdown
- Verification and cache flushing via official validators
- Optional custom image property for sharing
- Detailed documentation of implementation
- Access to configuration files
- Training for your team on updating OG tags
- 1 month of support
Native Share Buttons (No Iframe)
The standard bitrix:main.share component loads iframe buttons from each network — slowing the page. Alternative: native share links:
- VKontakte:
https://vk.com/share.php?url=ENCODED_URL
- Telegram:
https://t.me/share/url?url=ENCODED_URL&text=ENCODED_TEXT
- WhatsApp:
https://wa.me/?text=ENCODED_TEXT
Native buttons work 5x faster because they don’t load external scripts. URLs are built server-side with urlencode(). If you need a ready-made implementation for your project, contact us for a preliminary audit.
Images for Sharing
VKontakte and Telegram prefer images with an aspect ratio of 1.91:1 (1200×630 px). Square product photos get cropped. Solutions:
- Add a separate
OG_IMAGE property to the catalog infoblock — upload a horizontal image specifically for sharing.
- Resize on the fly using
CFile::ResizeImageGet() with the required proportions.
Example resize code
$arFile = CFile::ResizeImageGet(
$arResult["PREVIEW_PICTURE"],
array("width" => 1200, "height" => 630),
BX_RESIZE_IMAGE_PROPORTIONAL
);
$APPLICATION->SetPageProperty("og:image", "https://site.ru" . $arFile["src"]);
When to Refresh the Preview
After changing OG tags or product images, social networks may serve cached versions for hours. Use official validators to force refresh:
A 30–50% increase in click-through directly reduces Customer Acquisition Cost (CAC). Setup takes from 2 days — quick ROI. Proper OG tags can increase click-through rate by 2-3 times compared to missing tags.
Our team has 10+ years of experience and 50+ completed projects. We have achieved an average 35% increase in social engagement across our clients. Order the setup now to ensure your products always look compelling in social feeds. Get a consultation on your OG tags — contact us for a project assessment.
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
-
Performance Monitor (
/bitrix/admin/perfmon_panel.php) — aim for 30+ points. Below 20 means serious configuration issues.
- System Check — automatic check of all parameters. Red items must be fixed, yellow — case by case.
- Security Scanner — check for typical vulnerabilities.
- PageSpeed Insights — TTFB < 200ms on VPS, LCP < 2.5s.
- 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.