Why the sitemap deserves attention
Picture a Tashkent online store on Bitrix: a new batch arrives today, an item is pulled tomorrow, a sale section opens this week. Googlebot or Yandex only learns about this when it reaches the page through internal links. A sitemap shortens that path by listing the addresses you consider important.
It is a hint, not a guarantee of indexing. If the file is full of closed pages, redirects and duplicates, search engines start trusting both the hint and the site a little less.
Where Bitrix builds the file
The built-in generator sits in the admin area under marketing, inside the search optimization settings. Menu names shift slightly between product versions, but the logic is the same: you create a rule, choose which site it covers, name the output file, and pick the sources to read — the file structure and infoblocks.
You can create several rules. That matters when one installation serves multiple sites or language versions, because each can have its own sitemap with its own addresses.
What to include and what to leave out
The sitemap should list pages that can bring customers from search: the home page, services, delivery and payment, contacts, catalog sections, active product cards, articles and news. If you have filter landing pages built around real queries, such as "buy a sofa in Tashkent", and they are open to indexing, add them too.
Everything else should stay out:
- cart, checkout, personal account, and return pages after Click or Payme payments
- internal site search results
- service and test folders such as /include/, /local/, /test/
- inactive products and empty sections
- URLs with sorting or display parameters
- anything blocked in robots.txt or marked noindex
Russian and Uzbek versions on one installation
A common situation in Uzbekistan: the site runs in two languages, but the sitemap was generated only for the default one. Search engines then find the Uzbek pages late and by chance. Create a separate rule for each language version, or confirm that a shared sitemap contains the addresses of both.
While you are there, check the hreflang attributes in the page code. They tell search engines which page is meant for which audience, and a mismatch between the sitemap and hreflang is one of those quiet errors that costs traffic without any visible warning.
Automatic updates and the lastmod date
You can run the generator by hand, but on a live store that rarely lasts: someone remembers the button once a quarter. Set up regular regeneration through Bitrix agents or a server cron job, and after the first runs confirm that the file's modified date really changes.
The lastmod tag needs its own care. It should show when a page changed in substance, not when the sitemap was built. If every URL gets a fresh date every day, search engines stop relying on it. For large catalogs Bitrix splits the output into several files and creates an index file; that index is what you submit to Search Console and Yandex Webmaster.
Checking the result and common mistakes
A full check fits into one evening:
- open the sitemap in a browser: URLs should be absolute, with the right protocol and the main domain
- spot-check several addresses for a 200 response, with no redirects or 404s
- make sure every child file in the index opens too
- add a Sitemap line with the file path to robots.txt
- submit the file in Search Console and Webmaster, then read the error report after a few days
- once a month, compare the number of URLs in the file with the number of pages that should be in search
When the built-in generator is not enough
If part of your pages is produced by custom code, for example filter selections or sections pulled from an external system, a developer can write a dedicated sitemap script. The conditions stay the same: it reads from the same sources as the site and runs on a schedule.
If you are unsure what state your sitemap is in, the markdev team can audit indexing and set the file up as part of SEO optimisation in Uzbekistan. Send us a short description of your site and we will suggest where to start.
FAQ
Where do I generate sitemap.xml in Bitrix?
Open the admin area, go to marketing and then the search optimization settings, where the sitemap generator lives. The finished file usually sits in the site root and opens at yourdomain/sitemap.xml unless you chose another name.
How often should the sitemap be regenerated?
It depends on how often the site changes. A store that adds products daily should regenerate on a schedule. A small brochure site can refresh the file after structural changes.
Why are my Uzbek pages missing from the sitemap?
Usually the generation rule was created only for the default site. Add a separate rule for the Uzbek version, or check that the shared sitemap covers both language versions.
What if Search Console says a sitemap URL is blocked from indexing?
Either remove the URL from the sitemap, or lift the robots.txt or noindex block if the page truly belongs in search. The sitemap and your indexing policy should agree.
Let’s look at your task for free
Leave your contact — in a 15-minute call we’ll show where leads get lost and what to fix first.