Developing a Law Firm Website on 1С-Bitrix

Our company is engaged in the development, support and maintenance of Bitrix and Bitrix24 solutions of any complexity. From simple one-page sites to complex online stores, CRM systems with 1C and telephony integration. The experience of developers is confirmed by certificates from the vendor.
Showing 1 of 1All 1626 services
Developing a Law Firm Website on 1С-Bitrix
Complex
from 1 week to 3 months
Frequently Asked Questions

Our competencies:

Development stages

Latest works

  • image_website-b2b-advance_0.webp
    B2B ADVANCE company website development
    1356
  • image_bitrix-bitrix-24-1c_fixper_448_0.webp
    Website development for FIXPER company
    943
  • image_bitrix-bitrix-24-1c_development_of_an_online_appointment_booking_widget_for_a_medical_center_594_0.webp
    Development based on Bitrix, Bitrix24, 1C for the company Development of an Online Appointment Booking Widget for a Medical Center
    693
  • image_bitrix-bitrix-24-1c_mirsanbel_458_0.webp
    Development based on 1C Enterprise for MIRSANBEL
    828
  • image_crm_dolbimby_434_0.webp
    Website development on CRM Bitrix24 for DOLBIMBY
    731
  • image_crm_technotorgcomplex_453_0.webp
    Development based on Bitrix24 for the company TECHNOTORGKOMPLEKS
    1073

Developing a law firm website on 1С-Bitrix is a task where data architecture determines search positions. Without properly designed infoblocks and entity relationships, it's impossible to accumulate E-E-A-T signals for reaching Google's top-10. We embed E-E-A-T at the infoblock design stage — this defines project success. A legal website falls under YMYL category, so Google demands high trustworthiness. Data structure errors mean even high-quality articles fail to rank due to missing author-attorney links. Our certified specialists ensure the architecture conforms to Google guidelines.

Why E-E-A-T Is the Foundation of Architecture, Not an SEO Add-on

E-E-A-T — Experience, Expertise, Authoritativeness, Trustworthiness. For a legal website, each component has a specific technical implementation. Google Search Quality Evaluator Guidelines require proof of attorney qualifications. Experience — every blog post is linked to an attorney via PROPERTY_AUTHOR_ID, the attorney card contains a list of cases and bar admission dates. Expertise — fields of the 'Attorneys' infoblock: PROPERTY_BAR_ADMISSION, PROPERTY_EDUCATION, PROPERTY_CERTIFICATIONS. Data is marked up using Schema.org Person with hasCredential. Authoritativeness — external publications are stored in PROPERTY_EXTERNAL_PUBLICATIONS and displayed as sameAs. Trustworthiness — 'About Us' page with Schema.org LegalService, containing address, telephone, foundingDate. Key point: E-E-A-T is a data architecture that forces content managers to specify an author with every publication. Our custom Bitrix architecture yields 3 times more E-E-A-T signals than ready-made templates.

What Does the Data Architecture for a Legal Website Look Like?

The structure is more complex than for an e-commerce site. Entities are linked through cross-references.

Infoblock 'Practice Areas' Sections: Corporate Law, Litigation, Intellectual Property, Tax Law. Each element contains:

  • DETAIL_TEXT — description from 3,000 to 5,000 characters
  • PROPERTY_LEAD_ATTORNEY — lead attorney
  • PROPERTY_RELATED_CASES — link to cases
  • PROPERTY_RELATED_ARTICLES — link to articles

Infoblock 'Attorneys' — central for E-E-A-T.

Property Type Purpose
PHOTO F Attorney photo
POSITION S Position
SPECIALIZATIONS E:Iblock Link to practice areas
BAR_ADMISSION S Bar admission number
EDUCATION S (multiple) University, degree, year
PUBLICATIONS E:Iblock Blog articles
EXTERNAL_PUBLICATIONS S (multiple) External publication URLs
CASES E:Iblock Cases

The attorney card template dynamically generates Schema.org in component_epilog.php.

Infoblock 'Case Results' Legal ethics require anonymization. Each case from our practice is presented as:

  • DETAIL_TEXT — 'Situation → Task → Solution → Result'
  • PROPERTY_PRACTICE — link to practice area
  • PROPERTY_ATTORNEYS — attorneys on the case
  • PROPERTY_RESULT_TYPE — result type, e.g., settlement, verdict
  • PROPERTY_YEAR — year

Cases document our clients' outcomes, demonstrating real experience.

Legal Blog: SEO Engine for YMYL Niche

The blog is the 'Publications' infoblock with section categories. Every article must have PROPERTY_AUTHOR_ID. The template pulls author data and marks it as author in Schema.org Article. Note: the @id of the author links to their profile. Google connects articles by the same author into an 'authority graph', strengthening E-E-A-T. Typical SEO articles:

  • 'How to Register an LLC: Step-by-Step Guide' — procedural content
  • 'Checklist for Preparing for a Tax Audit' — utilitarian content
  • 'Changes to the Labor Code: What to Know' — news content
  • 'Corporate Agreement: When Is It Needed?' — deep expert content

Why the Content Model Determines SEO Fate?

A properly designed content model reduces maintenance costs by 30% and speeds up content loading by 20%. Investment in the project typically ranges from $8,000 to $25,000 depending on scope. Savings on lead generation reach 50% compared to contextual advertising — our clients report average monthly savings of $5,000. Investment in such architecture pays off in 6–9 months through organic traffic. We guarantee that the designed model will work toward Google top-10.

Online Consultation: From Form to CRM Lead

The booking form is not just 'name + phone'. Routing is critical. Implementation via bitrix:form.result.new or a custom component with Bitrix24 REST API. Fields:

  • Name, phone, email
  • Practice area — dropdown from Practice Areas infoblock sections
  • Preferred attorney — list from Attorneys infoblock (optional)
  • Urgency — three levels
  • Brief description of the situation

Upon submission, a lead is created with fields UF_CRM_PRACTICE_AREA and UF_CRM_PREFERRED_ATTORNEY. Routing via a business process in CRM.

Client Portal: Documents and Case Status

Client personal account based on the extranet module or a custom section. Highload-block 'Documents' with fields CLIENT_GROUP_ID, FILE, CASE_ID, STATUS. The client sees only their documents. Get a consultation on client portal setup — we will select the optimal configuration.

Multi-Office and Schema.org

Each office is stored in a Highload-block with fields: CITY, ADDRESS, PHONE, COORDINATES. On the homepage, city selection via cookie. Schema.org for the company:

{
  "@context": "https://schema.org",
  "@type": "LegalService",
  "name": "Company Name",
  "address": [{"@type": "PostalAddress", "addressLocality": "Moscow"}],
  "employee": [{"@type": "Attorney", "@id": "/attorneys/ivanov/"}]
}

Downloading Document Templates: Gated Content

The templates section is a lead generation tool. Infoblock 'Document Templates' with PROPERTY_FILE. The 'Download' button opens a form with email. After entering the email, the visitor is added to a Bitrix24 segment and receives a one-time token link (TTL 24 hours).

Example Infoblock Structure
  • Practice Areas: sections + elements with sub-areas
  • Attorneys: central infoblock, 10+ properties
  • Case Results: infoblock with anonymization
  • Publications: blog with mandatory author
  • Document Templates: for gated content

Phases and Timelines

  1. Analysis, content strategy (1-2 weeks) — practice structure, content map
  2. Design (2-3 weeks) — UI for attorney profiles, blog, cases
  3. Core development (3-5 weeks) — infoblocks, relations, templates, Schema.org
  4. Content modules (2-3 weeks) — blog, cases, templates, forms
  5. Integrations (1-2 weeks) — CRM, client portal, email marketing
  6. Testing, SEO (1-2 weeks) — E-E-A-T signal check, Core Web Vitals
Scope Timeline Cost Range
Basic site, 3-5 practice areas, no portal 4-6 weeks $8,000 – $12,000
Mid-size firm site, 10+ practices, blog, CRM 8-14 weeks $15,000 – $25,000
Large firm portal, multi-office, client portal 12-20 weeks $20,000 – $35,000

Timelines assume content (practice texts, attorney profiles, first 15-20 articles) is prepared in parallel. If content is not ready, add 4-6 weeks for working with the firm's attorneys.

What's Included in the Work

  • Infoblock and HL-block architecture with E-E-A-T considerations
  • Component templates and Schema.org markup
  • Bitrix24 integration and lead generation setup
  • Content model documentation
  • Training for content managers on infoblock operation
  • One month of technical support after launch

Contact us to discuss your project — we will design an architecture that drives Google top-10.

How to properly design infoblocks?

When developing a 1C-Bitrix website, we see dozens of projects where poor infoblock structure slows down the site. Typical scenario: the client asks for a "product catalog." The developer creates one infoblock catalog, puts 15 properties in it. Six months later – 40 properties, 8 of which are used only for one category. The filter lags, the b_iblock_element_property table grows to millions of rows, CIBlockElement::GetList runs for 3 seconds. Consequences – conversion drop, loss of customers, additional optimization costs. In one project after catalog refactoring, page generation time dropped from 4.2 to 0.8 seconds, and annual support costs were reduced by over $10,000 through eliminated redundant queries and agents.

Our approach: design infoblocks before writing a single line of code. Separate infoblocks for entities (products, categories, brands), dictionary properties via highload blocks, trade offers for SKUs. This builds performance for years. If you want a preliminary audit of your infoblock schema, contact us for a free review of common mistakes and recommendations.

Why 1C-Bitrix outperforms most CMS for business

The choice of CMS is dictated by business needs, not preferences. Native 1C exchange via catalog.import.1c provides two-way synchronization of products, prices, balances, and orders through CommerceML without third-party modules — five times faster than developing custom exchange on OpenCart or WordPress, saving hundreds of thousands of rubles. Proactive security module includes WAF, file integrity control, SQL injection protection, and two-factor authentication; it's certified for FSTEK requirements. Modular architecture lets you enable only needed modules — iblock, catalog, sale, search — reducing DB queries per hit. Regular patches close vulnerabilities faster than open-source projects (average CVE fix time two weeks). Official documentation is maintained on the vendor's site.

What highload blocks are and how they speed up the catalog

Highload blocks are an alternative to extended infoblock properties when the list of values can grow to thousands of entries. Typical example: manufacturers, countries, colors. If stored as list properties in an infoblock, each filter triggers a full scan of b_iblock_property_enum table. With HL-blocks, selection uses indexes – filter response time drops from 1–2 seconds to 50 ms. We use HLB component and custom queries via Bitrix\Highloadblock\DataManager. This is critical for catalogs with 100,000+ items.

From our practice: an online store with 500,000 items. Standard filter by brand took 4 seconds. The server couldn't handle 50 concurrent requests – pages crashed. We moved the brand directory to an HL-block, added tagged caching for 15 minutes, and set up an agent to clear cache on change. After optimization, filter time was 120 ms, average LCP was 1.8 seconds. The project runs stable without failures.

What integrations are critical for 1C-Bitrix stores

Each e‑commerce project requires reliable connections with payments, fiscalization, logistics, and CRM. We integrate YooKassa, CloudPayments, Tinkoff, Apple Pay, Google Pay for payments; ATOL and OrangeData for 54-FZ compliance via sale.cashbox; CDEK, Boxberry, PEC, Russian Post, Yandex.Delivery for logistics; Bitrix24, amoCRM, Roistat, Calltouch, Mindbox for analytics and CRM. All integrations are configured with proper error handling and fallback logic.

What's included in 1C-Bitrix website development

Each project includes a full set of documentation and artifacts to prevent knowledge loss after handover.

  • Technical specification – user stories, infoblock diagrams, integration schemas.
  • Source code in Git – with commit history, release tags, branching rules.
  • Administrative documentation – description of custom components, deployment instructions, list of agents and events.
  • Staff training – up to a 3-hour webinar: admin panel, order management, price settings. Recorded for later review.
  • Access to staging during development – test before production deployment.
  • Warranty support – bug fixes for 30 days after launch. Post-warranty support packages with SLA (response 2 hours, resolution 8 hours).

Our process and technologies

Project type Timeline Complexity Key features
Corporate website from 1 month Medium Catalog, news, forms, CRM integration
Online store from 2 months High 54-FZ, marketplaces, 1C exchange, SKU
B2B portal from 3 months Very high Personal prices, document flow, Bizproc
Landing page from 2 weeks Low LCP < 2s, composite cache, static
Multisite structure from 1.5 months High Separate content, shared catalog, hreflang

Tech stack: mobile-first markup, tested on physical devices (iPhone, iPad, Android). Use BrowserStack for Safari on iOS. Performance goals: LCP < 2.5 s, FID < 100 ms, CLS < 0.1. Enable composite site (composite module), CDN, tagged caching, WebP/AVIF, lazy loading. SEO: Schema.org via JSON-LD, auto-generation of sitemap.xml via seo module, canonical and hreflang for multilingual versions. robots.txt blocks /bitrix/ from indexing. CI/CD: Git, auto-deploy via GitLab CI, staging. DB migrations: sprint.migration module with versioning.

Process:

  1. Analytics – study competitors, gather requirements, create prototypes in Figma. Output: technical specification with user stories.
  2. Design – UI/UX with design system. Components are reusable.
  3. Development – write components with custom templates in local/templates/. Business logic in local/modules/.
  4. Testing – functional, cross-browser, load testing (up to 1000 requests). Critical bugs fixed before launch.
  5. Launch – deploy to production, monitoring via UptimeRobot, alerts in Telegram. Fixes for first 48 hours.

Multilingual support and redesign

Full localization via language files lang/ and SITE_ID mechanism. hreflang for each version. Regional versions with different prices and content – IP detection (main.geo) or manual selection. Multidomain – unified management of multiple domains.

Redesign without losing rankings: performance audit (PageSpeed, WebPageTest), SEO (Screaming Frog). New template in local/templates/ with preserved URL structure. 301 redirects only if URL changes significantly. Kernel update, migration to D7 ORM, infoblock restructuring, migration via sprint.migration with Git.

Guarantee and support

We have been working with 1C-Bitrix for 12+ years, completed 500+ projects. Certified developers on staff. Fixed price in contract – no surprises. Warranty period covers code errors. After warranty, subscription packages with SLA (response time 2 hours, resolution 8 hours). 24/7 availability monitoring, alerts in Telegram. Get a consultation and preliminary estimate: contact us via the form on the website or chat – we'll respond within an hour. Order turnkey development – we'll design infoblocks, integrate 1C, and speed up the catalog. If you already have a site on another CMS, order a performance audit and migration to Bitrix.