A missing XML sitemap means your site has no file that lists the pages you want search engines to crawl. Google and Bing then find pages only by following links, so new, deep or weakly linked pages are discovered later or not at all. Every modern CMS can generate a sitemap for you; the fix is to turn it on, check it lists the right URLs and submit it in Google Search Console and Bing Webmaster Tools.
What an XML sitemap is
A sitemap is an XML file, usually at /sitemap.xml, that lists the canonical URLs of your site with an optional last modified date:
<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
<url>
<loc>https://example.com/</loc>
<lastmod>2026-11-01</lastmod>
</url>
<url>
<loc>https://example.com/pricing</loc>
<lastmod>2026-10-14</lastmod>
</url>
</urlset>
One file holds at most 50,000 URLs or 50MB uncompressed. Larger sites split their URLs across several files and list those in a sitemap index, which you submit instead.
Google ignores the priority and changefreq fields. It uses lastmod when the dates are consistently accurate, so only update it when the content really changes.
Why it matters
- Faster discovery. A sitemap tells crawlers about new and updated pages without waiting for them to find a link.
- Deep pages get found. Products, archives and old posts several clicks from the home page are easy for crawlers to miss.
- Better indexing data. Search Console can filter the Page indexing report by sitemap, so you can see exactly which of your important URLs are indexed and why the others are not.
- AI answers start from the index. AI Overviews, ChatGPT search and Copilot answer from pages their search engines have crawled. A page that has not been discovered cannot be cited.
Google says small sites with good internal linking may not need a sitemap. A sitemap still costs nothing, and most sites grow past that point.
Why it happens
- A custom or headless build where nobody added a sitemap route.
- The sitemap lives at another URL, such as
/sitemap_index.xml, and nothing points to it from robots.txt. - The generator was switched off, for example when an SEO plugin was removed or replaced.
- A migration moved the site to a new platform and the old sitemap URL now returns a 404.
- The file is blocked, by robots.txt, a login wall or a firewall rule that stops crawlers fetching it.
How to find a missing sitemap
- Open the usual URLs. Try
/sitemap.xml,/sitemap_index.xmland/wp-sitemap.xmlon your domain. - Check robots.txt. A
Sitemap:line with the absolute URL tells every crawler where the file is. If it is missing or points to a 404, fix it. - Check Search Console. The Sitemaps report lists every sitemap you submitted with its status. Success means Google read it; Couldn't fetch means it could not download the file.
- Check it in UpCrawler. When you add a site, UpCrawler looks for your sitemap and shows Found with the number of URLs it lists, or Not found, before the first crawl starts.
How to fix it
- Generate the sitemap from your CMS or framework so it updates itself whenever pages change. Never maintain one by hand.
- List only canonical, indexable URLs that return 200. Leave out redirects, error pages, noindex pages and URLs with tracking parameters.
- Use absolute URLs on the same protocol and host as your canonical tags.
- Reference it in robots.txt with
Sitemap: https://example.com/sitemap.xml. - Submit it in the Google Search Console Sitemaps report and in Bing Webmaster Tools, then watch the status change to Success.
Add app/sitemap.ts. Next.js serves it at /sitemap.xml:
import type { MetadataRoute } from 'next'
import { getPosts } from '@/lib/posts'
export default async function sitemap(): Promise<MetadataRoute.Sitemap> {
const posts = await getPosts()
return [
{ url: 'https://example.com', lastModified: new Date() },
...posts.map((post) => ({
url: `https://example.com/blog/${post.slug}`,
lastModified: post.updatedAt
}))
]
}
Build the list from the same data your pages render, so a new page is included automatically. Past 50,000 URLs, use generateSitemaps to split it into several files.
Since version 5.5, WordPress generates a sitemap at /wp-sitemap.xml with no plugin. SEO plugins replace it with their own: Yoast SEO serves /sitemap_index.xml and Rank Math does the same once its Sitemap module is on. Use one or the other, never both.
If no sitemap loads, check that Settings, then Reading, does not discourage search engines, and that no plugin has disabled sitemaps. Then visit Settings, then Permalinks, and save once to refresh the rewrite rules.
Shopify generates /sitemap.xml on your primary domain automatically. It is a sitemap index linking to separate files for products, collections, pages and blog posts. You cannot edit it, but you can submit it.
If Search Console cannot fetch it, check you submitted the primary domain rather than the myshopify.com address, and that the store is not password protected. To exclude a page, hide it with the seo.hidden metafield, which removes it from the sitemap and from search.
Let AI fix it, page by page.
Paste this prompt into AI with your project open. In UpCrawler, every affected page comes with a prompt like this, already filled in with its URL.
Generate an XML sitemap of canonical, indexable, 200-status URLs only, reference it from robots.txt and submit it in Search Console. Split into an index past 50k URLs or 50MB.
Frequently asked questions
Do I need an XML sitemap?
For most sites, yes. Google says a small site with good internal links can be found without one, but a sitemap speeds up discovery of new pages and gives you indexing data per URL in Search Console.
How do I submit a sitemap to Google?
Open Google Search Console, choose your property, go to Sitemaps, enter the sitemap URL and press Submit. Add the same URL to robots.txt so Bing and other crawlers find it too.
Why does Search Console say "Couldn't fetch"?
Google could not download the file. Usually the URL returns an error, is blocked by robots.txt or a firewall, or the sitemap was submitted on the wrong host. Open the URL in a private window to confirm it loads, then resubmit.
Should every page be in the sitemap?
Every page you want in search, and nothing else. Leave out redirects, error pages, noindex pages and duplicates, because a sitemap entry tells Google you want that URL indexed. If Google keeps choosing a different canonical, check that the sitemap lists the same URL as your canonical tag.
Share it with whoever runs your site’s SEO.