Sitemap gzip compression removed, why?

  • Resolved justatest47

    (@justatest47)


    4 years, 10 months ago

    Is there any particular reason why you guys removed gzip compression in sitemaps? Can you please bring it back? Its too useful to remove it… especially for large websites.

    Thanks

Viewing 2 replies - 1 through 2 (of 2 total)
  • Michael Torbert

    (@hallsofmontezuma)

    WordPress Virtuoso

    4 years, 10 months ago

    Hi

    Thank you for your feedback!

    Nothing is off the table, but what we were finding was that compression was rarely, if ever, needed, and caused more problems (doesn’t work well on nginx) that it solved.

    If your sitemap is configured to use indexes, with each sitemap page 1000 or fewer, I suspect you’ll find that you don’t need compression. (https://semperplugins.com/documentation/xml-sitemaps-module/#enable-sitemap-indexes)

    However, as I said, nothing is off the table, and we welcome feedback about how we can improve. Feel free to open a Github issue and be part of the discussion. https://github.com/semperfiwebdesign/all-in-one-seo-pack/issues (requires creating a free Github account)

    Thread Starter justatest47

    (@justatest47)

    4 years, 10 months ago

    I understand that some users do not use or need compression but what about those of us who do need it? I’m not asking for a new function which requires extra work. All Im asking is to bring back a function which was already there, there’s no need for any additional coding and programing. Please bring it back and let users choose whether they want to use compression or not. Compression also reduces stress on the server side when the sitemap is being built. Its just too useful. I really need it.

    Please open a request on Github on my behalf.

    Thank you.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Sitemap gzip compression removed, why?’ is closed to new replies.