Split a catalogue sitemap and check every index reference
Admin ·
The catalogue needs smaller sitemap files without changing the path each entry represents. Split an existing URL set and check the generated references before deploying.
Split the example after its second entry
Choose Load example and Split sitemap. The count limit is two. Three source entries become two part files and one sitemap-index.xml.
Open sitemap-part-001.xml in the preview. The first URL retains its finish and stock query parameters, its 2026-11-19 date, and its weekly change frequency. The archive URL appears in the second file.
Verify the public child addresses from the index
Choose sitemap-index.xml. Its two loc values point to sitemap-part-001.xml and sitemap-part-002.xml at https://catalog.example.com/.
Change Public sitemap folder URL only when the new folder is the intended deployment location. The index uses the same folder for its part links. Review any directory-scope finding for the page URLs.
Open each XML file in the package
Download the ZIP and check that the named parts open and cover the original URL order. If a file-size limit is reached sooner, the part closes before the next entry.
A saved sitemapindex input produces separate index files with its recorded loc and lastmod values. Submit or deploy those indexes individually as appropriate.
Sitemaps protocol, namespaces, fields and limitsGoogle Search Central, manage sitemaps with an index
Common questions
What if a duplicate has different metadata?
The tool reports the difference and waits for you to choose which entry to keep. This preserves your control over the fields that appear in the output.
Will the generated index have a new lastmod for every part?
Generated child references contain locations. Dates already in the input are preserved within their entries.