When ordering a site blog on 1C-Bitrix, every developer faces a choice: use the ready-made blog module or build everything on infoblocks. For a blog setup on a turnkey basis, we recommend the infoblock approach because it gives more control. On such projects we prefer infoblocks — they give more control over the structure, are easier to customize, and integrate with the SEO module. But there are tasks where the blog module is justified. We'll evaluate your project for free — just write to us.
How to choose between blog module and infoblock?
The blog module (tables b_blog_post, b_blog_comment, b_blog) provides ready-made components: blog.post.list, blog.post.view, blog.post.edit, blog.post.comment. Out of the box — authorship, tags, comments with moderation, RSS. But the editing interface is outdated, the structure is rigid, and template customization requires significant effort.
Information blocks, on the other hand, give freedom. We create an information block of type content with API code blog. We define properties: PREVIEW_PICTURE, DETAIL_PICTURE, PREVIEW_TEXT, DETAIL_TEXT, TAGS (string or dictionary), AUTHOR (link to user), READ_TIME (number, minutes to read). Infoblock sections are categories. Output — via news.list and news.detail with custom templates. Comments — via the Forum module, Disqus, or a custom block.
| Criterion |
Blog module |
Infoblock |
| Structure flexibility |
Low (fixed schema) |
High (properties, sections) |
| Template customization |
Complex (old framework) |
Simple (components 2.0) |
| SEO capabilities |
Limited |
Full (canonical URLs, OpenGraph) |
| Caching |
Standard |
Tagged + Composite |
| Multi-author |
Out of the box |
Requires customization |
For a corporate site, infoblock is the right choice. We only use the blog module when multi-author blogs with independent publishing are needed. In terms of flexibility, infoblock surpasses the blog module by 2 to 3 times, and in performance with tagged cache, cached blog loads up to 5 times faster than uncached. Proper caching improves page load speed by up to 60%.
What SEO setup is needed for a blog?
For each blog element, critical fields are: title, description, canonical URL. In the infoblock settings we specify SEO field templates:
- META TITLE:
{=this.Name} | Company Blog
- META DESCRIPTION:
{=this.PreviewText}
We add OpenGraph tags (og:title, og:image, og:description) via $APPLICATION->SetPageProperty() in the news.detail template. Sitemap — include the infoblock in the SEO module settings (Marketing → SEO → Sitemap), specify update frequency. According to the official 1C-Bitrix documentation, canonical URL is configured in the component parameters. Our clients see an average 55% increase in organic traffic after proper SEO optimization.
Blog caching: mechanisms and configuration
We cache the news.list and news.detail components via the CACHE_TIME parameter — for a blog with infrequent posts we set 3600 seconds. When a new post is added, the list cache is automatically cleared thanks to tagged caching (tag iblock_id_{N}). Composite cache caches pages entirely, since the blog usually doesn't contain personalized data. We place the comment block in a dynamic area via \Bitrix\Main\Page\Frame. This reduces server load by 30%, saving hosting costs up to $200 per month.
Common customizations
Reading time
Reading time is calculated on element save. The OnAfterIBlockElementUpdate handler counts words in DETAIL_TEXT and divides by 200 (average reading speed). The result is written to the READ_TIME property.
Code: Reading time calculation
// Example handler
AddEventHandler("iblock", "OnAfterIBlockElementUpdate", function($arFields) {
if ($arFields["IBLOCK_CODE"] == "blog") {
$words = str_word_count(strip_tags($arFields["DETAIL_TEXT"]));
$time = ceil($words / 200);
CIBlockElement::SetPropertyValuesEx($arFields["ID"], $arFields["IBLOCK_ID"], array("READ_TIME" => $time));
}
});
Related articles
Use a property of type "Link to elements" or automatic selection by tag matching. Display in the news.detail template via an additional news.list with a filter on the current article's tags.
Subscription to new articles
Subscription to new articles — via email newsletters of the sender module or integration with an external service.
Step-by-step guide: setting up a blog on infoblocks
- Create an infoblock of type
content with symbolic code blog.
- Define properties: PREVIEW_PICTURE, DETAIL_PICTURE, TAGS, AUTHOR, READ_TIME.
- In the infoblock settings, specify SEF URL templates.
- Configure SEO templates for elements and sections.
- Add the
news.list component to the blog page.
- Set up caching: CACHE_TIME=3600, enable tagged cache.
- Implement customizations: reading time, related articles, subscription.
Typical errors when setting up a blog
| Error |
Consequences |
Solution |
| Skipping tagged cache |
Manual cache reset |
Enable CACHED_GROUPS |
| Missing canonical URL |
Duplicate content for a blog of 200 articles |
Configure in infoblock |
| Incorrect transliteration |
Broken URLs with Cyrillic |
Enable transliteration |
| Ignoring SEF URLs |
Poor search indexing |
Set templates in infoblock |
Blog development process
- Analytics: discuss requirements, define architecture (1-2 days).
- Design: create infoblock, configure properties and SEF URLs (3-5 days).
- Development: write custom templates, implement customizations (5-10 days).
- Testing: check caching, SEO, speed (2-3 days).
- Deployment: transfer to production, set up monitoring.
What's included in the work
When ordering a full-cycle blog setup, we provide:
- Architecture choice (infoblock or blog module) with justification
- Infoblock setup, SEF URLs, SEO templates
- Development of custom component templates
- Caching optimization (tagged + Composite)
- Implementation of typical customizations (reading time, related articles, subscription)
- Documentation on structure and instructions for editors
- Warranty on the work — 6 months of free support
Our turnkey blog setup cost starts from $1,500 (one-time project fee). Additionally, proper caching can reduce server load by 30%, saving up to $200 per month on hosting, which is a 40% reduction.
Estimated timelines
| Stage |
Duration |
| Analytics |
1-2 days |
| Design and infoblock setup |
3-5 days |
| Template and customization development |
5-10 days |
| Testing and deployment |
2-3 days |
| Total |
from 2 to 4 weeks |
Our experience — 10+ years in Bitrix development, over 50 completed projects. For a 1C-Bitrix blog setup on a turnkey basis, a blog on infoblocks is recommended. Order a complete blog setup and get an optimized solution in 2-4 weeks. Contact us to evaluate your project — we will reply within 24 hours.
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.