Title: Cache control?
Last modified: May 1, 2023

---

# Cache control?

 *  Resolved [robertoarias](https://wordpress.org/support/users/robertoarias/)
 * (@robertoarias)
 * [3 years, 1 month ago](https://wordpress.org/support/topic/cache-control-5/)
 * I work for a fairly large site and with many years, it turns out that every time
   Google, Microsoft or any search engine downloads the xml, the processing goes
   up a lot and the number of requests is enormous.
 * Since we have posts from many years ago, I would like to know how I can generate
   a cache of the xml from previous years, since I don’t see the point that every
   time a 2016 file is requested, it is generated from 0.
 * Hopefully someone can help me.

Viewing 1 replies (of 1 total)

 *  [saurabhdhariwal01](https://wordpress.org/support/users/saurabhdhariwal01/)
 * (@saurabhdhariwal01)
 * [3 years, 1 month ago](https://wordpress.org/support/topic/cache-control-5/#post-16713875)
 * [@robertoarias](https://wordpress.org/support/users/robertoarias/) , thankyou
   for contacting us!!
 * We are not managing the caching of older xml.

Viewing 1 replies (of 1 total)

The topic ‘Cache control?’ is closed to new replies.

 * ![](https://ps.w.org/google-sitemap-generator/assets/icon-256x256.png?rev=2713572)
 * [XML Sitemap Generator for Google](https://wordpress.org/plugins/google-sitemap-generator/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/google-sitemap-generator/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/google-sitemap-generator/)
 * [Active Topics](https://wordpress.org/support/plugin/google-sitemap-generator/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/google-sitemap-generator/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/google-sitemap-generator/reviews/)

 * 1 reply
 * 2 participants
 * Last reply from: [saurabhdhariwal01](https://wordpress.org/support/users/saurabhdhariwal01/)
 * Last activity: [3 years, 1 month ago](https://wordpress.org/support/topic/cache-control-5/#post-16713875)
 * Status: resolved