BugWP logo BugWP
Back to Community
Home / Community / Plugin → Xml sitemap generator for google

Troubleshooting Common 'XML Sitemap Generator for Google' Errors and Warnings

48 threads Sep 7, 2025 Plugin → Xml sitemap generator for google

Content

If you use the 'XML Sitemap Generator for Google' plugin, you might occasionally run into confusing error messages, warnings from security plugins, or unexpected behavior. This guide compiles the most common issues reported by users and provides steps to diagnose and resolve them.

1. False "Blocking Search Engines" Warning

The Problem: The plugin displays a warning that "Your site is currently blocking search engines!" even though your WordPress Reading Settings are correctly configured to allow search engine indexing.

Why It Happens: This is a known bug that has appeared in several plugin versions. The plugin's check against the blog_public WordPress option is not functioning as intended.

The Solution: This issue is typically resolved in subsequent plugin updates. Ensure your plugin is updated to the latest version. If the problem persists after updating, it is generally safe to ignore the warning as long as your actual WordPress settings are correct.

2. Wordfence "Suspected Malware URL" Alert

The Problem: Security plugins like Wordfence flag the file sitemap-core.php for containing a suspected malware URL: http://www.google-analytics.com/collect.

Why It Happens: This URL is part of the plugin's optional, anonymous usage statistics tracking feature. Wordfence's blacklist has incorrectly classified the non-HTTPS version of this legitimate Google Analytics endpoint.

The Solution: This is a false positive. You can safely ignore the warning in Wordfence. The 'XML Sitemap Generator for Google' team has addressed this in newer versions, but the alert may still trigger. If you are concerned, you can disable the anonymous data sharing option in the plugin's settings.

3. "There was a problem while notifying Google/Bing"

The Problem: The ping test or automatic notification to search engines fails, often accompanied by a debug log message.

Why It Happens: This can be caused by several factors:

  • Bing's API Change: Bing has discontinued its instant ping feature. The plugin has since removed this functionality.
  • DNS or Connection Issues: A temporary problem with your server's ability to connect to external services.
  • Debug Mode: The error message might be obscured if WP_DEBUG</code is disabled on your site.

The Solution:

  • For Bing, no action is needed. Bing will automatically crawl your sitemap without manual pinging.
  • For Google, try using the "Notify search engines now" button manually. If it works, the automatic ping will likely resolve itself.
  • Check your server's error logs for more specific connection-related errors.

4. Database Error: "Unknown column 'post' in 'where clause'"

The Problem: A PHP error appears in your logs referencing an unknown column 'post' in a SQL query generated by the plugin.

Why It Happens: The error occurs when a post_type value in a SQL query is not wrapped in quotes, causing it to be interpreted as a database column name instead of a string value.

The Solution: This is a bug that the plugin's developers have fixed in an update. Updating the plugin to the latest version should resolve this error immediately.

5. Excessive Calls to Google/Bing

The Problem: Your server is making an extremely high number of calls to ping search engines, sometimes dozens per minute.

Why It Happens: This happens when the "Notify search engines about updates" option is enabled. The plugin is designed to ping them every time a post or page is published or updated. On a busy site with frequent changes, this can create many requests.

The Solution: If the volume of requests is problematic, you can disable the automatic notification feature. You can then manually submit your sitemap to Google Search Console and Bing Webmaster Tools, which is often more efficient.

General Troubleshooting Tips

  • Update First: Always ensure you are running the latest version of the plugin, as many reported bugs are fixed in subsequent releases.
  • Check Logs: Server error logs (often found in your hosting control panel) provide more detailed information than generic WordPress warnings.
  • Conflict Test: If problems are unexplained, temporarily disable other plugins to test for a conflict.

Most issues with the 'XML Sitemap Generator for Google' plugin are minor and resolved through updates. By following these steps, you can quickly get your sitemap back on track.

Related Support Threads Support