Why doesn’t Google recognize my sitemap?

Google usually ignores a sitemap because it cannot fetch it or cannot read it: the URL returns an error or a redirect, the file is blocked or behind a login, or the XML is invalid. If the Sitemaps report in Search Console shows “Couldn’t fetch” or errors, the problem is almost always the file or the server, not Google.

A sitemap is a hint, not a command. Even a sitemap with status “Success” does not mean that every listed URL will be crawled or indexed. Google decides that per page.

Why does Search Console not accept my sitemap?

• Not reachable. The sitemap URL returns 404, 5xx, a redirect chain or a login page. Googlebot must be able to fetch the file directly without logging in.
• Blocked by robots.txt. If a robots.txt rule blocks the sitemap URL, Google cannot read it.
• Invalid format. Typical errors are a missing or wrong namespace, unescaped characters such as a plain “&” in URLs, or a file that is not UTF-8 encoded.
• Too large. A single sitemap may contain at most 50,000 URLs or 50 MB uncompressed. Larger sites need several sitemaps, optionally combined in a sitemap index file.
• Wrong property or location. A sitemap submitted for https://www.example.com/ cannot list URLs on http:// or without www. Without submission in Search Console, a sitemap only covers URLs in its own directory and below.
• Relative URLs. Google expects absolute URLs such as https://www.example.com/page/, not /page/.

Our robots.txt and sitemap checker shows whether both files can be reached and fit together.

How do I fix the sitemap step by step?

1. Open the sitemap URL in a private browser window. It must load directly as XML, without redirect and without login.
2. Test with URL Inspection. Enter the sitemap URL in URL Inspection in Search Console and run a live test. “Page fetch: Successful” means Googlebot can reach it.
3. Check robots.txt. Make sure no rule blocks the sitemap. You can also list the sitemap there with a Sitemap: line; this is optional but helpful.
4. Submit in the Sitemaps report. Enter the full URL under “Add a new sitemap”. Google fetches the sitemap right away. You need owner permission on the property to submit.
5. Read the details. If the status is not “Success”, click the row. The details page names the error, for example a parsing problem or an unsupported format.
6. Resubmit after the fix. If a fetch keeps failing, Google retries for a few days and then stops. After fixing the problem, submit the sitemap again.

What belongs in a good sitemap?

• Only canonical, indexable URLs. No redirects, no error pages, no pages with noindex, no parameter duplicates.
• A correct lastmod date. Google uses lastmod only if it is consistently and verifiably accurate. It ignores priority and changefreq.
• Automatic updates. Let your CMS or SEO plugin generate the sitemap so that new and deleted pages are reflected immediately.

Note that the Sitemaps report only shows sitemaps submitted there or via the API, not sitemaps Google found through robots.txt. If you want to track errors, submit the sitemap explicitly. If individual pages stay unindexed despite a working sitemap, see our FAQ on why indexing new pages takes long.

Check sitemaps first with a live test in URL Inspection, then submit them in Search Console and only list canonical URLs that return status 200.

Sources

• Google Search Central: Build and submit a sitemap
• Search Console Help: Sitemaps report
• Google Search Central: What is a sitemap

Is your sitemap still rejected, or are important pages missing from the index? We check sitemap, robots.txt and indexing in Search Console and fix the cause. Book a free intro call or read more about our search engine optimisation.