Is your feature request related to a problem? Please describe.
Currently, the sitemap declare the same priority value for all content type items from a settings.
Describe the solution you'd like
Many SEO strategy seems to define a different priority depending some item criteria.
We currently don't want to add new field on items to manually define a priority value since it is a sitemap only feature and seems too much for few reallife cases.
We have implemented a customized Sitemap class for article which do the following:
Default priority value comes from setting option priority;
If article is pinned, it try to use setting option pinned_priority, fallback to default if option is not set;
If article is featured it try to use setting option featured_priority, fallback to default if option is not set;
It seems the right way for basic usages. This is only for Article since other content type have no proper and simple criteria to use.
Is your feature request related to a problem? Please describe. Currently, the sitemap declare the same priority value for all content type items from a settings.
Describe the solution you'd like Many SEO strategy seems to define a different priority depending some item criteria.
We currently don't want to add new field on items to manually define a priority value since it is a sitemap only feature and seems too much for few reallife cases.
We have implemented a customized Sitemap class for article which do the following:
It seems the right way for basic usages. This is only for Article since other content type have no proper and simple criteria to use.