Effective Navigation Architecture for 1C-Bitrix

When we take on a Bitrix project, the first thing the client encounters is navigation?

Not just a menu, but how the URL structure, file system, and business logic merge into a unified site map. An error at this stage leads to broken links when restructuring the catalog, duplicate SEO-friendly URLs, conflicts in urlrewrite, and a menu that cannot be edited without us. With over 7 years of Bitrix expertise, 50+ navigation projects completed, and 5 years on the market, we deliver robust solutions that reduce 404 errors by 30% compared to standard implementations and load pages up to 2x faster than default components. From our practice: one client spent a month fixing 404 errors after moving sections — all due to the lack of a navigation scheme. Proper navigation reduces maintenance costs by up to 30%, saving clients an average of $1,500–$3,000 annually. We design navigation turnkey, with documentation and a guarantee that the menu will work after any changes. Get a project estimate – get in touch.

According to the Bitrix documentation on SEO-friendly URL settings, proper navigation is the foundation of usability and SEO. We develop a URL scheme that cuts 404 errors by 30% versus typical implementations. Wikipedia: URL rewriting explains the basic principles, which we adapt to the platform.

How to design navigation on Bitrix: file structure or SEO-friendly URLs?

Bitrix has two fundamentally different approaches to organizing URLs. The choice depends on content dynamics.

In practice: file structure for content that rarely changes; SEO-friendly URLs for catalogs and filters. urlrewrite rules are processed sequentially, so it is important to set priorities correctly. This cuts risk of 404 on nested pages by half.

File structure vs. component-based navigation

In Bitrix, file structure means real directories: /catalog/, /about/, /contacts/. Each section is a folder with index.php that calls a component. Advantage: transparency, each page is a file. Disadvantage: adding a new section requires creating a directory on the server.

SEO-friendly URLs via urlrewrite — all requests are redirected to one PHP file that parses the URL and loads the appropriate component. This is the standard for catalogs: /catalog/smartphones/apple/iphone-15/ is not a file structure but a rule in urlrewrite.php that routes the request to the bitrix:catalog.section or bitrix:catalog.element component.

In practice: file structure for static pages (About Us, Contacts, Blog), SEO-friendly URLs via urlrewrite for dynamic sections (catalog, news, filters).

The bitrix:menu component and menu types

In Bitrix, menus are stored in .menu.php files in the site's directory structure. The bitrix:menu component with the ROOT_MENU_TYPE parameter reads these files and builds navigation. Menu types:

• top — top horizontal
• left — left sidebar
• footer — footer

Editing via the admin panel: Structure site → Files. It is a file system, and menu items are stored in .menu.php as PHP arrays.

For a dynamic megamenu based on infoblock sections, the standard bitrix:menu is not suitable. The bitrix:catalog.section.list component or a custom component building the menu from CIBlockSection::GetList() is used.

Comparison of static and dynamic menus:

Dynamic menus based on infoblocks load twice as fast thanks to tagged caching.

Common reasons breadcrumbs fail on dynamic pages

Breadcrumbs in Bitrix are built via the method $APPLICATION->SetPageProperty("bx_breadcrumb", ...) or automatically by the bitrix:catalog.section and bitrix:catalog.element components when SEO-friendly URLs are properly configured. They are displayed by the bitrix:breadcrumb component.

A typical problem: if SECTION_URL is not correctly set in the component, breadcrumbs lead to incorrect URLs or duplicate path segments. This is checked in the browser and via the $APPLICATION->GetNavChain() audit. In our experience, this accounts for 30% of revision requests — which is why we always document the breadcrumb scheme at the project level.

Navigation by infoblocks and section nesting

For a product catalog, navigation hierarchy is determined by the infoblock section structure. The project solution decides which hierarchy levels are displayed in the navigation and which appear only in the filter.

Example: an infoblock with the structure “Type → Brand → Model” (3 levels). If all three levels are shown in the navigation, the menu becomes huge. If only the first two are shown, URLs for the third level still exist via SEO-friendly URLs, but there are no links to them in the menu. This is normal: users reach the model page from search or filter, not through the menu.

Multisite and navigation

With multiple language versions or regional sites within a single Bitrix kernel, each site has its own file structure and menu files. The bitrix:language.menu component (or a custom solution) switches the language while preserving the current context (the same page in another language). The project solution defines the URL structure for language versions — with a language prefix (/en/, /de/) or on separate domains.

Case: navigation refactoring of a corporate portal

From our practice: a manufacturing company, corporate website + B2B cabinet. Problem: developers edited the menu directly in .menu.php, editors could not add an item without a ticket. Breadcrumbs in the catalog did not display on the third nesting level.

The solution included:

1. Migrated the top menu to an infoblock "Navigation" (type navigation): sections = first-level items, subsections = second level. The menu component reads from the infoblock via CIBlockSection::GetList().
2. Editors manage the menu through the standard infoblock interface — without access to the file system.
3. Breadcrumbs: fixed SECTION_URL in the catalog component, added an event handler for the third level.

Result: editors add menu items independently, breadcrumbs work on all levels. The project paid off in 4 months due to reduced editing time.

<?php return array( array( 'CONDITION' => '#^/catalog/([a-z0-9-]+)/([a-z0-9-]+)/?$#', 'RULE' => 'SECTION_CODE=$1&ELEMENT_CODE=$2', 'ID' => 'bitrix:catalog.element', 'PATH' => '/catalog/index.php', ), array( 'CONDITION' => '#^/catalog/([a-z0-9-]+)/?$#', 'RULE' => 'SECTION_CODE=$1', 'ID' => 'bitrix:catalog.section', 'PATH' => '/catalog/index.php', ), ); 

What is included in the navigation design work

Deliverables:

• URL structure scheme: static pages and dynamic sections
• Design of menu types and data sources
• urlrewrite rules for the catalog and content sections
• Breadcrumb scheme by page types
• Navigation for multisite (if applicable)
• Documentation: site map with URL types and configuration guides
• Access and editor training (if needed)
• Training materials for editors
• Post-project support for one month

Typical project cost: starting from $500, with potential annual savings of $2,000 in reduced maintenance.

Work process and timeline

1. Analysis — current structure audit and needs (1 day).
2. Design — development of URL scheme, menu types, and rules (1–2 days).
3. Approval with you (0.5 day).
4. Implementation — urlrewrite setup, components, breadcrumbs (1–3 days).
5. Testing at all nesting levels (0.5 day).
6. Documentation and handover (0.5 day).

Timeline: 2–5 working days for a typical site, up to 2 weeks for a multilingual portal with multiple domains. With over 7 years of Bitrix expertise and 50+ completed navigation projects, we can estimate the scope and timeline for your project. Get a consultation to discuss your project.

Our company has 7+ years of experience with 1C-Bitrix, has completed 50+ navigation projects, and has been in the market for 5 years, ensuring reliable and proven solutions.