Configuring Rank Math XML sitemap settings is not simply a matter of enabling every available content type. A sitemap should reflect the public, useful URLs that a website wants search engines to discover and potentially index. That decision can differ between a company website, a content site and a WooCommerce store.
Rank Math provides separate controls for posts, pages, products, taxonomies, authors, attachments and other supported types. This makes configuration flexible, but it also means that a missing URL may be intentional rather than a technical error. The practical approach is to review the content type, indexability, canonical settings, exclusions, archive content and cached XML response before changing anything.
What Rank Math XML Sitemap Settings Control
Rank Math creates a sitemap index at the site’s sitemap_index.xml path. This index refers to individual sitemap files for the content types enabled in the configuration. Depending on the content and integrations present, separate sections can cover standard posts and pages, WooCommerce products, WordPress categories and tags, product categories and product tags, authors, attachments, forums, topics and replies.
The main control is the Include in Sitemap setting. It allows each supported content type or archive to be enabled or disabled independently. This is useful because a website may want its public pages and products to be discoverable while excluding utility archives, thin content or other URLs that do not represent valuable destinations.
Inclusion in a sitemap supports URL discovery, but it does not guarantee crawling, indexing or ranking. Rank Math’s documented recommendations are generalized, so the final decision should reflect the content and SEO goals of the particular website. Enabling every option automatically can make the sitemap less focused rather than more useful.
Which WordPress and WooCommerce Content Types to Include
Begin with the purpose of each URL. The question is not whether Rank Math offers a switch for a content type, but whether that type contains public, useful content that the website wants search engines to discover and potentially index.
Posts, Pages and Products
Posts and pages are often the core public content of a WordPress site. Review whether they are intended for public discovery, rather than assuming that every item should appear. Private, utility or low-value content may require a different decision from an important article or service page.
For WooCommerce, review public product URLs separately from product categories and product tags. Products may be central to a store, while the usefulness of an archive depends on its content and role on that particular site. The sitemap setting helps organize discovery; it does not replace decisions about indexability or the value of individual URLs.
Taxonomies, Authors and Other Archives
WordPress categories and tags, as well as WooCommerce product categories and product tags, should be evaluated as archives. An archive with useful, non-thin content may serve a different purpose from an empty or low-value archive. Authors, attachments, forums, topics, replies and other supported types should also be treated as conditional options, not automatic inclusions.
Rank Math documents that empty category, tag and custom taxonomy archives are excluded by default. The Include Empty Terms option can add them, but it should not be enabled without a specific reason for the site. Also review duplicate, private and utility URLs individually before changing their settings.
How to Configure Rank Math Sitemap Sections
Open the sitemap settings in Rank Math and review the sections corresponding to the content types and integrations present on the website. Work through standard WordPress content separately from WooCommerce products and product taxonomies, so that an intended decision for one type is not accidentally applied to another.
For posts, pages, products, categories, tags and other supported archives, use Include in Sitemap according to the earlier content review. Do not treat this control as a replacement for checking whether a URL should be indexable or whether its canonical points to the intended address.
Save the sitemap settings after making changes. Before changing or resetting them, preserve a backup or record of the current configuration. Rank Math states that resetting sitemap settings affects all sitemap settings and cannot be undone without a backup. After saving, test the generated index and the individual sitemap files rather than assuming that the configuration has been served immediately.
Why Is a URL Missing from the XML Sitemap?
A URL missing from the XML sitemap is not automatically evidence of a broken configuration. First determine whether the omission is deliberate. Rank Math documents several settings and content conditions that can explain why an address does not appear.
Indexability, Canonicals and Exclusions
Check the URL’s noindex setting. A noindex instruction can exclude the URL from the sitemap, and changing it without understanding the intended SEO purpose may create a different problem.
Next, inspect whether a custom canonical points to another URL. If the canonical identifies a different address as the preferred version, the original URL may not appear as the expected sitemap target. Confirm that this is intentional before changing it.
Review explicit exclusions in Rank Math for the relevant post or term. A post, taxonomy term, user or role may have been excluded through configuration. Such an exclusion should not be removed merely because the address is absent. The correct troubleshooting question is whether the exclusion still matches the website’s intended SEO decision.
Empty Archives and Stale Output
If the missing address is a category, tag or custom taxonomy archive, check whether it is empty. Rank Math excludes empty archives by default, so their absence can be expected. Enabling Include Empty Terms may add them, but the available documentation does not establish that empty archives are beneficial for every website.
Finally, compare the expected configuration with the actual XML response. If the settings were changed recently but the served file still reflects an older state, the issue may be cached output rather than content eligibility.
Caching: Why the Sitemap Looks Outdated
A cached sitemap can continue serving an older XML response after a URL is published, edited or included through sitemap settings. As a result, a newly expected address may appear to be missing even though the current Rank Math configuration allows it. The same issue can make an old entry remain visible after a change.
When this occurs, check the relevant caching layers used by the website. These may include a site-level cache, a caching plugin, server-side caching or a CDN. The exact exclusion and purge workflow depends on the active environment, so there is no single setting that applies to every hosting provider, server or plugin stack.
Rank Math recommends excluding sitemap files from caching when cached output prevents updates from appearing. Apply that principle to the relevant environment, clear only the appropriate cache layers where suitable, and then request the XML again. Verify the actual response after saving settings and after cache-related changes. A purge is a diagnostic action, not a guaranteed fix; a persistent issue may still come from indexability, canonical or exclusion settings.
How to Troubleshoot a sitemap_index.xml 404 Error
Rank Math automatically creates the sitemap index at the site’s sitemap_index.xml path. A 404 response means that the index is not found, or that an individual sitemap referenced by the index cannot be found. Treat this as a sitemap availability problem rather than a normal sitemap response.
- Confirm the endpoint. Check that the tested address uses the site’s
sitemap_index.xmlpath and that no different or incomplete path is being tested. - Check sitemap generation. Review whether the sitemap module in Rank Math is active and whether the index is being generated.
- Inspect referenced files. Open the index and test each individual sitemap listed in it. A 404 may concern the index itself or one of its child files.
- Save the settings. After reviewing or changing sitemap configuration, save it and test the endpoint again.
- Review site routing. If the error remains, check routing, rewrite behavior and permalink-related site behavior, along with relevant cache layers.
- Consider the environment. The precise repair can depend on the server and installed plugin stack. A continuing 404 may require assistance from the hosting provider or the plugin’s support channel.
Submitting a missing or unavailable sitemap address to Google Search Console does not repair the 404. Availability should be restored and verified first.
Final Validation and Search Console Submission
After configuration, open sitemap_index.xml directly and inspect the individual files it references. Confirm that expected posts, pages, products or archives appear in the appropriate sitemap. Also confirm that deliberate exclusions remain absent, so that the result matches the site’s content and SEO decisions.
Use a short final checklist:
- Review the intended content types and archive value.
- Check noindex and custom canonical settings for missing URLs.
- Inspect explicit post and term exclusions.
- Check whether a taxonomy archive is empty.
- Compare the live XML response with the current configuration.
- Verify that the index and referenced sitemap files do not return 404.
Once the settings are saved and the files are available, the sitemap_index.xml path can be submitted through Google Search Console. Submission supports discovery, but it does not guarantee crawling or indexing.
Effective Rank Math XML sitemap configuration is a focused review, not an instruction to include every available type. Select public and useful content, then investigate missing URLs through indexability, canonical, exclusions, empty archives and cache. For WooCommerce, review products separately from product categories and tags. When sitemap_index.xml returns 404, test both the index and its referenced files before assuming the problem has one universal cause. A sitemap can help search engines discover URLs, but the quality and purpose of those URLs remain site-specific. Explore our WordPress plugins, WooCommerce extensions, themes and membership plans to find the right tools for your website.