-
Notifications
You must be signed in to change notification settings - Fork 882
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
Wrong last modified date time in sitemap index #7163
Comments
Please inform the customer of conversation # 197055 when this conversation has been closed. |
Some further testing: 1.Edit a post within a category. In the example below, I edited the post on July 4th, 2017 2.The category sitemap (in this example the coupon-sitemap) changed to reflect the current last modified date of that updated post 3.The main sitemap did not. In fact, in some testing the coupon-sitemap changed while in others the store-sitemap changed NOTES: More Notes: |
Please inform the customer of conversation # 180345 when this conversation has been closed. |
Please inform the customer of conversation # 209099 when this conversation has been closed. |
Please inform the customer of conversation # 415752 when this conversation has been closed. |
Taxonomy sitemap last mod date is missing in the sitemap on parent taxonomies that only have posts in it's child taxonomies. Result is, in Google's new search console:
Is the above an issue?
The big issue for us is that posts are created via the API via a CRM. (jobPostings) and therefore it's not possible to add posts to the parent taxonomies as a quick fix. Any help fixing this would be super appreciated! Cheers, |
Please inform the customer of conversation # 519931 when this conversation has been closed. |
I can confirm that this issue is still there. Basically also using filter to change the numbers of max entries the problem persist. It is like that yoast cache those values and also on generating new sitemaps that existed before it used that date. |
Having a similar issue
So because an older post is on there then it doesn't update the sitemap date so Google still has the old content in the description So I have to update a post type that is in that taxonomy that is published so that it no longer has an old date It needs to make sure that when a post is changed to draft then (or post_status changes) then it recognises that fact and updates accordingly |
Please inform the customer of conversation # 1037430 when this conversation has been closed. |
Please inform the customer of conversation # 1120544 when this conversation has been closed. |
Related issue: #15801 |
Please inform the customer of conversation # 1144640 when this conversation has been closed. |
Please inform the customer of conversation # 1147078 when this conversation has been closed. |
What did you expect to happen?
That the last modified date in the sitemap would reflect the last modified date of the posts/pages in that specific sitemap (discussed with SEO team, also their expectation of the workings of the sitemap dates). No caching used.
What happened instead?
The dates are not always the same.
How can we reproduce this behavior?
Sitemap:
![xml_sitemap](https://cloud.githubusercontent.com/assets/11910661/26490860/5e08bdb2-420d-11e7-8329-fa6ed083e19f.png)
Post-sitemap8:
![xml_sitemap](https://cloud.githubusercontent.com/assets/11910661/26490882/79256b4a-420d-11e7-908e-452a56ccb3cb.png)
Sitemap:
![xml_sitemap](https://cloud.githubusercontent.com/assets/11910661/26490961/ce1a4b34-420d-11e7-8f6b-34743a450103.png)
Post-sitemap15:
![xml_sitemap](https://cloud.githubusercontent.com/assets/11910661/26490978/e2ba2a46-420d-11e7-8e69-6f9ca54d5b1e.png)
User example with 18.000 posts and sitemap set to max 500 entries:
Sitemap:
![xml_sitemap](https://cloud.githubusercontent.com/assets/11910661/26491149/a5c90e3a-420e-11e7-9fc9-07ab09823bf7.png)
Post-sitemap7:
![xml_sitemap](https://cloud.githubusercontent.com/assets/11910661/26491166/bd7bc568-420e-11e7-8f97-507d7c3f5df5.png)
Technical info
The text was updated successfully, but these errors were encountered: