IT Company Website Development on 1C-Bitrix
An IT company sells expertise. The website must prove this expertise—not with words like "we are professionals," but with structured portfolio, technical depth in the blog, and clear service navigation. 1C-Bitrix here functions as a CMS with flexible info-block architecture, a comprehensive SEO module, and the ability to customize for non-standard tasks—career portal, pricing calculator, external API integrations.
Project Portfolio
The "Cases" info-block is the foundation of the portfolio section. Property structure:
- Client—text field + logo (file)
- Industry—binding to directory (info-block or Highload-block)
- Task—text field with HTML editor
- Solution—similar, with the ability to insert flowcharts
- Tech Stack—multiple property-directory (React, Python, PostgreSQL, etc.)
- Results—numeric metrics (conversion growth, load time reduction, savings)
- Screenshots—multiple "file" property with Lightbox gallery
Filtering via catalog.smart.filter: by industry, tech stack, service type. Each case is a detailed page with anchor navigation (task → solution → stack → results). The detail page template is custom, with block layout for each section.
Service and Technology Catalog
A two-level info-block. Top level—directions: web development, mobile development, DevOps, data analytics. Within each—specific services with description, technology list, links to relevant cases (property "binding to elements" of the cases info-block).
A technology page contains: description of team competency, number of completed projects on this stack (automatic counting via PHP code in component template), list of cases. This forms internal linking: service → technology → case—the search engine sees expert depth.
Team with Competencies
The "Team" info-block with sections by department. Properties: photo, position, competencies (multiple directory), GitHub/LinkedIn links, brief bio. We display not just a list of people but grouping by project roles—this shows the client who will work on their task.
Career Section with HH.ru Integration
Vacancies are stored in an info-block with fields: position, department, level, description, requirements, conditions, salary range. Synchronization with HeadHunter via API—when a vacancy is created in Bitrix, it automatically publishes to HH.ru via the POST /vacancies method. Feedback: responses from HH.ru are pulled via webhook into Bitrix24 CRM as leads with source "HH.ru".
A Bitrix agent checks vacancy status every hour: if a vacancy is closed on HH.ru, it deactivates the info-block element. The on-site application form—resume upload (PDF, DOC) + cover letter. Files are saved to upload/ and linked to a CRM lead.
Development Cost Calculator
A step-by-step form in JS with server-side validation. Logic:
- Product type (website, mobile app, SaaS platform)
- Functionality—checkboxes with weights (authentication—20 hours, personal account—40, CRM integration—30)
- Design (template, custom, premium)
- Timeline (standard, accelerated with 1.3 coefficient)
Result: cost range and timeframe. Data is sent to CRM as a lead with detailed options. Hourly rate and coefficients are stored in a Highload-block—manager updates them without developer involvement.
Content Marketing via Blog—Primary Lead Generation Channel
For an IT company, the blog is not decoration but a funnel. Technical articles attract target traffic: someone searches "how to optimize PostgreSQL queries," finds your article, sees expertise, navigates to portfolio, submits a request. Let's examine the blog architecture that supports this funnel.
Blog Info-block Structure. Element properties: title, summary (for list and meta description), detailed text, author (binding to Team info-block), category (multiple binding to directory), tags (multiple string), reading time (calculated field—word count / 200), cover image, publication date.
Categorization. Not flat but two-level. Top level: "Development," "DevOps," "Analytics," "Project Management." Within: "React," "Laravel," "Kubernetes," "A/B Testing." Each category is a separate page with its own Title and Description, optimized for search clusters. This provides dozens of additional entry points from search.
SEO Optimization at Module Level. We use Bitrix's built-in SEO module: meta-tag templates for the blog section, friendly URLs via rules in urlrewrite.php, automatic sitemap.xml generation with priorities (fresh articles—priority 0.8, archive—0.5). Breadcrumbs via breadcrumb component with BreadcrumbList microdata. Article markup—Article schema.org with author, date, cover.
Article Series and Related Content. "Series" property—binding to a series element (e.g., "Migration from Monolith to Microservices: Part 1, 2, 3"). In the detail template, we display series navigation. "Related Articles" block—via news.list component with tag matching filter, excluding the current element.
Conversion Elements Within Articles. After each article—a block with relevant CTA. If the article is about PostgreSQL optimization—CTA "Need a database performance audit?" Implementation: "CTA Type" property in the info-block (audit, consultation, project estimate)—the template inserts the corresponding block. Lead magnets: checklists, statement templates—download after entering email, sent to CRM.
Content Plan and Editorial Process. Element statuses: draft → review → revisions → published. Permissions: authors create drafts, editor transitions to "review," editor-in-chief publishes. Workflow via standard info-block business process with notifications at each stage.
Content Analytics. We connect Yandex.Metrica and Google Analytics 4 via GTM. Goals: read article longer than 2 minutes, CTA click, lead magnet download, portfolio navigation from blog. In Bitrix, we create a report via the "Web Analytics" module with grouping by categories—see which topics generate leads, which just traffic.
Distribution. RSS feed via built-in rss.out component—for aggregators and email newsletters. Automatic announcement posting to Telegram channel via bot webhook when element is published (handler for OnAfterIBlockElementUpdate event). Subscriber mailing—subscribe module with category segmentation.
Technical Implementation
| Component | Bitrix Module/Tool | Details |
|---|---|---|
| Portfolio | Info-block + news.list / news.detail |
Custom templates with filtering |
| Blog | Info-block + SEO module | Two-level categories, schema.org |
| Vacancies | Info-block + HH.ru REST API | Sync agent every hour |
| Calculator | JS + Highload-block coefficients | Result → CRM as lead |
| Team | Info-block with department binding | Grouping by project roles |
| Site Search | search module with morphology |
Case, article, service indexing |
Work Stages
| Stage | What We Do | Timeframe |
|---|---|---|
| Analytics and Prototype | Site structure, key page prototypes, blog content plan | 2–3 weeks |
| Design | UI kit, home, portfolio, blog, career page layouts | 2–3 weeks |
| Frontend Development | Template markup, calculator JS, responsiveness | 3–4 weeks |
| Backend and Integrations | Info-blocks, HH.ru integration, CRM, analytics | 3–4 weeks |
| Content and SEO | Portfolio population, first 10 articles, SEO setup | 2–3 weeks |
| Testing and Launch | QA, load testing, deployment | 1–2 weeks |
An IT company website on Bitrix is not just a service catalog but a content platform working to attract clients 24/7 through search traffic and demonstrating real expertise.