Imagine handing Google a complete, always-up-to-date list of every page on your website — and Google actually reading it. That’s what a sitemap is. It won’t magically rank your pages, but it removes every excuse Google has for not finding them. For a new or small site, that’s worth a lot.
What Is a Sitemap, Exactly?
A sitemap is a file — usually XML — that lists the URLs on your site you want search engines to know about, along with a little metadata for each one (typically when the page was last modified). A simple entry looks like this:
<url> <loc>https://yoursite.com/my-article/</loc> <lastmod>2026-10-01</lastmod> </url>
Large sites split this into a sitemap index: a parent file that points to several child sitemaps (one for posts, one for pages, one for categories, and so on). Each individual sitemap file caps out at 50,000 URLs or 50MB uncompressed — a limit you’ll only ever think about if you’re running a very large site.
Now the part people misunderstand: a sitemap helps Google discover your pages. It does not make Google index them. Discovery and indexing are separate steps. Google can find a URL in your sitemap, crawl it, and still decide not to put it in the index. Submitting a sitemap is you raising your hand — it’s not a ticket into the search results.
That said, for new pages on sites Google doesn’t crawl often, a sitemap is the fastest reliable way to get them discovered. It also gives you something valuable in return: the Sitemaps report in Search Console, which tells you exactly how Google sees your file.
Where Is Your WordPress Sitemap?
Here’s the good news: you probably already have one.
If you run WordPress 5.5 or newer (and in 2026, you should), WordPress generates a sitemap automatically at:
yoursite.com/wp-sitemap.xml
No setup, no settings page. It’s a sitemap index linking to separate sitemaps for your posts, pages, categories, tags, authors, and custom post types. It updates itself the moment you publish something new, skips drafts and private content, and quietly turns itself off if you’ve ticked “Discourage search engines from indexing this site.”
If you run Rank Math or Yoast, the plugin takes over sitemap duty and serves its own, richer version at:
yoursite.com/sitemap_index.xml
(Note the underscore — it’s sitemap_index.xml for the plugins, wp-sitemap.xml for WordPress core. Mixing them up is the most common reason people submit a URL that 404s.) The plugin versions add extras core doesn’t have: image sitemaps, the ability to exclude specific posts, and respect for your noindex settings.
Not sure which one you have? Open both URLs in your browser. Whichever one loads valid XML is your sitemap. If neither loads, check that your WordPress is up to date and that no plugin has disabled sitemaps.
How to Submit Your Sitemap to Google Search Console
Google will eventually find your sitemap on its own — through your robots.txt file’s Sitemap: line (which we set up in our robots.txt guide) or just by crawling. Submitting it directly is better for one reason: it unlocks the Sitemaps report, so you can see errors instead of guessing.
You need a verified Search Console property first. Then:
- In Search Console, go to Indexing → Sitemaps in the left sidebar.
- Under “Add a new sitemap,” type just the filename — for example
sitemap_index.xml. The domain is already filled in for you, so don’t paste the full URL. - Click Submit.
That’s it. Google will fetch the file within minutes to hours and the report will show a status for it.
Reading the Sitemaps Report (What the Statuses Mean)
Each submitted sitemap gets one of three statuses:
- Success — Google fetched and parsed the file cleanly. Its URLs are queued for crawling. This is the one you want.
- Has errors — the file was fetched, but something inside it is wrong: malformed XML, unreachable URLs, entries Google can’t use. Click through for the per-URL details.
- Couldn’t fetch — Google couldn’t download the file at all. This is the scary-looking one, and it has its own troubleshooting section below.
Two things the report routinely confuses people about. First, “Discovered URLs” is not “indexed URLs.” It’s just how many URLs Google found in your file. To see how many actually made it into the index, go to the Pages report under Indexing and filter by your sitemap. Second, a sitemap that once succeeded and later fails doesn’t make Google forget the URLs it already learned — but do fix it, because new pages stop being discovered through it.
Fixing “Couldn’t fetch” — A Calm Checklist
“Couldn’t fetch” looks alarming but it’s usually boring. Work through these in order:
- Open the sitemap URL yourself, in a private browser window. Does it load? Do you see valid XML? If you get a 404, you submitted the wrong filename (remember:
sitemap_index.xmlvswp-sitemap.xml). If you see an HTML error page instead of XML, something on your server is intercepting the request. - Check robots.txt isn’t blocking it. Your sitemap URL must be crawlable. (Yes, this is exactly the kind of thing our robots.txt guide helps you verify.)
- Rule out the firewall. Security plugins and server firewalls sometimes block Googlebot’s fetches while letting your browser through. If the file loads for you but Google can’t fetch it, this is the prime suspect.
- Run URL Inspection on the sitemap URL. Paste the full sitemap URL into Search Console’s URL Inspection bar and hit Test Live URL. This forces a fresh fetch and tells you exactly what Google sees — sometimes the “Couldn’t fetch” is just a stale cached failure from an earlier attempt, and the live test comes back clean.
- Resubmit and wait. Sitemap statuses can lag by a day. Fix the cause, resubmit, and check back tomorrow before assuming anything else is wrong.
One reassurance while you troubleshoot: a failed sitemap does not remove your pages from Google’s index, and Google discovers most pages through links anyway. The sitemap is an accelerator and a diagnostic tool, not a load-bearing wall.
Two Things People Get Wrong About Sitemaps
“I submitted my sitemap, so my pages will be indexed.”
No. Submission gets your URLs discovered and queued for crawling. Indexing is a separate decision Google makes per page, based on quality and signals — and “Request indexing” in URL Inspection is a nudge, not a guarantee. If submitted pages sit at “Discovered — currently not indexed” for weeks, the fix is better content and real links, not sitemap configuration.
“I don’t need to submit it — Google will find it anyway.”
Mostly true, and that’s fine for established sites. But submission costs thirty seconds and buys you the Sitemaps report: fetch errors, discovered-URL counts, and early warning when something breaks. For a new site publishing its first articles, it’s the cheapest visibility into how Google sees you.
Frequently Asked Questions
Do I need a sitemap if my site is small?
It helps most when your site is small or new — that’s when Google crawls you least often and a direct list of your pages does the most work. Large established sites get crawled thoroughly regardless.
How long does it take Google to process a sitemap?
The fetch itself usually happens within minutes to hours of submission. The status in the report can lag by a day. Actual crawling and indexing of the discovered URLs then takes days to weeks, and is never guaranteed.
Why does my sitemap say “Couldn’t fetch” even though the URL works for me?
The usual suspects, in order: wrong submitted filename, the file blocked by robots.txt or a firewall, a server error Google hits but your browser doesn’t, or a stale cached failure. Run through the checklist above — URL Inspection’s live test is the tiebreaker.
Does submitting a sitemap guarantee indexing?
No. It guarantees discovery — Google will know the URLs exist and queue them for crawling. Whether each page gets indexed depends on Google’s quality assessment, not on the sitemap.
Should I submit one sitemap or several?
Submit the sitemap index (the parent file). Google follows it to the child sitemaps automatically. Don’t submit each child file separately — it just clutters the report.
Your sitemap is the one file on your site whose entire job is talking to Google. Submit it, glance at the report monthly, and fix “Couldn’t fetch” the day you see it — future you will be grateful.
Earlier in this series: Robots.txt for Beginners — what every WordPress site owner should know.
