Hi,
In the Excluded categories part of the settings, for some reason, the list of categories is shown 4 times in the following fashion:
Everything is in the title ??
I guess the root cause is visible when using the debug feature, error in logs:
[15-Dec-2023 10:38:55 UTC] PHP Fatal error: Uncaught TypeError: Unsupported operand types: int * string in /home/x/uat.closdebreuilly.com/wp-content/plugins/google-sitemap-generator/class-googlesitemapgeneratorstandardbuilder.php:702
Stack trace: 0 /home/x/uat.closdebreuilly.com/wp-content/plugins/google-sitemap-generator/class-googlesitemapgeneratorstandardbuilder.php(53): GoogleSitemapGeneratorStandardBuilder->build_product_categories() 1 /home/x/uat.closdebreuilly.com/wp-includes/class-wp-hook.php(324): GoogleSitemapGeneratorStandardBuilder->content() 2 /home/x/uat.closdebreuilly.com/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters() 3
….
/home/x/uat.closdebreuilly.com/wp-admin/options-general.php(10): require_once(‘/home/x/…’) 13 {main}
thrown in /home/x/uat.closdebreuilly.com/wp-content/plugins/google-sitemap-generator/class-googlesitemapgeneratorstandardbuilder.php on line 702
I initially thought this was related to the link per page settings: config was not modified for a long time. I attempted to deactivate/reactivate, save config: not much effect.
Code seems a bit paranoid about the fact that links_page is an integer, maybe with good reason ?? yet it is surprisingly the lhs that is not an integer:
$offset = ( --$offset ) * $links_per_page;
error_log( ‘offset ‘ . $offset ) reveals the value of $offset to be… ‘-sitemap’ which is likely not an offset!
PS: there was at the same time an upgrade of WooCommerce (to 8.4.0). Product categories are messed up (I have two “unclassified” categories, one translated to french, the site native locale, and one in english) but this was the case before the upgrade. Removing the “product categories” from sitemap generation had sitemap generation working again…
]]>I’ve been using this plugin with my brand new site that isn’t ranking in the search engines yet, and I recently made major changes to my site structure and want to start over with an entirely new sitemap using this great plugin.
Since my site is brand new and doesn’t rank in search engines yet I am not worried about losing search engine rankings.
I tried deactivating, then deleting, then reinstalling, then reactivating this plugin, but it remembered all my sitemap.xml info. How can I delete all my old sitemap.xml info and tell this plugin to start over and rebuild the sitemap.xml files starting from nothing?
Thanks in advance!
]]>Hi,
We are using your Google XML Sitemap Generator plugin here to manage sitemaps.
but need help about something.
we have a custom post type with this ag_county_post
slug, that we manage those archive pages to have better URLS,
but we don’t have any option in your plugin to use custom slug (rewrite slug) so I excluded it.
and made a custom one here: https://www.agespace.org/counties.xml
is there maybe some filters or actions to change and use custom slug on sitemaps generating from your plugin?
something that allow change this:
https://www.agespace.org/ag_county_post/worcestershire
to this:
https://www.agespace.org/services/home-care/worcestershire
Hello
I am getting following error when creating Google News sitemap using your plugin.
An invalid date was found. Please fix the date or formatting before resubmitting.
You can see it in screenshot below
Upon looking into the issue, turns out your plugin is generating timezone part in wrong format
Example of what is generated by plugin
<news:publication_date>2022-06-05T19:21:07+0000</news:publication_date>
What it should look like to comply with Google
<news:publication_date>2022-06-05T19:21:07+00:00</news:publication_date>
The difference is in the last part in the date
From
+0000
To +00:00
“:” is missing. Can you please fix this?
]]>How to add terms of taxonomies to the sitemap that do not contain linked posts
]]>Hello!
I found your plugin after replacing another one (dismissed), which caused my sitemaps not being indexed and in the meantime I lose 25 positions on Google :(.
I installed your plugin and loaded sitemaps on Google Search Console, and I saw there is 1 error related to some media terms.
I have a plugin called “Enhanced Media Library” which categorizes images in Library in categories, it is for admin use only, therefore I don’t not need them to be indexed.
I use Seo Yoast and I excluded indexation for this taxonomy.
In your “Sitemaps defaults” window this taxonomy is not listed,
what I have to do to delete this error in Search Console?
I fear this could worse my website position.
Thank you very much for your help!
]]>date error
https://prnt.sc/Ot8ZW_jmf5u2
https://prnt.sc/rA1KUv8NqrS8
I installed ver 2.06 a couple of days ago on a simple 3-page website. Updated just now to 2.07. The plugin appears not to generate a sitemap. Google webmaster tools reported a problem finding a sitemap.
Until the problem is resolved, would you please provide a link to the prior version (probably 2.05) so it can be used temporarily?
Many thanks
]]>There is no functionality to add woo categories to the sitemap. How to solve it?
]]>Hi,
After your latest plugin update I am seeing critical error when trying to access sitemaps. Also, my Google console is unable to fetch sitemaps created by your plugin. Everything was fine until the latest update to version 2.0.6
google is warning me that I have noindex pages listed in my sitemap. How can i remove those?
]]>After the 2.0.4 upgrade, I attempted to edit a post, I get a blank screen. After deactivating the plugin, I am able to edit my posts.
Why does an XML site generator plugin have the ability to break post editing in WordPress?!
]]>After updating to the latest version I got this in my header!
<link rel=”alternate” type=”application/rss+xml” title=”RSS” href=”https:// www. mysite. com/rsslatest.xml” />
I have no idea what this is or why it is showing in the header. Looks terrible. Had to rollback to the older version.
Can you let me know when this is fixed so I can update.
]]>Hi,
I have a Woocommerce shop and have a problem with my xml sitemap and indexing by Google.
Please take a look to this picture:
https://ibb.co/202gC0X
You can see that I search on “8698 370 319” This is a product in my shop.
I get results from a other product but with the text from the “8698 370 319” product.
How can I correct this in this tool ?
Thanks,
Frank
]]>I have found that in the index sitemap (xmlsitemap.xml by default) the first link points to the index sitemap itself /sitemap-files/xml/index/index/1/. So , it is redundant. I don’t know if this happens after I excluded the index in the plugin settings.
]]>Hi, thanks for the great plugin. Especially the ability to change sitemap url, someone been scraping my site using the sitemap.
Now i want to ask on how to disable:
Even when I empty their urls, i can still access the former links just fine.
I want to 404 them.
Thank you.
]]>https://prnt.sc/vvDAzZwvUdRL
how to disable in general, e all parameters except xml?
and
https://prnt.sc/IvftB65Vx09k
how to disable /sitemap-files/xml/latest/archive/1/ ?
Hi,
looks like there’s two erroneous variable uses, followed by wpdb throwing notices:
PHP Warning: Undefined variable $frontPageId in /srv/wp-content/plugins/www-xml-sitemap-generator-org/code/providers/archiveProvider.php on line 41
PHP Warning: Undefined variable $offset in /srv/wp-content/plugins/www-xml-sitemap-generator-org/code/providers/archiveProvider.php on line 41
PHP Notice: wpdb::prepare was called incorrectly. The query argument of wpdb::prepare() must have a placeholder. in /srv/wp-includes/functions.php on line 5768
PHP Notice: wpdb::prepare was called incorrectly. The query does not contain the correct number of placeholders (0) for the number of arguments passed (4). in /srv/wp-includes/functions.php on line 5768
XSGfG 2.0.3
WC 6.3.1
WP 5.9.2
PHP 8.0.17
It is possible remove /xml/latest/archive/1/ from sitemap. I exclude all but this is still in sitemap file.
Thank you for help
Roman
Sorry wrong forum! How do I delete this post?
]]>Tried a new XML Plugin. I saw, that yours does not recognize Multilanguage solutions. In my case im using Translatepress.
Your XML ouput show this url
https://www.example.com/mypost/
But real default url is
https://www.example.com/de/mypost/
Thats ok. Google is intelligent enough to follow this automatic redirection. But url′s like
https://www.example.com/en/mypost/
https://www.example.com/fr/mypost/
are completly missing.
Used the Rank Math sitemap before. There it was working.
]]>Hi,
There is no sitemap being generated for /sitemap-files/xml/posts/post/1/ contained in xxx .com/xmlsitemap.xml. It’s the same for all /posts/post/* sitemaps.
But there is no problem with xxx .com/sitemap.xml from XML Sitemap & Google News plugin.
I’ve disabled the latter and the issue remains, so reactivated it again.
WP V 5.9
Plugin V 2.0.2
Thank you
]]>There’s a bug in the way it is calling flush_rewrite_rules on multisite activation.
Because flush_rewrite_rules() gets the context of the current site, it’s actually flushing the rewrites of the current site to all the subsites in a multisite install.
You may not realize it if you have same permalinks formats on your other sites, but if you have different permalinks, this instantly results in sitewide 404 on all your other sites.
The fix: code/core.php:
function doSiteActivation
replace
self::add_rewrite_rules();
flush_rewrite_rules();
with
if ( is_multisite() && ms_is_switched() ) {
delete_option( 'rewrite_rules' );
}
else {
self::add_rewrite_rules();
flush_rewrite_rules();
}
This is taken from yoast ^
]]>Hello!
I just noticed that Publication date in XML sitemaps is most likely displaying without a GMT offset, which is in my case GMT+3. For examle, if post is published or updated at 12:00, XML sitemap will show 09:00 and so on. I am planning to use plugins for automatic post update so I really need to output last modified post time in XML sitemap. (so option to use “created” instead of “updated” for generating Publication date is not suitable for me)
Wordpress settings are set correctly, I also checked PHP time and MYSQL time as well, they are correct. So it seemes to me that plugin just not use those settings and just fetching data from MYSQL data table without aplying GMT offset to it.
Hi,
I’ve checked the “Add sitemap links to your robots.txt file” checkbox, but sitemap links don’t show on robots.txt
User-agent: *
Disallow: /wp-admin/
Allow: /wp-admin/admin-ajax.php
]]>
I don’t set wp_head now.
Should I do it with this plugin?
Hi,
Added the sitemap yesterday using this plugin, and all looks fine in Search Console. But when I check my access logs, I don’t see that Google has visited the sitemap. With my old sitemap plugin, I could see that Google would quite instantly visit the new sitemap several times per day.
I see this in the log: Oct 25 2021 00:26:53 – Google Auto ping – Google Webmaster Tools – Sitemap Notification Received.
Maybe I’m just being paranoid.
]]>Hi,
Just installed the sitemap and seems to work fine, except I get error in search console for /sitemap-files/xml/posts/sby_videos/1/. It says “XML-tag missing”.
Also, is it possible to change the URL of the sitemap in the settings to a custom one?
Edit: googled and found this answer, is it true?
The “missing XML tag” error appears when the sitemap contains zero items.
]]>Hello
I created custom urls that are not included in sitemap.
How can I add urls programmatically?
I tried
private function addUrlsToSitemap($linkUrls){
require_once('wp-content/plugins/google-sitemap-generator/sitemap-loader.php');
require_once('wp-content/plugins/google-sitemap-generator/sitemap.php');
$googleSitemapGeneratorLoader = new GoogleSitemapGeneratorLoader();
$googleSitemapGeneratorLoader->LoadPlugin();
if(class_exists('GoogleSitemapGeneratorPage')){
$priority = '0.5';
$changeFreq = 'weekly';
$lastMod = time();
foreach ($linkUrls as $key=>$linkUrl) {
$pages[] = new GoogleSitemapGeneratorPage($loc, $priority, $changeFreq, $lastMod, null);
}
$sg = GoogleSitemapGenerator::GetInstance();
$sg->SetPages($pages);
$sg->SavePages();
return;
}
}
But urls aren’t saved.
I’m afraid I am missing one last step.