Sitemap errors and how to fix them
Start with the status in Search Console's Sitemaps report. Couldn't fetch means Google could not get the file at all, usually because of a wrong address, a server problem or a robots.txt block. Has errors means Google read it but found problems such as invalid dates, bad addresses or addresses from another domain. Fix the cause, then check the status again.
Start with the status
Open the Sitemaps report in Google Search Console. Each submitted sitemap shows one of three statuses:
- Success: fetched and read without errors. Your job here is checking the content, not fixing errors.
- Has errors: fetched, but one or more problems were found. Click into the sitemap to see which.
- Couldn't fetch: Google could not retrieve the file at all.
If you also use Bing Webmaster Tools, compare. When both search engines report a problem, it is almost certainly in the file or the server. When only one does, check how and where the sitemap was submitted to that one.
Couldn't fetch: Google never read the file
Google lists several possible causes. Work through them in order:
- Wrong address. Open the exact submitted address in a private browser window. If you get a not found page, the sitemap has moved, often after a redesign or plugin change. Submit the correct address and remove the old one.
- Blocked by robots.txt. Open yourpractice.com/robots.txt and look for a rule blocking the folder the sitemap lives in. This can happen when settings from a staging site carry over to the live one.
- Server problems. If the file opens for you but slowly or only sometimes, Google may be getting errors. Your host can check the server logs.
- Low crawl demand. For a small or new site, Google may simply not have fetched it yet. Give it a few days before treating it as broken.
A manual action against the site can also cause it. Manual actions are listed separately in Search Console, so check there if nothing else explains the problem.
Does ChatGPT recommend your practice?
The Surge Score measures five things about your practice website: how often ChatGPT, Gemini and Perplexity recommend you, your PageSpeed, your structured data, your indexing and your reviews, each with its evidence and date. Free.
Has errors: what the common messages mean
When Google can read the file but finds problems, it names them. Errors you may see include:
- URL not allowed: the sitemap lists addresses on a different domain, or above the folder the sitemap sits in. Typical causes are an old domain, a www mismatch or a sitemap stored in a subfolder.
- Invalid URL: an address contains spaces, quotes or characters that are not properly escaped. An ampersand in an address, for example, must be escaped in XML.
- Invalid date: a lastmod value is not in W3C Datetime format. Valid examples are 2026-11-14, or a full date and time with a time zone. See lastmod.
- URLs not followed: addresses redirect, sometimes through several hops, or are relative paths instead of full addresses. List the final address, starting with https.
- Too many URLs: more than 50,000 addresses in one file. Split it and use a sitemap index.
- Nested sitemap indexes: an index lists another index. An index may list only sitemaps.
- Missing XML tag or incorrect namespace: the file does not follow the sitemap standard, usually a sign of a hand made file or a broken generator.
Most of these trace back to how the file is generated, so the fix belongs with whoever built the site.
Problems the report will not flag
A sitemap can show Success and still be wrong. The Sitemaps report checks that the file can be read, not whether you listed the right pages. Look for these yourself:
- Pages marked noindex, which tells Google not to index the very pages you listed
- Addresses that redirect to other pages, often left over from a redesign
- Pages that return not found, such as departed providers or discontinued services
- Duplicate versions, such as http and https, or with and without a trailing slash
- Staging or development addresses from your agency
- Thank you pages and portal logins
The Page indexing report helps here. Filter it to your sitemap and look at why listed pages are not indexed: a noindex tag, a redirect, a not found error. Each points to an entry that should not be in the sitemap. The status that needs the most judgment is covered in crawled, currently not indexed.
Fix it, then confirm the fix
- Fix the cause in the website or with your vendor, rather than editing the sitemap file by hand, unless the file really is hand made.
- Open the sitemap in a browser and confirm the problem is gone.
- In the Sitemaps report, you can submit the same address again to prompt Google to fetch the corrected file.
- Check the status again after a few days.
- For page level problems you fixed, use Validate fix in the Page indexing report. Google says validation typically takes up to about two weeks, and sometimes longer.
Record what you changed and when. If the same error comes back, the cause is in whatever generates the file, not in the file itself.
When to call your developer
You can fix many page level problems yourself on most platforms: unpublishing a departed provider's page, removing a noindex setting on an important page, deleting a page that should redirect. The sitemap updates itself afterwards.
Call your developer for anything in the file's structure: invalid dates, escaping problems, namespace or tag errors, nested indexes, a staging domain, or two plugins producing competing sitemaps. Call them, too, after any redesign where the old sitemap is still being served. Give them the exact error name and an example address from the report; it saves an hour of guessing. Launch day is the best time to catch these, so add sitemap checks to your launch day checks.
Checklist
- Every submitted sitemap shows Success in Search Console
- Old or wrong sitemap addresses are removed from the report
- robots.txt does not block the sitemap or important pages
- No sitemap entry redirects, returns not found or is marked noindex
- All addresses use your live domain and https
- Dates are in a valid W3C Datetime format
- Fixes are confirmed with Validate fix and a recheck of the report
Frequently asked
My sitemap says Success but my pages are not indexed. Why?
Success only means Google read the file. Whether each listed page is indexed is a separate decision. Filter the Page indexing report to your sitemap to see the reason given for each page that is not indexed.
Are sitemap errors hurting my rankings?
Not directly. They can stop Google from using your sitemap to find pages, which matters most for new or poorly linked pages. Fix them, but do not expect a ranking jump from the fix alone.
What does soft 404 mean for a page in my sitemap?
Google thinks the page looks like a not found page even though the server says it is fine, for example a page that only says a provider or service is no longer available. Either give the page real content, or redirect or remove it and take it out of the sitemap.
How long until errors clear after a fix?
The sitemap status updates the next time Google fetches the file, which is often within days. Page level fixes tracked with Validate fix typically take up to about two weeks, according to Google, and sometimes longer.
Sources
- Sitemaps report, Search Console Help (Google)
- Page indexing report, Search Console Help (Google)
- Sitemaps XML format, sitemaps.org
- Build and submit a sitemap, Google Search Central
- Manage your sitemaps with sitemap index files, Google Search Central
- How Google interprets the robots.txt specification, Google Search Central
Book a strategy call with the team.
Twenty minutes. We'll walk through the specific opportunities in your market and what a MedPracticeGrowth engagement would look like for your practice.