Thank you for your plugin. I’ve installed it today for the first time on my staging site to test it.
I’m having a bizarre situation where the sitemap being shown on my site is different depending on whether I’m logged in or logged out.
I make changes in the Settings > XML Sitemap, and save the changes. I’ve also manually excluded some pages with the “Exclude this post from the XML sitemap” option.
I go to “View the current XML sitemap index”, and the changes are correctly shown — the pages that should be excluded are excluded.
But when I go to a Guest profile to check, the changes aren’t implemented. It still shows the pages that are supposed to be excluded.
What I’ve tried:
I’m at my wits end. How can I solve this problem, please?
More information:
Thank you
]]>Hi there ????
Previously, there has been a feature request to add the plugin’s meta box for all registered custom post types instead of only posts, pages and products, which has been marked as resolved. Looking at the code, however, currently the add_posts_metabox()
functions seems to limit the meta box to the above post types.
I could see that a pro version is mentioned in the comments, but wasn’t able to find any further information on this. Is this feature currently in development or will a pro version with this feature be released in the near future?
I then checked for filter hooks that would allow to filter the post types in our theme, but couldn’t find any. Have I been missing something?
Thanks!
]]>It would be great if you could make the meta box optional (exclude page/post). Or user role specific.
Thanks for the plugin.
Best regards
]]>Would be nice, thanks.
]]>Hello, I just installed this plugin. It works very well. However, I have a small issue with the deprecation warning on the admin page. My website is using PHP 8.2
Creation of dynamic property WP_Sitemaps_Config_Admin::$plugin_screen_hook_suffix is deprecated
wp-content/plugins/wp-sitemaps-config/admin/class-wp-sitemaps-config-admin.php:271
]]>
Hi @kybernetikservices !
In this thread the user @eikomadori is reporting, that Google is still complaining about the date/time format.
I get the same error in the search console and I think there is a mistake in the TZD = time zone designator (Z or +hh:mm or -hh:mm)
mentioned in the other thread.
The date is showing like this:2023-02-10T10:46:33+0000
But I think it should be:2023-02-10T10:46:33+00:00
(Please note the missing “:” in the time zone offset.)
Additionally, I think it makes no sense to add a priority to the same static value of 0.5 or a change frequency to “never”.
Looking at the spec the change frequency should only be set to “never” for archived URLs. This could also a SEO problem, because “never” means that the URL will be crawled much less.
Setting the priority to 0.5 for everything is not necessary, because 0.5 is the default value anyway.
According to the spec:
The priority of this URL relative to other URLs on your site. Valid values range from 0.0 to 1.0. This value does not affect how your pages are compared to pages on other sites—it only lets the search engines know which pages you deem most important for the crawlers.
This means setting everything to any static value makes no sense, too. It should be used to prioritize the content on your site.
Is there a public Github repo available to suggest any PRs?
Thanks in advance!
All the best
Torsten
Hi there!
At first: Thank you for this plugin!
Just a small styling issue: I think you need to remove this overflow: hidden
on the wrapper, because otherwise the focus styles on the “Save” button are cropped at the left.
div.wrap div.wpsc_wrapper {
overflow: hidden;
}
Are there any plans to make the priority and change frequency customizable?
All the best
Torsten
Multi-language sitemap without displaying TranslPress
]]>Nice plugin but the User Experience could be improved.
The Gutenberg editor is still a work in progress and to add to its clutter (the XML sitemap meta box) is inappropriate.
I avoid all plugins that unnecessarily clutter the Editor.
Maybe move the function to Settings > XML Sitemap > Posts (tab)
The tab could present an editable list of Excluded Posts
Maybe allow wildcards, e.g. https://example.com/mypost# (exclude all posts starting with ‘mypost’)
regards
]]>Hi,
is there any way to get the “Exclude this post from the XML sitemap” meta box for all registered custom post types instead of only posts and pages? It’s a great feature and would help tremendously.
Thank you!
]]>Thanks for the nice plugin for easily modifying the core WordPress sitemaps. A great improvement on the plugin I used for this before.
Unfortunately the ‘Add last modification date’ option appears to be creating tags with an invalid format for the sitemap schema https://www.sitemaps.org/schemas/sitemap/0.9/sitemap.xsd
The format should be ‘2005-05-10’ or ‘2005-05-10T17:33:30+00:00’ but what it is generating is ‘2005-05-10 17:33:30’ without the ‘T’ before the time part and without the timezone designator. See https://www.w3.org/TR/NOTE-datetime
Google processes the sitemap but reports an error, while Bing doesn’t seem to be processing it at all.
Thanks in advance.
]]>Hi.
Is there any way to exclude specific woocommerce products from the sitemap?
Can’t find the exclude meta box when editing products, which is available for both posts and pages. Would be nice if this worked for products too.
Hi,
Nice plugin. All works well but I get a blank line on sitemap.xml for each excluded post or page. More spcifically several lines of: <url><loc/></url>
Google says:
Sitemap can be read, but has errors
Invalid URL
9 instances
This is not a valid URL. Please correct it and resubmit.
Examples
URL:
Line 3
Parent tag:
url
Tag:
loc
URL:
Cheers
]]>Hi,
Excellent work this plugin, thanks! Saved me from a lot of headaches.
On my provider’s system I get a PHP warning in the error log:
PHP Warning: set_time_limit() has been disabled for security reasons
Web hosting companies do this to prevent you from running very-long-running processes that could impact the availability of other websites sharing the server. Why do you need unbound execution time? Maybe find a way of doing what you need in smaller chunks?
I know it’s just a warning, but is there any way we can avoid filling the logs of my provider’s setup with this?
Thanks in advance,
Rob