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
Sitemaps: Disable Image Sitemaps #7248
Comments
Also requested in 636092-zen |
Once we follow through with #7335 it should be easy enough to do. But for goodness sake please don't do anything before it's merged to avoid conflicts. |
For now, one can use the following filter to disable image sitemaps:
|
Also requested in 932008-zen. |
I need this, any plan to support this? |
@hakamairi That's not currently on our roadmap, but as you can see we've added the "Good For Community" label to this issue; if you were to contribute a patch for this feature, we'd be happy to review it and include it in Jetpack! |
where do i add the filter? thx |
@1lucas You can follow the instructions here to add custom code to your site: |
add_filter( 'jetpack_sitemap_image_skip_post', '__return_true' ); You can add this in functions.php of the active theme |
Another request to disable image sitemaps in 17122534-hc Update: The code snippets seems to be working now. |
Requested here: 15687925-hc |
Also supporting having a checkbox for disabling this. We have ~140,000 images and the sitemap has caused Google Bot to crawl all the (default) attachement pages that we don't actually use. It drained resources and went on undetected for a while. |
Requested here as well: 29339388-hc |
This is still a case. |
Another case on the forums: https://wordpress.org/support/topic/why-does-jetpack-assume-we-want-an-image-sitemap-xml-file/?view=all |
In the sitemaps module there's currently no way to disable any specific instances of the sitemaps, specifically the image sitemap.
Checking the developer options I'm seeing filters for excluding specific images but not a way to disable the full image sitemap.
requested in 3216712-t
The text was updated successfully, but these errors were encountered: