WordPress sitemaps are XML files that list the URLs on your site that are eligible to be crawled (and potentially indexed) by search engines. In modern WordPress, a core sitemap is generated automatically, stays updated as you publish or change content, and is organized as a sitemap index that links to smaller sitemap files by content type.
They don’t “force rankings” or guarantee indexing. Instead, they help crawlers discover URLs efficiently and understand what content exists, especially on larger sites or sites with complex navigation.
What a sitemap is (and what it isn’t)
A sitemap is a machine-readable roadmap of your site. Search engines can use it to find URLs they might otherwise miss (for example, pages not well linked internally yet, or deep archive URLs).
- A sitemap helps with discovery. It’s a hint: “These URLs exist and may be worth crawling.”
- A sitemap is not an indexing guarantee. Search engines may choose not to index some URLs (duplicate, low-value, blocked, or canonicalized elsewhere).
- A sitemap doesn’t replace internal links. Good internal linking still matters for crawl paths, topical context, and prioritization.
When WordPress started including sitemaps by default
Since WordPress 5.5, core WordPress can generate an XML sitemap out of the box (no plugin required). The WordPress project introduced this to improve how quickly search engines can discover key pages on new and existing sites. (See the WordPress 5.5 documentation reference: WordPress 5.5 “Say hello to your new sitemap”.)
Where to find your WordPress sitemap (default locations)
On most sites using “pretty permalinks,” the core sitemap index lives at:
- /wp-sitemap.xml
- /?sitemap=index
This behavior is documented in the WordPress developer reference for how the index URL is built: WP_Sitemaps_Index::get_index_url().
What you see when you open wp-sitemap.xml
The main file is typically a sitemap index, not a single massive list. The index links to multiple sitemap files (for example, one for posts, one for pages, and possibly additional sitemaps for other public post types and taxonomies).
This split matters because search engines prefer manageable sitemap sizes. WordPress uses an index so the system can generate and maintain multiple smaller sitemaps rather than one huge file.
What WordPress sitemaps include by default
WordPress’s core sitemap system is designed to cover public, indexable content types that WordPress knows about. What’s included depends on your site configuration (and what your theme/plugins register as public).
Common inclusions are:
- Posts and pages (standard WordPress content types)
- Other public post types (for example, portfolio items or documentation, if registered as public)
- Taxonomy archives (for example, categories and tags), when enabled as public
- Author archives, depending on how your site is set up
Each sitemap entry typically includes a URL and a last modified date/time, which can help crawlers decide whether something needs to be revisited.
What WordPress core sitemaps usually do not include
- URLs that aren’t public (private posts, password-protected content)
- Admin URLs (wp-admin and other backend routes)
- Many “thin” utility URLs that aren’t meaningful as standalone pages
Also note: WordPress core sitemaps are not the same as specialized sitemap extensions (for news, video, images). Those often require additional tooling and configuration and depend on what a site publishes.
How WordPress generates and updates sitemaps
WordPress generates sitemaps dynamically using core functionality. Practically speaking, this means:
- Publishing new content adds new URLs automatically. When a post or page becomes public, it becomes eligible to appear in a sitemap.
- Updating content can update the lastmod value. The sitemap can reflect when a URL last changed, which may encourage re-crawling.
- Deleting content removes it from the sitemap. (Search engines may still crawl the old URL for a while; your redirects and status codes matter.)
There isn’t a universal “push” notification happening from your sitemap alone. Search engines still crawl on their own schedules, and sitemaps are one of several signals that influence crawl discovery and recrawl patterns.
How search engines use a WordPress sitemap
Search engines can use sitemaps in a few key ways:
- Discovery: Find URLs that exist, especially ones that aren’t prominent in internal navigation yet.
- Prioritization hints: Use signals like last modified dates to decide what to recrawl sooner.
- Coverage checks: Compare what you say exists (sitemap) versus what they can crawl (blocked pages, redirects, errors).
Google’s documentation describes sitemaps as a way to tell Google which pages and files you think are important on your site (and when they were last updated). You can read more in Google Search Central’s sitemap overview.
Indexing behavior: why “in the sitemap” doesn’t always mean “indexed”
If a URL is included in your WordPress sitemap, that simply means WordPress considers it a public URL worth listing. Search engines still apply their own evaluation, such as:
- Quality and uniqueness: near-duplicate or thin pages may not be indexed.
- Canonicalization: if a page points to a different canonical URL, the canonical may be indexed instead.
- Crawl accessibility: if the URL is blocked (robots directives) or returns errors, indexing can fail.
- Site signals and crawl budget: very large sites may see slower discovery/recrawls for low-priority URLs.
A good mental model is: sitemaps help crawlers find URLs; indexing depends on whether those URLs are worth keeping in the index and can be accessed reliably.
How to verify your WordPress sitemap is working
1) Open the sitemap in a browser
Visit /wp-sitemap.xml on your domain. You should see an XML sitemap index listing one or more child sitemap files. If you see a 404, the site may be using a different sitemap solution, permalinks may be off, or something is filtering sitemap output.
2) Check that important content types appear
Click into the child sitemaps (often grouped by type). Confirm that recent posts/pages appear and that the URLs look correct (right domain, right protocol, preferred trailing slash style).
3) Spot-check last modified times
Edit a page, update it, and then re-check its entry later. You’re looking for a plausible last modified value. Don’t obsess over minute-by-minute changes; focus on whether the sitemap reflects meaningful updates over time.
4) Use Search Console coverage and sitemap reporting (if you have it set up)
If you’ve connected your site to a search engine’s webmaster tools, you can typically submit the sitemap index URL and monitor discovered URLs, errors, and warnings. This is often the fastest way to find issues like submitted URLs blocked by robots directives, redirecting URLs, or server errors.
Common WordPress sitemap issues (and what to do)
Sitemap returns 404 or doesn’t load
- Permalinks: confirm your permalink settings are enabled and saved (resaving can refresh rewrite rules).
- Plugin conflicts: some SEO plugins replace the core sitemap route with their own. That can be fine, but you should have one clear sitemap index to submit.
- Caching/security rules: aggressive security rules can block sitemap endpoints; server logs can help diagnose.
Too many low-value archive URLs listed
Depending on your site, category/tag/author archives can be useful (especially for editorial sites) or can create lots of thin pages (especially with many tags used once). If your sitemap contains many pages you don’t want crawled or indexed, consider whether you should:
- reduce the number of tag archives you create,
- improve archive pages so they’re genuinely helpful, or
- adjust whether those archives are meant to be indexable (this is usually handled via SEO settings/plugins, not by editing the sitemap directly).
Sitemap lists URLs you redirected or deleted
If you recently changed URLs, search engines may continue to request the old URLs for a while. The sitemap should eventually reflect the new reality, but what matters most is that the old URLs return appropriate redirects (or 410/404 where intended) and the new URLs are internally linked.
Core WordPress sitemaps vs. SEO plugins: what site owners should know
Core sitemaps cover the basics. Many SEO plugins add more control, such as:
- including/excluding specific post types or taxonomies from sitemaps,
- fine-grained rules for archives,
- additional sitemap formats (depending on the plugin),
- tighter alignment between “index/noindex” settings and what gets listed.
If you’re using an SEO suite that automates on-page SEO and site structure, it may also help you avoid the most common sitemap pitfall: listing lots of URLs that don’t have strong internal links or clear purpose. For example, SEO Max Suíte focuses on content creation, internal linking, and structured enhancements—things that can make the URLs in your sitemap more valuable once discovered.
Best practices for managing WordPress sitemaps (without overthinking them)
- Make sure your sitemap index is accessible (loads fast, doesn’t error, returns 200 status).
- Keep your URL set clean: avoid generating endless low-value tag/parameter pages.
- Align indexability with intent: if a section shouldn’t be indexed, don’t rely on the sitemap to “fix” that—use proper SEO settings and technical directives.
- Use internal linking to support discovery and importance: sitemaps help, but internal links tell crawlers what matters most.
- Treat the sitemap as a diagnostic tool: if it’s full of URLs you wouldn’t want a user landing on from Google, that’s a signal to adjust your architecture.
Quick recap: how WordPress sitemaps work
- WordPress generates an XML sitemap system by default (since 5.5).
- The main file is usually a sitemap index at /wp-sitemap.xml.
- The index links to child sitemaps grouped by content type.
- Sitemaps update as you publish, edit, or delete public content.
- Search engines use sitemaps primarily for discovery and recrawl hints, not as an indexing guarantee.