How XML Sitemaps Work and How WordPress Plugins Differ
- An XML sitemap is a list of URLs for search crawlers
- It works as an index with multiple lists, not as a single file
- WordPress’s built-in feature is simple and largely automatic
- SEO plugins provide more detailed control over the same map
- Yoast SEO connects search visibility settings with the sitemap
- Rank Math lets you manage content types from its settings
- AIOSEO keeps the sitemap up to date as a virtual page
- The most important thing about a sitemap is the quality of its URLs
- Which sitemap should I use for my site?
- Frequently Asked Questions
- WordPress Resources
You created a sitemap hoping your pages would appear in search results sooner, so why has nothing changed? An XML sitemap is not a magic file that boosts search rankings. It is more like a directory that gives search crawlers a list of your site’s URLs.
In WordPress, however, two sitemaps can look quite different even when they serve the same basic purpose. The structure and controls depend on whether you use WordPress’s built-in feature or an SEO plugin.
An XML sitemap is a list of URLs for search crawlers
For people, a site’s menus and the links between its articles are a map for finding your way around. For search crawlers, an XML sitemap is more like a separate address book handed to them.
Imagine a small shop that has just opened. Even if it is tucked away down an alley, customers can find it more easily if they are given a flyer with its address and opening hours. A sitemap does something similar by pointing crawlers to pages they might otherwise miss.
According to Google, a sitemap can include not only page URLs but also information such as when a page was last updated and details about equivalent pages in other languages. But listing a URL in a sitemap does not guarantee that the page will appear in search results.
There is an important distinction to make here. A search crawler finding and visiting a page is a different process from adding that page to the search index.
A sitemap helps with the first step: discovery and crawling. If a page has thin content or is too similar to another page, a search engine may choose not to include it in search results even after crawling it.
It works as an index with multiple lists, not as a single file
If your site has only a handful of pages, putting all the URLs in one file is perfectly manageable. But if an online shop has 30,000 products or a blog has 5,000 posts, maintaining a single list quickly becomes impractical.
That is why XML sitemaps are usually built in two layers. First comes a sitemap index containing the overall list. Under it sit separate sitemaps for different types of content, such as posts, pages, and products.
Search crawlers read the index first, then follow it to the relevant child sitemaps to check the individual URLs.
Google says a single sitemap can contain up to 50,000 URLs or 50MB of uncompressed data. If you exceed either limit, you split the URLs across multiple files and group those files together in an index.
This structure is not just for very large sites. Even on a small site, separating posts from products or other content types makes it easier to see what is being managed properly.
Surprisingly, a sitemap does not have to be a physical file on the server. WordPress and many plugins generate XML on demand by reading the database when a sitemap URL is requested.
So it is perfectly normal not to find a file called sitemap.xml in a server folder. If the URL opens normally in a browser and the contents are correct, you may be looking at a dynamically generated sitemap.
WordPress’s built-in feature is simple and largely automatic
WordPress has provided XML sitemaps by default since version 5.5. The default URL is usually your site’s address followed by wp-sitemap.xml.
According to the WordPress developer documentation, the built-in feature organizes WordPress-managed content—such as posts, taxonomies, and users—by provider. If the site is publicly accessible, WordPress can generate a sitemap without an additional plugin.
The main advantage of the built-in feature is its simplicity. You do not need to install another plugin, and the sitemap updates automatically when you publish or delete content.
The trade-off is that fine-grained control may be limited. If you want to exclude a particular post type or taxonomy from search results, you may need to use theme code or another feature.
There is another setting to watch: whether the site is visible to search engines. If WordPress is configured to discourage search-engine visibility, the sitemap may not appear at all or may return a 404 error.
When checking for the first time, the following sequence is the simplest:
- Add wp-sitemap.xml to the end of your site address.
- Check whether the sitemap index contains lists for posts and pages.
- Confirm that the URLs of recent posts appear in the relevant list.
- Click a URL and make sure the page opens without requiring a login.
SEO plugins provide more detailed control over the same map
An SEO plugin’s sitemap is not simply a copy of WordPress’s built-in version. Each plugin makes its own decisions about which content to include or exclude, how to divide the lists, and how to record update dates.
Yoast SEO connects search visibility settings with the sitemap
Yoast SEO typically uses an index URL called sitemap_index.xml. It divides posts, pages, taxonomies, and other content into multiple child sitemaps, while excluding content that has been set not to appear in search results.
This makes management straightforward. When you set a post to noindex—in other words, when you tell search engines not to include it in their results—it is also left out of the sitemap.
However, running it alongside WordPress’s default sitemap can create multiple sitemap URLs. Yoast’s own guidance notes that its sitemap can conflict with other sitemap-generation features, so you should check which one is actually active.
Rank Math lets you manage content types from its settings
Rank Math also generally uses an index in the form of sitemap_index.xml. Its settings let you control different content types—such as posts, pages, taxonomies, and products—and it displays the last-modified date in the lists.
On a site where the built-in feature is active as well, the same page may be referenced by different sitemaps. This does not necessarily cause a problem for search engines, but it can leave site owners unsure which URL they should treat as the primary one.
AIOSEO keeps the sitemap up to date as a virtual page
AIOSEO typically uses sitemap.xml as its starting point and divides posts, pages, and other content into separate lists. According to its documentation, the sitemap is generated dynamically when requested, and you can configure the content types and the number of URLs in each list.
By default, the plugin limits each list to 1,000 URLs. The idea is to break the content into smaller batches so crawlers do not have to process an excessively large list at once.
Ultimately, the important difference between plugins is not whether they provide a sitemap, but which URLs they allow you to include or exclude. That is why you should not assume two systems work the same way simply because their URLs look similar.
The most important thing about a sitemap is the quality of its URLs
A well-managed sitemap is not one packed with as many URLs as possible. The goal is to include the canonical URLs you actually want to appear in search results.
Suppose, for example, that an online shop has created 20 URLs for the same product, one for each colour. If you want search engines to show a single product page as the main version, it is better to include that canonical URL in the sitemap.
Deleted posts, login-protected pages, temporary test pages, and pages set not to appear in search results should generally be left out of the sitemap. Including URLs that search engines do not need to crawl can divert resources from the pages that matter most.
URLs should be listed in their complete form. Mixing http and https, or using both www and non-www versions inconsistently, can make the same page appear to be several different URLs.
Pay attention to the last-modified date as well. If you have genuinely updated an article but its date remains unchanged, the sitemap does not help crawlers recognize that an update has taken place.
On the other hand, if the date changes automatically every time without any real change to the content, the signal may become less trustworthy. It is best to avoid settings that update the modified date simply because someone opened the page.
Google does not treat a sitemap as a tool that directly improves search rankings. It is a supporting resource that tells crawlers about important URLs and recent changes.
That is why internal links deserve attention before sitemaps do. Visitors and crawlers should be able to follow the menus and links from the homepage all the way to the pages that matter.
Which sitemap should I use for my site?
For a company website with only a few dozen pages, WordPress’s built-in sitemap is often enough. If you do not need to exclude special content or finely separate product, video, or news listings, there is little reason to run overlapping features.
An SEO plugin can be useful if you frequently adjust which blog posts appear in search or selectively manage categories and tags. Its settings can also help on shops and booking sites with many types of content beyond standard posts.
The deciding factor is not which plugin is most famous. What matters is whether it lets you accurately select the content you actually want to show in search results.
After installation, check these four things:
- Choose one sitemap URL that actually opens.
- Confirm that the sitemap contains your important pages.
- Make sure deleted or hidden pages are no longer listed.
- Do not submit the same sitemap multiple times in your search tools.
If a sitemap URL suddenly returns a 404, do not automatically blame the plugin. Try saving your permalink settings again. A caching feature may be serving an outdated XML file, or the server may be turning the sitemap URL into a regular HTML page.
If checking your sitemap and robots.txt manually every time is difficult, SOHO SEO‘s Site Error Check (key search engine items) lets you configure the plugin to check its sitemap and robots.txt once a day. You can receive an email alert when a problem is detected.
Be especially careful when switching plugins. Turn off the previous plugin’s sitemap feature and confirm the new plugin’s primary URL. Maintaining one accurate sitemap is easier than managing two competing versions.
And submitting a sitemap to a search tool does not mean every page will be indexed immediately. If important pages still do not appear in search after several days, review the page content, internal links, robots.txt, and noindex settings alongside the sitemap.
An XML sitemap is not a report card for your site. It is an up-to-date address book for search crawlers. It does its job when it lists the important destinations accurately and the site itself provides clear paths to reach them.
Frequently Asked Questions
Q. Do I really need an XML sitemap plugin for a WordPress site?
A. Not necessarily. WordPress 5.5 and later provides a built-in sitemap, so the default feature may be enough for a small site. Consider a plugin when you need to exclude content more precisely or separate different types of products and other content.
Q. I do not know whether my sitemap URL is wp-sitemap.xml or sitemap_index.xml.
A. Check which feature is currently active. WordPress’s built-in feature generally uses wp-sitemap.xml, while some SEO plugins use sitemap_index.xml. Open both URLs in a browser and use the one that contains the actual sitemap.
Q. Will every page in my sitemap be indexed by Google?
A. No.
A sitemap helps search engines discover and crawl pages, but it does not guarantee that they will be indexed. Content quality, duplication, internal links, and the search engine’s own assessment all play a role.
Q. I deleted a post, but it is still showing in the sitemap.
A. A cache may be serving an older version, or another plugin may be generating a separate sitemap. Clear the cache, check the different sitemap URLs, and confirm that the deleted post’s public URL returns a 404 or leads to an appropriate replacement page.
Q. Should I submit a sitemap for a small blog?
A. Google says a sitemap may not be necessary for a small site with roughly 500 pages or fewer, provided its internal links are well organized. Even so, submitting one can be a sensible precaution if you want new posts discovered quickly or have isolated pages.