You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We generally split our sitemaps using a global sitemap index, which loads the site's sub-sitemaps.
This makes it easier to request a re-indexing from search engines, and allows to combine the sitemap of a global site from different sub-site.
Suggested solution(s)
For instance, instead of the existing custom URLs, a separate front-end could generate its own routes-based sitemap, and in Strapi we could request the inclusion of this specific sitemap.
Related issue(s)/PR(s)
N/A
The text was updated successfully, but these errors were encountered:
To implement this I think the plugin will need a big rewrite.
As of now you can only create one sitemap.
To implement this you have to be able to create multiple sitemaps.
Then those sitemaps should be able to be added to sitemap indexes.
When I have the time I'll make the efforts to build this.
Seems like this should just be the default when adding URL Bundles, essentially WordPress does this same sort of thing by default for every custom post type. There is nothing wrong with having the system automatically create a sitemap for each bundle with the main sitemap being the index.
Feature request
Summary
Please add support for the
sitemapindex
.Why is it needed?
We generally split our sitemaps using a global sitemap index, which loads the site's sub-sitemaps.
This makes it easier to request a re-indexing from search engines, and allows to combine the sitemap of a global site from different sub-site.
Suggested solution(s)
For instance, instead of the existing custom URLs, a separate front-end could generate its own routes-based sitemap, and in Strapi we could request the inclusion of this specific sitemap.
Related issue(s)/PR(s)
N/A
The text was updated successfully, but these errors were encountered: