A service website is fundamentally different from an online store: instead of a cart and stock quantities, you need custom fields, online booking, cost calculators, and deep CRM integration. 1C-Bitrix provides built-in tools for such tasks—infoblocks, forms, REST API. But without proper infoblock architecture and caching configuration, the site will lag and forms will lose leads. We develop service websites on 1C-Bitrix turnkey: from infoblock design to Bitrix24 integration. With 50+ projects, certified specialists and a work guarantee. We use tagged caching, Service schema markup, and custom components to ensure fast loading and correct snippets. Our sites load up to 1.7x faster than competitor solutions. Project cost depends on scope, typically ranging from $5,000 to $20,000. Each project starts with an audit of the current infrastructure and a strategy choice: modernization or ground-up development. We'll evaluate your project in 2 days—contact us.
How much does a service website cost?
Adapting Infoblocks for Services
Services are an infoblock of type services. Sections are categories: "Legal Services", "Accounting", "Audit". Elements are specific services: "LLC Registration", "IP Liquidation", "Tax Audit".
Typical element properties:
| Property | Bitrix Type | Purpose |
|---|---|---|
DURATION |
String | Service duration (30 min, 1 hour, 2-3 days) |
PRICE_FROM |
Number | Minimum price for "from ..." display |
PRICE_TO |
Number | Upper price range |
INCLUDED |
HTML/Text | What's included in the service |
SPECIALISTS |
Element link | Link to "Specialists" infoblock |
BRANCHES |
Element link | Link to "Branches" infoblock |
BOOKING_AVAILABLE |
List (Yes/No) | Is online booking available |
RESULT |
HTML/Text | What the client receives |
DOCUMENTS |
File (multiple) | Document templates or examples |
Sections get UF-fields: UF_SECTION_ICON (SVG icon), UF_SECTION_DESCRIPTION (extended description for SEO). Nesting up to two levels: direction → subcategory → service. The catalog.section.list component is configured with DEPTH_LEVEL and a custom template.
Service Card and Schema Markup
The service card uses bitrix:news.detail (not catalog.element—it's overkill). In result_modifier.php we load specialists, similar services (3-4 cards), and portfolio. Everything is cached with tagged caching using the iblock_id_XX tag—this reduces server load by 2-3 times.
Schema markup Service per schema.org/Service: name, description, provider, areaServed, offers. Google Search Console shows status within 2-3 days.
More about Service schema markup
Service schema markup per [schema.org](https://schema.org/Service) includes fields name, description, provider, areaServed, offers. It helps search engines understand it's a service and display rich snippets.Why choose our Bitrix development services?
Setting Up Online Booking and CRM Integration
Two approaches. The built-in form module is fast but inflexible: no service linking, time selection, or calendar integration. A custom form via infoblock is 3 times more flexible: we create a "Bookings" infoblock with fields for service, specialist, date, time, and status. The frontend form is a React component or custom template with AJAX submission via bitrix:main.ajax.
When saving an element, the OnAfterIBlockElementAdd handler creates a lead in Bitrix24 via REST API:
CRest::call('crm.lead.add', [ 'fields' => [ 'TITLE' => 'Booking: ' . $serviceName, 'NAME' => $clientName, 'PHONE' => [['VALUE' => $phone, 'VALUE_TYPE' => 'WORK']], 'SOURCE_ID' => 'WEB', 'UF_CRM_SERVICE_ID' => $serviceId, ] ]); For calendar—integration with Bitrix24 calendar module: calendar.event.add creates an event, calendar.event.get shows free slots. Requires cloud or box subscription.
UTM tags from the URL are passed to the lead via fields UTM_SOURCE, UTM_MEDIUM, UTM_CAMPAIGN. Authorization—OAuth 2.0, webhook, or incoming webhook.
Case Study: Multi-Branch Medical Center
Our client—a medical center with 5 branches and 40 services. We deployed a two-level section structure with UF-fields, linked services to branches, and integrated with 1C. Online booking via a custom infoblock and Bitrix24 calendar reduced booking time by 60%. Service cards include schema markup and tagged caching—loading time decreased by 40%.
Process and What's Included
- Analysis and design (1-2 weeks) — current site audit, service structure, prototypes.
- Backend development (2-4 weeks) — infoblocks, components, CRM integration, forms, calculator.
- Frontend development (2-3 weeks) — responsive layout, interactive components.
- Content and SEO (1-2 weeks) — content entry, META templates, sitemap, robots.txt.
- Testing and launch (1 week) — functional testing, cross-browser.
Included: analytics, prototypes, database design, infoblock and component development, CRM integration, caching setup, schema markup, editor training, access transfer, documentation. Post-launch support—monitoring and revisions.
| Project Scale | Timeline |
|---|---|
| Business card site with 10-15 services, inquiry forms | 4-6 weeks |
| Service catalog with online booking and CRM | 6-10 weeks |
| Multi-branch site with calculator and personal account | 10-16 weeks |
Typical Mistakes and How to Avoid Them
- Services as static pages. No filtering, sorting, or automatic catalog. Solution: migrate to infoblock with 301 redirects.
- Forms without CRM integration. Leads lost in email. Integration takes 2-3 days and pays off in a week.
- Identical META tags. Google sees duplicate content. META templates with service and section name substitution are mandatory.
Why us: over 10 years in the market, 50+ Bitrix projects, certified specialists. Get a consultation for your project—we'll evaluate and propose a solution. Order development today.