You submitted a sitemap and Search Console reports it as unread, errored, or read with far fewer URLs than it contains. The causes are few and each produces a distinct symptom.
For what a sitemap is and how to structure one, see XML sitemaps.
Could not fetch
Search Console cannot retrieve the file at all.
- The URL is wrong, or has changed since submission.
- It is blocked in robots.txt — a disallow rule matching the sitemap path.
- It returns a 404, a redirect, or requires authentication.
- The server is slow enough that the fetch times out.
Fetch the sitemap URL yourself, signed out, and confirm it returns 200 with XML. Most fetch failures are visible immediately this way.
Fetched but showing errors
- Invalid XML — usually a stray character, an unescaped ampersand, or a PHP notice printed above the XML declaration.
- URLs from another domain, including http entries on an https site. A sitemap may only contain URLs from its own domain.
- Too large — over 50,000 URLs or 50MB uncompressed. Split into a sitemap index.
- Wrong content type served by the server.
An unescaped ampersand in a product URL is a common cause on stores and breaks the whole file rather than one entry.
Read, but few URLs indexed
This is usually not a sitemap problem at all, and it is where most of the confusion sits. The sitemap was read successfully; the URLs in it are not being indexed for their own reasons.
- URLs blocked in robots.txt or carrying noindex.
- URLs canonicalising elsewhere, so the canonical is indexed instead.
- Pages judged not worth indexing. See pages not indexed.
- A large site simply not yet fully crawled.
A sitemap is a suggestion about what exists, not an instruction to index. Submitting it again does not change any of the above.
Keeping it clean
- Only canonical, indexable URLs. Never include redirects, 404s, noindexed pages or non-canonical variants.
- Absolute URLs matching your preferred form exactly — protocol, hostname, trailing slash.
- Accurate lastmod values, or none at all. Wrong values are worse than absent ones.
- Declare it in robots.txt as well as submitting it.
- Regenerate it after a migration. Stale sitemaps pointing at old URLs are a common post-launch fault.
Frequently asked questions
How often is a sitemap re-read?
Periodically, and more often on sites that change frequently. Resubmitting does not force it.
Do I need one?
A small well-linked site can manage without. Large sites, new sites and sites with weak internal linking benefit meaningfully.
Should noindexed pages be listed?
No. It is a direct contradiction — listing a page as worth crawling while telling crawlers not to index it.
Why does the indexed count differ from my URL count?
Because indexing is a judgement made per URL. A gap is normal; a very large gap points at the causes above.
Consulting CTA
If your sitemap is being read and pages are still not indexed, book an SEO consultation.