Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Yoast Post Sitemap not sorted descending by modified time #13923

Open
2 tasks done
BradFD opened this issue Nov 22, 2019 · 15 comments
Open
2 tasks done

Yoast Post Sitemap not sorted descending by modified time #13923

BradFD opened this issue Nov 22, 2019 · 15 comments

Comments

@BradFD
Copy link

BradFD commented Nov 22, 2019

  • I've read and understood the contribution guidelines.
  • I've searched for any related issues and avoided creating a duplicate issue.

Please give us a description of what happened.

Post sitemaps are sorted oldest modified date first then newest when it should be the reverse with newest modified posts appearing first in the post sitemap. This is with current 12.5 plugin

I have checked multiple sites under my control and they all show this sorting behavior in the post sitemap. See below

Current Sorting of Post Sitemap Example:

  1. Homepage (modified recently)
  2. Old post (ex 2013 modified date)
  3. Old Post (ex 2014 modified date)
    4 Old Post (ex 2015 modified date)
    and so on to: 1000. New Post (modified yesterday)

Please describe what you expected to happen and why.

I expect most recently modified posts to appear first in the sitemap and descend from there.
Expected Sorting of Post Sitemap Example.

  1. Homepage (modified recently)
  2. Newest Post (modified today)
  3. Next Newest modified Post (modified yesterday)
  4. Next Next Newest modified Post (modified 3 days ago)
  5. etc and so on to: 1000. Oldest modified (ex 2014 modified date, years ago)

How can we reproduce this behavior?

  1. Load post sitemap
  2. See homepage as first entry
  3. See oldest modified dates second and then ascending to the most recently modified post appearing last in the sitemap.

Technical info

  • WordPress version: 5.3
  • Yoast SEO version: 12.5
@Djennez
Copy link
Member

Djennez commented Nov 25, 2019

Hi @BradFD , this should not make a difference, SEO-wise. Why would you like to see this?

@BradFD
Copy link
Author

BradFD commented Nov 25, 2019

Sorting by modified date with most recent date first ensures optimized use of crawl budget. Additionally, in the "multiple URL" example shown in the specification document at https://www.sitemaps.org/protocol.html#sitemapXMLExample the example shows entries appearing sorted by the most recent modified date to the oldest modified date. Logically, this is also the way to do.

@Djennez
Copy link
Member

Djennez commented Nov 26, 2019

@jono-alderson I contacted you about this yesterday, would you mind having a look and seeing if this is a valid feature request?

@jonoalderson
Copy link

I don't think that the ordering is particularly important as far as Google is concerned (unless you have an enormous site, crawl budget for XML sitemaps shouldn't be a concern - they're not crawled/consumed/processed in the same way/system as conventional URLS/pages).

However, generally, I think that sorting by last modified date would make sense as a default.

Buuuut, I think this needs some scoping. I'm thinking it through, and there are some grey areas. E.g.,

  • Homepages and 'special pages' (blog home, store home, etc) should always be listed first.
  • In the case of pages, we should order by the order parameter (as/and, the lastmod date of a page is less significant than that of a post).

More generally, If I make a minor alteration to a legacy post, should that catapult it to the top of the list? That feels awkward.

Up for discussion!

@Lofesa
Copy link

Lofesa commented Dec 2, 2019

Hi
My 5 cts. I think is a reasonable feature. When the OP say crawl budget, I think is not about crawl the xml files but to urls from the site, i will say, if you have and old site with 1000 url´s you may expect that not all the url be crawled, so the user may will that the newest url be crawled/indexed first, before the older content.
In other hand, if you modify and older post, changed their content, you may will that these renewed post be crawled before the unchanged older post.
About special pages, all most the blog home is allways the 1st. cause in the functions that put the url in sitemap first is calculated the home and then the post/pages. maybe others stuff like store home need some modifications.
But all this maybe solved with a check in settings and let the user choose wath the order for sitemaps is.

@adidoro
Copy link

adidoro commented Oct 22, 2020

I also think is a good feature. Any update yet?

@saqib-ahmed
Copy link

This is a must-have feature for us. Any update on this?

@mbenedek
Copy link

Google uses the first few elements as the "site links" under the main page search result. So, yes it absolutely matters what order the posts are in. Also, logically, the most recently modified post should be at the top of the list, since it has the most recent content, and should be indexed first, not last.

@jonoalderson
Copy link

Google uses the first few elements as the "site links" under the main page search result. So, yes it absolutely matters what order the posts are in. Also, logically, the most recently modified post should be at the top of the list, since it has the most recent content, and should be indexed first, not last.

There's no relationship between XML sitemaps (their order, or their contents), and the choice/presentation of site links - other than facilitating their discovery.

However, I do still agree that ordering by last modified (with some exceptions / special cases for the homepage, etc) is a better default; I'll make sure this is still on our radar internally.

@shabnam611
Copy link

Please inform the customer of conversation # 1054950 when this conversation has been closed.

@manuelRod
Copy link

@Djennez any news on this feature request?

@WpSEOit
Copy link

WpSEOit commented Dec 25, 2023

we are interested too

@jsayubi
Copy link

jsayubi commented Jan 5, 2024

We need this Feature Please!

@Yvonne-Palanca
Copy link

Please inform the customer of conversation # 1103732 when this conversation has been closed.

@StueberMa
Copy link

+1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests