When the number of user pages exceeds the limit for a single sitemap, split their URLs across multiple sitemaps rather than putting them all in one file. According to Google’s official documentation, you can list each file’s location in a sitemap index file and submit that index, or submit multiple sitemaps separately. This helps search engines discover pages but does not guarantee that every page will be indexed. The submission methods below focus on Google.
Limits apply to both URL count and uncompressed file size
Google’s documentation specifies two limits for a single sitemap: its uncompressed file size must not exceed 50 MB, and it must contain no more than 50,000 URLs. If either limit is exceeded, the sitemap must be split. Even if you have fewer than 50,000 URLs, you still need to check the file size. If you compress the file, the limit still applies to its uncompressed size.
- Too many URLs: distribute the URLs across multiple sitemaps.
- File too large: split it further, even if the URL count is within the limit.
- After splitting: check every file against both limits, rather than checking just one file.
Use an index file to manage multiple sitemaps
A sitemap lists page URLs; a sitemap index file lists the locations of individual sitemaps. As your site grows, you can add new sitemap locations to the index file and submit it to Google. The official documentation also allows you to submit multiple sitemaps and multiple index files, so using an index file is one way to manage your sitemaps, not the only approach.
For example, if you have 60,000 page URLs to include, you could divide them into two sitemaps containing 30,000 URLs each, then list both in one index file. However, each sitemap must still meet the file size limit. This is only an example of how to divide the URLs, not an official requirement to put exactly 30,000 URLs in each file.
For dynamic sites, plan the groups, then check each group’s URL count and file size
Even if you have not yet exceeded the limits, you can plan how to split your sitemaps in the future. A public technical discussion suggested generating sitemaps by grouping users; this is an implementation suggestion, not an official rule. Because each user may add a different number of pages, the number of users in a group is not enough to tell you whether its sitemap meets the limits. You still need to check that group’s total URL count and file size.
Another public discussion suggested that using an index file from the start, even when there is only one sitemap, makes future expansion easier. This is a maintenance consideration, not evidence of an indexing advantage.
When creating each sitemap, do not overlook the basic format requirements: Google’s documentation requires UTF-8 encoding and fully qualified absolute URLs, and recommends placing sitemaps in the site’s root directory. If you do not submit them through Search Console, remember that a sitemap’s location limits the directories it can cover.
Sitemaps for user pages: perspectives from across the web
Besides submitting them to Google, how else have people suggested helping search engines find the separate sitemaps?
An older technical discussion suggested grouping users to generate multiple sitemaps and listing each file's location in robots.txt. Another article cautioned that doing so could reveal important files and the number of pages on the site to others. The two focus on different concerns: the former addresses making the separate files discoverable, while the latter addresses information disclosure. These suggestions should not be treated as current platform rules.
Will user pages that require a login be indexed if they are included in a sitemap?
You cannot assume they will be indexed on that basis. A public discussion noted that, as a general rule, Google cannot index backend pages that require a username and password to access. Providing a sitemap tells search engines where pages are located; it does not replace their need to access the page content. If user pages also require a login, first check whether search engines can actually access them, rather than merely checking whether their URLs are listed.
After splitting the sitemaps, could URL order or duplicate entries cause search engines to stop reading early?
One technical discussion argued that search engines would not stop reading a sitemap just because of the order of newer and older URLs, or because those URLs had appeared in other sitemaps. The same answer cautioned that files exceeding the size limit or containing XML errors could cause problems when search engines read them. This is a discussion participant's view, not a guarantee that every search engine will read every file completely in all circumstances.
References
- 建立並提交 Sitemap | Google 搜尋中心 | Documentation | Google for Developersdevelopers.google.com — Source used in the article above.
- Should sitemaps list their dynamic data, newest first or oldest first?webmasters.stackexchange.com — Discusses: After splitting the sitemaps, could URL order or duplicate entries cause search engines to stop reading early?
- Re: [問題] Google Search Console搜尋資源設定www.ptt.cc — Discusses: Will user pages that require a login be indexed if they are included in a sitemap?
- Sitemap 是什麼?讓 Google 爬蟲快速了解你的網站!www.awoo.ai · 2022-10-06T09:41:23+00:00 — Source used in the article above.
- Sitemap是什麼?一次搞懂網站地圖提交www.da-vinci.com.tw · 2021-08-17T20:33:00+08:00 — Discusses: Besides submitting them to Google, how else have people suggested helping search engines find the separate sitemaps?
- Sitemaps index submissionwebmasters.stackexchange.com — Source used in the article above.
- Proper sitemap.xml setupwebmasters.stackexchange.com — Discusses: Besides submitting them to Google, how else have people suggested helping search engines find the separate sitemaps?



