Renaming a section in the menu and changing its symbolic code are different changes. A symbolic code is a short identifier such as accessories, which may be used in the section’s URL. Changing the visible text may not change URLs. A new code can change the paths of the section and its products if they use that code. Before saving, determine which URLs actually depend on this field.
This guide applies to «1С-Битрикс: Управление сайтом». Custom templates, complex components, and Marketplace solutions may build links differently. So the right approach starts with a short list of real URLs, not with a bulk recreation of rules.
How to determine which links will change
Open the relevant section in the admin panel and note its symbolic code. Then record the section’s public URL and several product URLs from its list. Add a nested section and a product that belongs to two sections, if such cases exist.
The developer checks the infoblock URL templates: SECTION_PAGE_URL for a section and DETAIL_PAGE_URL for an element. Their purpose is described in Bitrix help on infoblock fields. Also check the catalog component’s parameters: it may use its own templates instead of the expected infoblock values.
If a link uses the section path, changing one code may affect child pages. If a product URL is built only from the element code or ID, its path may stay the same. You cannot assume in advance that renaming will change the entire catalog or have no effect on products at all. This depends on the configuration of the specific site and must be checked.
Example: accessories becomes spare-parts
Imagine a catalog where section /catalog/accessories/ is being renamed to /catalog/spare-parts/. A mounting bracket has the old URL /catalog/accessories/mount-10/. This is an illustrative example, not a client migration case study.
Record the mappings before making the change:
| Object | Old URL | Expected new URL |
|---|---|---|
| Section | /catalog/accessories/ | /catalog/spare-parts/ |
| Mounting bracket | /catalog/accessories/mount-10/ | /catalog/spare-parts/mount-10/ |
| Child section | /catalog/accessories/steel/ | /catalog/spare-parts/steel/ |
After changing the code, links in lists should point to the new URLs, the new pages should open the correct objects, and the old URLs should work according to the agreed redirect rules. If the new product URL shows a section instead of a product page, link generation and request handling are out of sync.
A separate test product whose URL does not include the section should keep its existing URL. This check guards against an overly broad change in which the developer redirects the entire catalog using one unverified template.
What to check in SEO-friendly URLs and urlrewrite
In SEO-friendly URL mode, the catalog component parses virtual paths. The URL handling system routes the request to a physical PHP file. The general mechanism is described in Bitrix documentation on URL handling. These two layers have different responsibilities: opening the correct handler and determining the specific section or product.
The developer should check SEF_FOLDER, the component templates, and the catalog rule. After changing only the symbolic code within an existing folder, the catalog may still be handled by the same general rule. Recreating urlrewrite is not a required response to every code change: first identify which setting no longer matches the route.
Recreating rules is especially worth considering if the physical entry page or the SEO-friendly URL folder was changed through a file upload. Save the current file and check custom rules first. The official documentation distinguishes rules that components recreate automatically from custom rules without a populated ID.
New path handling does not automatically create a redirect from the old URL. That is a separate part of the task. Do not treat “SEO-friendly URLs rebuilt” as confirmation that old links from search results and ads have been preserved.
How to prepare redirects from old URLs
For each URL that changes, identify the corresponding new page. Usually, this is the same section or product, not the site’s home page. If some products have been removed, agree separately on how they should behave: a relevant replacement, an out-of-stock message, or another intended response.
The developer chooses where to implement redirects based on the current server and CMS configuration. The site owner needs a specific mapping of old and new URLs, not a generic .htaccess snippet that has not been checked against the environment. A rule suitable for one Apache catalog cannot be transferred to a different configuration without review.
For nested sections, check the boundaries of the redirect pattern. The substitution should preserve the necessary part of the path and avoid affecting a neighboring section with a similar name. Also test an old URL with an advertising campaign parameter: it should reach the same intended product page, not a routing error.
Where to look for remaining old links
After the change, check the menu, breadcrumbs, product lists, recommendation blocks, and internal search. Links from each location should point to the chosen canonical URL. Redirecting the old URL does not make outdated internal links a satisfactory final result.
If breadcrumbs are marked up for search engines, also check the URLs in their structured data. When switching CMS, you will need a catalog migration table rather than a single code change.
Check the sitemap and product canonicals. If the URLs have actually changed, these should consistently point to the new canonical URLs. The sitemap may build URLs from the infoblock template while the public list uses component parameters; that is why these sources should be checked separately.
Check pages while logged out and after clearing the applicable cache. If the menu has updated but recommendations still use the old path, find the cache for the relevant component. Do not change the symbolic code again just to remove an old link: that will not fix the source of the stale data.
What to check in catalog feeds
If product feeds, price lists, or partner integrations use the old URLs, add those sources to the checklist. The menu may already show the new paths while the next export file still provides the old ones. Save one URL from each active feed and compare it with the migration table. Do not check for integrations that do not exist: first find out which sources are actually in use on your site.
How to approve the section change
In the task, specify the actual section ID, the old and new codes, test products, the URL mapping, and the rules for old URLs. Ask the developer to show which templates were changed and which were left as they were. Record the release date so you can later compare it with a search engine crawl.
Acceptance criteria for the example: the new section opens; the mounting bracket displays the same product page; the child section works; old URLs lead to the agreed new pages; links, canonicals, and the sitemap are updated; and the test product outside the changed path keeps its URL.
Use a technical website audit to check published pages; related guides are collected in the blog. Changes in Google or Yandex indexes should be checked later using their latest data. The immediate development result is working URLs and reproducible redirects, not a promise to preserve every search ranking after a rename.