change sitemap.xml?page=1 to sitemap1.xml

The MR is only related to test cases.
Attaching patch as per 4.1.7 for change in pattern from sitemap.xml?page=1 to sitemap-1.xml right now its based on delta value and not on config.

The proposed solution should not replace the current routing. It should be an option.

In 💬 Changing Simple XML Sitemap Pagination Active @sparsh.sinha claims Google does not like our pagination either which is strange as we built this module to Google's standards. Can anyone confirm this? None of my sites are big enough for pagination to make sense, so I need your feedback.

@walkingdexter
If Google also flags this as erroneous, we can change this issue's category to bug and indeed overwrite the current behavior.

Another user has said in Slack today that "Google Search Console reports an indexing issue because it does not support nested sitemap indexes". I've directed them towards this issue. Perhaps Google has recently changed behaviour; hopefully someone with a GSC account and a site big enough to hit this is able to provide more detail.

Based on our customer's response, here’s what they are encountering in Google Search Console:

I’ve included a breakdown of triaging the issue in Google Search Console for the reference plus an explanation on why we think it's the pagination that’s causing all the missing page issues..

Issue: Nested Indexing Error in Google Search Console

Submitting sitemap works… at first but then when you inspect further

You can see that each sitemap.xml?page=X has an error. When we look at the error, we have a nested indexing error.

This happens because Google expects the sitemap index to reference separate sitemap files (.xml), but the current setup is dynamically paginating the index using query parameters (?page=1). When this happens pages can be missed.

Could someone review this and confirm if adjustments in Google Search Console are required? Or is changing the pagination URL the only viable solution?

Based on this google documentation

https://developers.google.com/search/docs/crawling-indexing/sitemaps/lar...

https://www.example.com/sitemap1.xml.gz
2024-08-15


https://www.example.com/sitemap2.xml.gz
2022-06-05

Google example has different sitemap name rather than sitemap parameter on the back of the url. I also got the same issue with massive sitemap over 15k url. it wont recognise if we are using pagination parameter. So my current workaround only increase the limit of the url generated for 1 sitemap page.