WordPress generates an XML sitemap automatically. Most site owners don’t know it exists until they start paying attention to how Google is crawling their site — and by then they’ve often been missing an easy indexing opportunity for months.
An XML sitemap is a file that lists all the URLs on your site in a structured format search engines can read directly. It doesn’t guarantee that Google will index every page, but it gives the crawler a clear map of what exists — which matters on newer sites that haven’t yet built up many incoming links for Google to follow.
This guide explains where WordPress keeps its sitemap, how to check it’s working, how to submit it to Google Search Console, and what to do if something isn’t right.
Quick Answer
WordPress automatically generates an XML sitemap at yourdomain.com/wp-sitemap.xml. To submit it to Google, open Google Search Console, go to Sitemaps in the left menu, enter wp-sitemap.xml in the URL field, and click Submit. No plugin required for the sitemap itself — it’s built into WordPress core.
Why Sitemaps Matter for a New Site
Google discovers pages primarily by following links. On an established site with plenty of internal and external links, the crawler finds its way around naturally. On a new site with few inbound links and a thin internal link structure, some pages can take weeks to be discovered — or get missed entirely.
Submitting a sitemap tells Google exactly what pages exist and when they were last updated. It doesn’t override Google’s own quality judgements about which pages to index, but it removes the discovery bottleneck. For new sites, that’s a meaningful difference in how quickly content starts to appear in search results.
Google’s sitemap documentation confirms that sitemaps are particularly valuable for large sites, new sites, and sites with pages that aren’t well linked internally — which describes most WordPress sites in their early stages.
Where to Find Your WordPress Sitemap
WordPress has generated a default XML sitemap since version 5.5. You don’t need to install a plugin or configure anything. Visit yourdomain.com/wp-sitemap.xml in your browser and you should see an index file that links out to individual sitemap files for posts, pages, categories, tags, and authors.
The sitemap index looks like this:
wp-sitemap-posts-post-1.xml— all published postswp-sitemap-posts-page-1.xml— all published pageswp-sitemap-taxonomies-category-1.xml— category archive pageswp-sitemap-taxonomies-post_tag-1.xml— tag archive pageswp-sitemap-users-1.xml— author archive pages
Each of these sub-sitemaps contains the URLs for that content type along with their last-modified dates. If you have a large site, WordPress automatically splits each type across multiple numbered files.
How to Submit Your Sitemap to Google Search Console
Before submitting, you need your site verified in Google Search Console. If you haven’t done that yet, the guide to setting up Google Search Console for a new WordPress website walks through verification and the initial configuration.
Once you’re in Search Console:
- Select your property from the top-left dropdown if you have more than one site.
- Click Sitemaps in the left-hand menu under the Index section.
- In the Add a new sitemap field, type
wp-sitemap.xml(your domain URL is already prefilled). - Click Submit.
Google will immediately attempt to fetch the sitemap. Within a minute or two you’ll see it appear in the Submitted sitemaps list with a status of Success and a count of discovered URLs. If it shows an error, see the troubleshooting section below.
You only need to submit the index sitemap (wp-sitemap.xml). You don’t need to submit each individual sub-sitemap separately — Google reads the index and follows the links to each one automatically.
Checking That the Right Pages Are Included
Once submitted, open each sub-sitemap in your browser and scan the URLs. You’re checking for two things: that the pages you want indexed are present, and that pages you don’t want indexed aren’t there.
Pages excluded from the sitemap by default include password-protected posts, drafts, and anything set to noindex via a plugin or custom code. If you’re using the default WordPress sitemap without a plugin, you have limited control over exclusions — the sitemap includes all published public content.
Author archive pages are included by default. If you’re a single-author site, having an author archive in the sitemap is generally harmless but adds little value. You can exclude it by adding a filter to your theme’s functions.php file, or by using a plugin that gives you sitemap controls.
Practical Tips
- Resubmit after major changes. If you significantly restructure your site — changing permalink structure, adding a large batch of new posts, or deleting pages — resubmit the sitemap to prompt Google to recrawl. Search Console keeps a record of each submission.
- Don’t confuse sitemaps with robots.txt. Your robots.txt file controls which pages crawlers are allowed to visit. Your sitemap tells them which pages exist. Both should list the same public content — pages blocked in robots.txt but present in the sitemap create a mixed signal.
- Check the Submitted vs Indexed count. In Search Console, the sitemap report shows how many URLs were submitted and how many are actually indexed. A large gap — say, 80 submitted but only 20 indexed — usually indicates thin content, duplicate content, or pages Google doesn’t consider worth indexing rather than a technical sitemap problem.
- The sitemap updates automatically. WordPress regenerates the sitemap dynamically every time it’s requested. You don’t need to do anything when you publish new posts — the sitemap always reflects the current state of your site.
Common Mistakes
- Submitting the sitemap before the site is ready to index. If you’re still building and have search engine indexing turned off in WordPress Settings → Reading, your sitemap will be accessible but Google won’t be able to index the pages anyway. Make sure indexing is enabled before submitting.
- Using a plugin that generates a duplicate sitemap. Some SEO plugins create their own sitemap and disable the WordPress default. If you’re using such a plugin, submit the plugin’s sitemap URL rather than
wp-sitemap.xml. Running two active sitemaps creates confusion rather than benefit. - Assuming submission means instant indexing. Google processes sitemaps on its own schedule. Submission speeds up discovery but doesn’t guarantee a specific timeline. New pages on new sites can take days to weeks to appear in search results even after submission.
If Your Sitemap Returns an Error
If visiting yourdomain.com/wp-sitemap.xml returns a 404 error, a blank page, or the sitemap doesn’t appear in Search Console, check these in order:
- Permalink settings. Go to Settings → Permalinks in WordPress and click Save Changes without changing anything. This flushes the rewrite rules, which is often enough to restore the sitemap if it stopped working after a settings change.
- Search engine visibility. Go to Settings → Reading and confirm the “Discourage search engines from indexing this site” checkbox is unchecked. When this is checked, the sitemap still exists but Google won’t crawl it.
- Plugin conflict. A security or caching plugin may be blocking the sitemap URL. Temporarily deactivate plugins one at a time and check whether the sitemap reappears.
- Caching. If you’re using a caching plugin, clear the cache after making any changes — an old cached version of the sitemap can cause stale data to appear in Search Console.
Sitemaps help Google discover pages, but discovery is only half the picture — once a page is found, its internal linking strategy is what signals which pages actually matter and helps them get crawled regularly.
Conclusion
Submit wp-sitemap.xml to Google Search Console early in your site’s life and leave it. The sitemap stays current automatically, and Search Console will show you how many of your pages are being indexed over time. If you haven’t connected Search Console yet, that’s the prerequisite — it’s also where you’ll find the indexing data that tells you whether your basic SEO setup is working. Everything about checking that indexing is happening correctly is covered in the guide on checking whether your WordPress website is indexed by Google. Start at Veravix for the full picture on building a well-structured WordPress site.
Etienne Basson works with website systems, SEO-driven site architecture, and technical implementation. He writes practical guides on building, structuring, and optimizing websites for long-term growth.