Configuring the Dynamic XML Sitemaps Generator Plugin

On a WordPress site, Dynamic XML Sitemaps Generator for Google creates sitemap files: lists of page addresses, or URLs, that software can read and search engines can use to discover content. The plugin, published by WP Grim, lets you choose which content to list and whether to publish one sitemap or a sitemap index. A sitemap index is a file that points to multiple sitemaps.

A sitemap gives Google a hint about which pages it can discover. It does not guarantee that Google will crawl or index every listed page, or improve a page’s rankings. To configure the plugin well, choose URLs that belong in search results, check the sitemap it generates, and submit its exact address in Google Search Console.

Install the plugin and choose a sitemap structure

In WordPress, install and activate Dynamic XML Sitemaps Generator for Google by WP Grim. The settings are under Settings → XML Sitemaps. Check the plugin name and publisher before installing; another plugin has a similar name.

Then configure the main sitemap:

1. Choose one sitemap for a simple setup, or a sitemap index if you want the plugin to organize content in multiple sitemaps.
2. Select the content types to include, such as posts, pages, custom post types, or taxonomies. A custom post type is a WordPress content type beyond standard posts and pages, such as products or portfolio entries. A taxonomy groups content, as categories and tags do.
3. Review the sitemap URL and use the plugin’s preview to inspect the output. If you change the URL, record the final address for submission and any other discovery settings.
4. Save the settings, then open the sitemap URL in a browser to confirm it displays sitemap content rather than an error page.

The plugin also offers a setting to add sitemap URLs to robots.txt, a file that gives search-engine crawlers instructions about a site. That setting can help crawlers find the sitemap, but it does not replace submitting the sitemap or checking its status in Search Console. The plugin’s XML sitemap settings describe the URL, preview, and robots.txt options.

Include URLs that belong in search results

Choose content based on whether you want the page to appear in search results. Google recommends listing each page’s preferred, or canonical, URL. A canonical URL is the version you want search engines to treat as the main address when substantially identical content appears at more than one URL.

For example, include a product post type if its product pages should appear in search, but review whether category or tag archives add useful pages before including those taxonomies. Then check sample entries in the generated sitemap. Do not assume that selecting a content type means every URL it produces is appropriate.

If another WordPress plugin or WordPress itself also generates sitemaps, check which sitemap URL you intend to maintain and submit. The plugin listing describes compatibility with other SEO plugins, but you still need to inspect the sitemap your site produces. Confirm that the submitted sitemap is the one containing the content you selected.

Set size and update details with care

Google limits an individual sitemap to 50 MB uncompressed or 50,000 URLs. If a sitemap exceeds either limit, split its URLs across multiple sitemaps. A sitemap index can reference those sitemaps. Google also recommends UTF-8 encoding and fully qualified URLs, meaning each entry includes the full address, such as the protocol and domain. See Google’s guidance on sitemap format and size limits.

For a sitemap index, the plugin’s Links Per Page setting controls how many links appear on a page. WP Grim recommends a value from 1,000 to 5,000 and warns that a lower value can slow index generation. This is the plugin’s recommendation, not a Google requirement.

The plugin also lets you set priority and update frequency. Google says it ignores the sitemap fields priority and changefreq, so these settings do not tell Google which page to rank higher or exactly when to revisit it. Google can use lastmod, the page’s last-modified date, when it accurately reflects a significant, verifiable change. Keep that date truthful rather than changing it for minor edits. The plugin’s sitemap options documentation describes its content settings.

Submit the sitemap and check Google’s response

After confirming the sitemap URL works in a browser, submit that exact address in the Sitemaps report in Google Search Console. Google’s report can show when Google accessed the sitemap and whether it encountered processing errors. A successful sitemap submission means Google processed the sitemap; it does not mean every listed page was indexed.

If the sitemap sits in a subdirectory, submitting it through Search Console is especially useful. Google notes that a sitemap ordinarily applies to URLs beneath its parent directory unless the sitemap is submitted through Search Console. Google’s sitemap overview also explains that sitemaps complement other ways Google discovers pages, including links between pages.

Enable image, video, or news sitemaps only when relevant

The plugin offers separate image, video, and Google News sitemap options. Enable the image, video, or news option when the site has that content. Then inspect the generated sitemap to confirm it lists the content you want. Enabling a sitemap type does not guarantee search visibility or eligibility for a particular Google feature.

For image content, the plugin’s image sitemap settings explain how to configure the output. The plugin documentation says the default image sitemap includes images used in content and provides a preview. Review that preview to see which images the sitemap lists.

The plugin also documents IndexNow notifications for participating search engines. IndexNow is separate from Google sitemap submission, so enabling it does not replace submitting the sitemap in Search Console.

Troubleshoot errors and stale output

If the sitemap URL returns a 404 error, the plugin’s WordPress FAQ recommends flushing rewrite rules. On an NGINX server, the plugin says additional rewrite rules may be needed; the exact change depends on the server configuration. Check the plugin’s instructions before editing server rules.

If the preview looks outdated after a settings change, check whether the plugin is showing a cached, or previously stored, sitemap. The plugin listing describes options to view the last cached time or clear the cache, but an old preview alone does not establish that caching caused the problem. Also confirm that Google received the correct URL and review the Search Console Sitemaps report for fetch or processing errors.

What I'm building

Delegate tasks. Get software.

Give Vroni a GitHub issue, bug report, spec, or rough idea. It reads the repo, plans the change, writes code, runs checks, and works toward a review-ready pull request.

Take a look at vroni.com