Development of a website for a consulting company using 1C-Bitrix

Consulting Company Website Development on 1C-Bitrix

Consulting company sells expertise. Client cannot touch product, doesn't see warehouse — evaluates professionalism by how company presents information. Website on 1C-Bitrix becomes central platform: service catalog, expert content, consultant profiles, cases with measurable results, and closed cabinet for current clients. All managed from single admin panel without developer involvement for each publication.

Service Catalog by Directions

Services structured in "Services" info block with first-level sections by directions: strategic consulting, financial consulting, HR consulting, IT consulting. Inside each direction — service elements with detailed description.

Element properties:

• Brief Description — for catalog card (PREVIEW_TEXT)
• Detailed Description — expanded service page (DETAIL_TEXT in HTML)
• Icon — SVG file for visual distinction in catalog
• Linked Cases — multiple binding to "Cases" info block
• Expert Binding — binding to "Consultants" info block
• CTA Text — string property for individual call-to-action button

Section page displayed via bitrix:catalog.section component with card template. Detail page — bitrix:news.detail with sidebar: linked cases, expert profiles of direction, consultation booking form.

Consultant Profiles

"Consultants" info block stores expert information:

• Photo, position, specialization
• Biography and professional experience (DETAIL_TEXT)
• Certifications — multiple String property
• Publications — binding to "Articles" info block
• Presentations — multiple File property (PDF presentations)

On consultant detail page articles auto-pull from content hub and cases where they listed as participant. Forms complete expert profile working on E-E-A-T.

Cases with Results

"Cases" info block structured for demonstrable measured results:

• Client — company name (with consent), industry
• Task — initial situation description
• Solution — work description
• Result — numeric metrics: revenue growth (%), cost reduction, ROI timeline
• Direction — binding to service catalog section
• Consultant — binding to "Consultants"
• Project Duration — numeric in months

Detail page template includes CaseStudy micromarkup and key metrics block displayed as visual cards with large numbers.

Deep-Dive: Content Marketing and E-E-A-T as Consulting Foundation

For consulting company, organic traffic — main client acquisition channel long-term. Context ads give leads but click cost in "strategic consulting" or "financial audit" hundreds of rubles. Content marketing with E-E-A-T focus reduces paid traffic dependency and builds reputation.

Content Hub: Info Block Architecture

Content hub — unified section combining articles, research, checklists, webinar recordings. Technically "Content" info block with property classification:

• Content Type — list: article, research, checklist, webinar recording, infographic
• Direction — service catalog section binding
• Author — "Consultants" binding (critical for E-E-A-T)
• Publication Date — chronological sort and sitemap
• Level — list: basic, advanced, expert (audience segmentation)
• Related Materials — multiple same-block element binding

Component bitrix:news.list displays content hub with filtering by type, direction, level. AJAX filtering allows parameter combination without reload. URL formed via friendly URLs: /insights/strategy/, /insights/finance/, /insights/type/research/.

Authorship and Expert Signals

Google evaluates E-E-A-T at page level. Each article must explicitly indicate author with expertise confirmation. In bitrix:news.detail template for content hub displays author block:

• Photo and name linked to consultant profile
• Position and specialization
• Publication count (calculated via CIBlockElement::GetList with author filter)
• Professional profile links (LinkedIn, industry associations)

Article micromarkup includes author with nested Person, datePublished, dateModified, publisher. Lets Google correctly attribute content.

Cross-Linking and Content Clusters

Each consulting direction forms content cluster:

• Pillar Page — direction detail from catalog (2000–3000 words)
• Cluster Pages — content hub articles bound to direction
• Links — auto cross-linking via "Related Materials" property and "Similar Articles" widget in template

"Similar Articles" widget works via bitrix:news.list component with direction match filter excluding current element (!ID). Outputs 3 materials sorted by date.

Content Updates and Freshness Signals

Search engines value content currency. Info block uses two date properties:

• DATE_CREATE — first publication date
• TIMESTAMP_X — last update date

Template outputs both: "Published: 15.01.2025 | Updated: 10.03.2025". On article update dateModified in micromarkup changes auto, signaling search engines.

For system updates, Bitrix agent runs weekly: report of articles over 6 months without updates, sent to editor email.

Conversion Through Content

Each article contains contextual CTA blocks. Stored as separate "CTA-Blocks" info block elements with direction binding. Inserted in article template after second <h2> via PHP DETAIL_TEXT processing:

• HTML split by <h2> tags via DOMDocument
• CTA-block HTML fragment inserted after second heading
• Reassembled to string

Lets managers change CTA-blocks centrally without editing each article.

Consultation Booking

Form via "Web Forms" module with fields: name, phone, email, direction selection (synced with catalog service sections), preferred time. Form submission creates lead in Bitrix24 CRM via REST API, assigning responsible manager by selected direction via business process.

Closed Client Section

For current clients, authorized section via standard main module (bitrix:system.auth.form component). Functionality:

• Documents — info block with user group binding; file access regulated by section read rights
• Reports — internal system exports, uploaded by manager in admin
• Notifications — mail events module for client notification on new documents

Access separated via Bitrix user groups: each client assigned group, info block sections have read rights for specific groups.

Implementation Stages