Support for changefreq and priority according to sitemaps.org specification

[Verkasha]

Hey everyone,
I noticed that changefreq and priority were removed in PR #545, with the reasoning that Google doesn't use them anymore. However, I think this reasoning misses an important point.

The purpose of a sitemap generator should be to follow the official sitemap protocol — as defined on sitemaps.org. According to the specification, both changefreq and priority are still valid and supported elements.

Whether or not Google chooses to use these fields is a separate concern. There are other search engines out there (Bing, Yandex, etc.) that may still use this metadata. Removing these elements outright reduces the utility of the generated sitemap for users who target a broader range of search engines.

In short:

• The generator should follow the spec.
• It’s up to search engines to decide what parts of the spec they care about.
• Users should have the choice to include these fields if they want.

I’d strongly recommend reconsidering the removal of these fields — or at the very least, making their inclusion optional.

[lukas-pierce]

Added pull request #572

[Verkasha]

Looks like
<priority>{{ number_format($tag->priority,1) }}</priority>
was missed in the commit.

[lukas-pierce]

Ok I will fix it as soon as I can and also fix the tests