Every WordPress site already has a sitemap. WordPress 5.5 put one at /wp-sitemap.xml back in 2020, and most owners never open it. Problems start once a plugin adds a second sitemap and you can't tell which of the two Google is reading.
On October 18, 2026, we looked at what 20 well-known WordPress sites really serve. At eight of them, /wp-sitemap.xml redirected somewhere else. One site served a file at that address whose own XML said a different plugin made it. So find out what your site has before you submit anything.
Below you'll see how to create a WordPress sitemap, find the one your site serves, and submit it to Google and Bing. Then we get to what helps new pages get indexed faster.
What WordPress makes on its own
When WordPress announced version 5.5, it said the site "will expose a sitemap index at /wp-sitemap.xml." That index points to smaller sitemaps for your public posts and pages. Others cover categories, tags and author archives, and the homepage is in there too.
A single small sitemap holds up to 2,000 URLs. The index can list up to 50,000 of those sitemaps, so you won't run out of room. WordPress also adds the sitemap to the robots.txt file it serves, which means search engines find it without any work from you.
If you don't run an SEO plugin, you don't need to create a WordPress sitemap at all. You just check that it works and submit it.
Find out which sitemap your site serves
You need about five minutes for this. Open each address below in your browser.
yoursite.com/wp-sitemap.xmlyoursite.com/sitemap_index.xmlyoursite.com/robots.txt
A list of sitemaps at the first address means WordPress core is in charge. If it jumps to the second address, an SEO plugin has taken over. Either way, the last line of robots.txt should be a Sitemap: line that points to whichever one is live.
Our 20-site check turned up three surprises. When Search Engine Journal redirected /wp-sitemap.xml, the response header named Yoast SEO as the source. WPBeginner did answer at /wp-sitemap.xml, but the file's own comment said All in One SEO Pro made it, not WordPress. And three sites had working sitemaps but no Sitemap line in robots.txt at all.
Seven more sites blocked our request or said "not found." Most of their robots.txt files pointed to working sitemaps, so bot protection is the likely cause. If yours won't load, look at your firewall before you decide the sitemap is missing.
We call this the two-sitemap trap. A plugin adds its own sitemap while the core one stays live, or something else answers for it, and you submit whichever you found first. Search engines are then left guessing which list is current.

Built by the team that got cited in 48 hours.
Content generation, backlink building, AI visibility tracking, and Google rankings. One platform, zero guesswork.
If you use Yoast SEO or Rank Math
Both plugins swap the core sitemap for their own at sitemap_index.xml. You don't have to switch anything off by hand, but each one behaves a little differently.
In Yoast SEO, go to Settings, then Site features, and you'll find an XML sitemaps toggle. Yoast's help page says that turning it on "will automatically disable the default WordPress XML sitemap." It also warns that if you later turn Yoast's sitemap off, the core one won't come back by itself.
Rank Math switches its sitemap on during setup. It lives at sitemap_index.xml, with separate sitemaps inside for posts, pages and products. You change it under Rank Math SEO, then Sitemap Settings.

If you've connected Rank Math to Search Console, its guide says it "will automatically submit the sitemap" for you. I'd still open the Sitemaps report once to make sure it arrived.
Never run two SEO plugins with their sitemaps on. That's the quickest way to land in the two-sitemap trap.
Submit it to Google Search Console
Google's steps on the Sitemaps report help page are short. Give yourself about 15 minutes the first time.
- Open Search Console and pick your property.
- Run your sitemap address through URL Inspection to check Google can reach it.
- Open Sitemaps from the left menu.
- Paste the address into "Add a new sitemap" and click Submit.

After that, the report shows one of three statuses. With "Success", Google fetched the file and read it. "Has errors" means it got the file, but something inside is broken. A "Couldn't fetch" is usually a firewall, a redirect loop or a wrong address.
Submit only the index. Google reads it and follows it to all the small sitemaps, so you don't need to add each one. Once you're set up, our guide to Search Console's AI performance report covers what else is worth a look in there.
Submit it to Bing Webmaster Tools
Don't skip Bing. Microsoft Copilot answers draw on Bing's index, so it matters more than its search share suggests. Bing's sitemaps help page calls sitemaps "an excellent way to tell Bing about URLs" its crawlers might miss.
Sign in to Bing Webmaster Tools, open Sitemaps and click "Submit sitemaps" at the top right. Then paste the same address you gave Google. If the site is already verified in Search Console, Bing lets you import it from there and save a step.
Bing reads the Sitemap line in robots.txt as well. WordPress and the big plugins add that line for you, but our check found sites without it, so look at yours.
Common sitemap problems and fixes
Most WordPress sitemap trouble traces back to a short list of causes. Here's what each status or symptom usually means.
| What you see | Likely cause | What to do |
|---|---|---|
| "Couldn't fetch" in Search Console | Firewall, security plugin or a wrong address | Load the sitemap in a private window, then check bot rules in your firewall or CDN |
| "Has errors" | A broken URL or bad XML inside one sitemap | Open the report, find the sitemap named, and check the plugin is up to date |
/wp-sitemap.xml shows 404 | Sitemaps turned off, or a plugin replaced it | Try /sitemap_index.xml, then check your SEO plugin's sitemap toggle |
| Pages in the sitemap but not indexed | Thin, duplicate or poorly linked pages | Improve the page and link to it from pages that are already indexed |
| Noindexed pages in the sitemap | A setting left on for tags or media | Exclude those types in the plugin's sitemap settings |
A site move catches people out too. If you changed domains, or went from http to https, submit the new sitemap under the new property. The old one won't carry over on its own.
When the sitemap checks out and pages still won't index, look at the pages. The file is almost never the cause.
What a sitemap won't do
Google doesn't oversell it. Its sitemap guide, last updated July 8, 2026, calls a sitemap "merely a hint." The Search Console help page goes further and says there's no guarantee a URL in it "has been or will be crawled or indexed."
You can see this in a thread on r/TechSEO. A new WordPress site owner had the homepage indexed and nothing else, and they kept asking for indexing by hand. The top reply told them to stop, since repeat requests don't move you up the queue. It added that on a site that small, Google doesn't need a sitemap to find the pages.
Need help: Homepage is indexed, but no other pages are getting indexed (WordPress + Hostinger)
Hi everyone, I'm dealing with a frustrating indexing issue on one of my client websites and would really appreciate your suggestions. Here's the situation: The website is built on WordPress and hosted on Hostinger. The homepage is indexed,...
A developer on r/webdev described a second trap. Your sitemap can load fine in your browser while a firewall or Cloudflare rule still blocks Googlebot from the pages it lists. So the fact that you can see the file proves nothing about what Google can crawl.
How to get new pages indexed faster
The sitemap only tells Google a page exists. Getting it indexed takes a reason for Google to care, and a few habits do most of the work.
Start with links. Your homepage and your older popular posts get crawled often, so a link from one of them gets a new page found fast. Then use URL Inspection once for each new or changed page. Leave it alone for a week or two, since asking daily won't help.
If a page still sits outside the index, fix it before you resubmit. A thin page, or a near-copy of another post, is often left out for a reason. Keep the sitemap itself clean as well. Most plugins let you leave out redirects, noindexed pages and thin tag archives.
Last, check your robots.txt, where one stray rule can block a whole folder. Our robots.txt and AI crawler checklist covers what to look for. For pages you update rather than create, our guide to re-indexing signals after a content refresh goes deeper.
See your first AI citation report in under 5 minutes.
No setup calls. No onboarding meetings. Connect your domain and see where AI mentions your brand right now.

Doing it yourself or handing it off
Setup is a one-time job of about 30 minutes. You run one check, change one plugin setting and submit to Google and Bing. From then on, the sitemap updates itself each time you publish. The work that never ends is the pages, which need internal links, real content and a reason to be indexed.
RankControl can take that part on. We write articles against the pages already ranking for each keyword and publish them as native WordPress posts, so they land in your sitemap like any other post. Our AI visibility tracking then checks up to 50 buyer questions a week across seven AI engines. Expect traffic from Google and AI search first, with citations following more slowly as other sites link to you.
Your competitors are building backlinks while you read this.
Organic outreach, social mentions, and citations from Editorial Circle member sites, with managed backlinks available as an add-on. Grow your domain authority without running the campaign yourself.










