A single Bitrix installation can run multiple sites. If the retail store's sitemap contains URLs from the wholesale catalog, first find out which data and which site are selected in the generation settings. Replacing the domain with a text search in the finished XML does not fix the source of the problem: the next run will create the same URLs again.
A sitemap is an XML file listing site URLs for search engines. It can link to several child files containing different groups of pages.
This article covers «1С-Битрикс: Управление сайтом» and the standard sitemap settings. If a custom script or Marketplace module creates the sitemap, you need to follow its rules. The same sitemap.xml filename does not mean the generation mechanism is the same.
How to make sure you have the right file open
Save the full sitemap URL: protocol, domain, folder, and filename. Open it without signing in to the admin panel. If the main file contains a list of child sitemaps, open the specific child XML where you found the other site's products. Record both URLs and the specific loc entry.
Check that this is a public file for the current site, not a downloaded copy or an old file on a CDN. The date shown in the browser does not always indicate when the file was generated. Ask the administrator to confirm which settings created the file and where it is saved. Until the source is identified, mark it as unknown.
If the issue concerns the availability of part of the sitemap, use the child sitemap check. Protocol and www differences are covered in the guide to aligning sitemap URLs.
Open several suspicious URLs. A product from another site may exist in the shared database but not be intended for this storefront. Note separately an incorrect domain, an incorrect product selection, and an unavailable page. These are different errors and cannot be fixed by renaming the file.
Where to check the sites and generation settings
Go to Settings → Product settings → Sites → Site list. Record the site IDs, domains, and root folders. The Bitrix course on multisite setups describes how site settings relate to a shared installation. An ID such as s1 is an internal designation, not a public domain.
Then go to Marketing → Search engine optimization → sitemap.xml settings. Open the settings for the specific site and check the sitemap URL. The standard site and tab selection procedure is described in the Bitrix lesson on sitemap generation.
On the “Infoblocks” tab, compare the selected data with the purpose of the storefront. On the “Files” tab, check the selected folders and masks. Fixing only the infoblock list will not help if the wholesale catalog's custom pages are included in the sitemap as physical files.
A training example with retail and wholesale sites
Imagine two sites: retail retail.example.com and wholesale wholesale.example.com. This is a fictional example. The “Retail products” infoblock should be included in the first site's sitemap, and “Wholesale sets” in the second site's sitemap. Both sites are running in the installation, but the retail sitemap settings include both infoblocks.
The reference table looks like this:
| Object | Reference URL | Retail sitemap | Wholesale sitemap |
|---|---|---|---|
| SKU RET-10 | https://retail.example.com/product/ret-10/ | Included | Excluded |
| SKU WHO-50 | https://wholesale.example.com/catalog/pack-50/ | Excluded | Included |
| Retail delivery | https://retail.example.com/delivery/ | Included | Excluded |
In a real project, the rules may differ: a shared product is sometimes published on both storefronts. In that case, each sitemap needs an accessible primary URL for the relevant site. The table does not prohibit a shared catalog; it helps make its use explicit.
After the fix, check both an included entry and an excluded one. The absence of WHO-50 from the retail sitemap is useful only if RET-10 is still there. Otherwise, you might accidentally “fix” the problem by removing the entire product XML.
What to check in the infoblock and URL templates
Open the selected infoblock's settings and check which sites it is assigned to. Then compare its public URL templates with the actual storefront URLs. The structure of the LIST_PAGE_URL, SECTION_PAGE_URL, and DETAIL_PAGE_URL fields is described in Bitrix help.
If an infoblock is linked to two sites, the developer should check how its links are generated in each context. The public listing may use one component template, while the sitemap generator may get URLs from a different source. A correct product page in the browser does not confirm that the generator got the right domain and folder.
Do not unassign the infoblock from the second site just to fix the sitemap until you know why it is used there. This may remove products from an active storefront. Often, the fix is to change the contents of the specific sitemap or align how its links are generated while keeping the shared database that is needed.
If the sitemap contains the wrong domain but the right products, treat this as a separate URL error. If the domain is right but the products are wrong, investigate the selection. Record these as two separate observations so the developer does not have to guess which layer to fix.
How to check the new sitemap after generation
Save the current reference entries, change the agreed settings, and run generation using the standard tool. When it is complete, reopen the main and child XML files at their public URLs. Check that the main file links to the expected parts, rather than to an old file with the same purpose that was left behind.
Find the full URLs for products RET-10 and WHO-50 from the reference table. The SKU is not necessarily present in the URL, so searching by SKU alone is not enough. Then directly open several new loc URLs and check the correct domain, expected product page, and a valid server response. XML can be syntactically correct yet contain broken pages, so checking the format does not replace checking the URLs.
Compare the sitemaps for both sites. The retail fix should not remove agreed wholesale pages. If they share a files folder, pay particular attention to the save paths and child XML filenames: one run should not unexpectedly overwrite the result of another.
How to prevent the problem from recurring
Record who creates new infoblocks and changes their site assignments. Include a sitemap contents check in this process. A new catalog temporarily assigned to both storefronts during setup may remain in the generated sitemap after the work is complete.
If a regular sitemap update mechanism is already configured, ask the developer to describe it. Checking one manual run does not confirm that the next automatic run will use the same rules. After the next standard update, check the two reference entries and the public files again.
If the automatic update mechanism is unknown, do not declare the problem permanently resolved. Record that manual generation has been checked and that the next run is still pending. This makes it easier to catch a separate script that creates the sitemap using the old logic.
How to submit the task and accept the fix
Include the site IDs, URLs of both sitemaps, IDs of the required infoblocks, and the product inclusion table in the task. Expected result: each sitemap contains the agreed set of accessible primary URLs for its storefront, and the next run preserves this rule.
A technical audit can help check published pages; related practical guides are available in the blog. Submit the new sitemap to Google or Yandex after checking the file. The presence of a URL in the XML does not confirm its indexing: the sitemap provides the URL, while a search engine's decision is assessed using separate, current data.