Why sitemap structure matters on large sites
One sitemap.xml works fine for a small site. But if you run a marketplace with thousands of product cards, or a listings site in the spirit of OLX, a single file turns into a pile. Categories, products, articles and service pages are mixed together, and you cannot tell from that file which part of the site search engines are reluctant to index.
There is also a formal reason. The sitemap protocol limits the number of URLs and the size of each file, so a big site has to be split anyway. The real question is whether you split it randomly or deliberately.
The sitemap index file as a table of contents
The foundation is the index file. It does not list pages itself. It points to child sitemaps: one for categories, one for products, one for the blog. You reference the index in robots.txt and submit it to Google Search Console and Yandex Webmaster. Search engines then read every child file on their own, so you do not need to submit each one by hand.
One rule to remember: an index cannot point to another index, so nesting goes one level deep only. Each entry can carry a lastmod date, but update it only when the contents of that child file actually changed. Otherwise the date loses meaning and crawlers stop trusting it.
Ways to split a sitemap
Splitting is not only about limits. It is mostly about analysis. These are the common schemes:
- by page type: core and service pages, categories, brands, products, articles
- by catalog section: electronics, furniture, clothing
- by language: separate sets for the Russian and Uzbek versions
- by region, if you have city or district pages
- by date added, for news and listings
Splitting as a diagnostic tool
For most sites the most useful scheme is splitting by page type. In the Search Console indexing report you can filter by a specific sitemap. If nearly all categories are indexed but only a small share of products are, the problem sits in the product template: thin descriptions, duplicates, slow loading or identical text on similar items.
On a bilingual site it makes sense to keep Uzbek pages in their own files. They are often added later and get fewer links, so you want to watch their indexing separately from the Russian section. That way you notice at once when the Russian part is healthy and the Uzbek part is stuck.
File naming and stable URLs
Use readable names: sitemap-products-1.xml, sitemap-blog.xml, sitemap-uz-services.xml. Numbers are needed only when one page type does not fit into a single file. Avoid putting a generation date or random hash in the name. Crawlers would see a brand-new file every time, and the history in your dashboards would break.
Distribute products across parts in a stable way too. If you split by ID or by date added, a product will not hop between files on every rebuild, and new items will always land in the last file, which is easy to monitor.
What to keep out and common mistakes
Even a well-planned structure fails if the wrong URLs end up inside. These problems come up again and again:
- filter combinations, sorting, pagination and internal search results included in the map
- discontinued products that will not come back still listed
- the same URLs repeated across several files
- the index and its child sitemaps submitted separately in the panels
- child sitemaps hosted on another domain without verified ownership
How to check the result
After changing the structure, confirm that every file in the index opens, that URLs are not duplicated, and that the total count is close to the number of pages that should be searchable. A big gap means something extra slipped in, or a whole section is missing.
A good sitemap structure lets you see the site in parts: spend the time once, and each later indexing review takes minutes instead of hours. If you want to set this up on your own site, markdev handles SEO optimisation in Uzbekistan, including the technical side. Tell us about your project and we will talk it through.
FAQ
Do I need a sitemap index on a small website?
Not necessarily. One sitemap.xml is enough for a small site. An index becomes useful when you have many pages or want indexing statistics by page type.
How should I split an online store sitemap?
Usually by page type: service pages, categories, brands, products and blog. If there are very many products, split them into numbered parts by ID or date added.
Where do I submit the index file?
Reference it in robots.txt and add it to Google Search Console and Yandex Webmaster. There is no need to submit child sitemaps separately.
Should Russian and Uzbek versions have separate sitemaps?
On a bilingual site, yes. It lets you track how well Uzbek pages are indexed, since they often appear later than the Russian ones.
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.