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

Troubleshooting Common Issues with XML Sitemap Generator for Google

22 threads Sep 16, 2025 Plugin → Xml sitemap generator for google

Content

Users of the 'XML Sitemap Generator for Google' plugin occasionally encounter issues that can prevent it from working correctly. Based on community reports, here are some of the most common problems and their potential solutions.

1. Blank or White Screens in Admin

The Problem: Users report seeing a completely white screen or a near-blank settings page after activating the plugin.

Why It Happens: This is almost always caused by a conflict with another plugin or the active theme. It can also be triggered by a PHP fatal error that stops the page from rendering.

How to Fix It:

  • Conflict Test: Deactivate all other plugins and switch to a default WordPress theme like Twenty Twenty-One. If the problem disappears, reactivate your plugins and theme one by one to identify the culprit.
  • Check Error Logs: Your web host can provide access to PHP error logs. Look for fatal errors that occur when the plugin is active, as they often point to the specific conflict.
  • Manual Plugin Check: In one case, the issue was traced to the plugin trying to load a non-HTTPS stylesheet. A user resolved it by removing the "Use default" stylesheet option in the plugin's settings.

2. Content Not Appearing in the Sitemap

The Problem: The generated sitemap is missing certain content types, such as posts, pages, categories, or custom post types.

Why It Happens: This can occur for several reasons. The plugin may automatically exclude items due to a perceived conflict, there could be a bug that populates the exclude field, or the plugin may not recognize custom rewrite rules and taxonomies from your theme.

How to Fix It:

  • Check Exclusion Settings: Navigate to the plugin's settings and carefully review the "Exclude posts" field. There are reports of this field being automatically filled with post IDs. Manually clear it and save your settings.
  • Custom Content Types: The plugin does not automatically read custom rewrite rules from .htaccess or recognize all custom taxonomies. Currently, the only solution is to manually add the URLs for these pages within the plugin's interface.
  • Re-save Permalinks: Sometimes, simply visiting Settings > Permalinks and clicking "Save Changes" can flush rewrite rules and resolve content visibility issues.

3. Plugin Conflicts and Warnings

The Problem: Users see a warning message about conflicting plugins (e.g., "The following plugins conflict with proper indexation of your website") but no specific plugins are listed.

Why It Happens: This warning is triggered when other SEO plugins like Yoast SEO or RankMath are active, even if their sitemap functionality is disabled. The message is a general notice rather than an indicator of a functional problem.

How to Fix It:

  • The sitemap itself often works correctly despite this warning. You can safely ignore the message if your sitemap is generating as expected. Alternatively, you can use the button provided to disable the other plugin's sitemap feature, which will make the warning disappear.

4. Permission Errors and .htaccess Warnings

The Problem: PHP warnings about being unable to open the .htaccess file appear in error logs when the plugin is active. Users may also be denied access to the settings page due to permission issues.

Why It Happens: The plugin attempts to modify the .htaccess file for certain functions. On hosts like WP Engine that do not use .htaccess files, this attempt fails and causes a warning. Permission issues can also stem from user role capabilities.

How to Fix It:

  • .htaccess Errors: These warnings are often harmless, especially on hosting platforms that use alternative configuration systems. You can typically ignore them if the plugin is otherwise functioning.
  • Settings Page Access: Ensure your WordPress user account has administrator privileges. If the problem persists, a conflict with a security plugin that manages user roles and capabilities is likely.

5. Performance and Timeout Issues

The Problem: Enabling the IndexNow feature can drastically slow down admin operations, like editing navigation menus, causing timeouts.

Why It Happens: The plugin sends IndexNow ping requests immediately after content is updated. On large sites with many changes, this can generate a high volume of API calls that block the editing process.

How to Fix It:

  • The only current solution is to disable the IndexNow feature if you are performing bulk operations in the admin area. You can re-enable it afterward. A feature to defer these pings to a background task has been suggested to the plugin's developers.

If you continue to experience issues after trying these steps, searching for your specific error message on independent forums like BugWP.com or the WordPress.org support forums can often yield additional insights from the wider community.

Related Support Threads Support