"Sitemap could not be read" in Google Search Console

You submitted your sitemap and Search Console says it could not be read, or "Couldn't fetch". Sometimes this is only a delay. Often it is a real fault you can see yourself in a minute.

What to do, in order

1. Open the sitemap address in a private window. It must load as plain XML, not a login page, a 404, or your home page. If it redirects anywhere, submit the final address instead.
2. Check the status code. Run curl -sI https://yourdomain.com/sitemap.xml. You want 200. A 403 usually means a firewall or security plugin is blocking Google.
3. Check robots.txt. It must not block the sitemap path. A line like Disallow: / blocks everything.
4. Check the content type and the first line. The file should start with <?xml, with nothing before it. A blank line or a stray space from a plugin breaks the parse.
5. Wait two or three days, then resubmit. On new properties "Couldn't fetch" often means Google has not tried yet. If steps 1 to 4 pass, this is the likely answer.

If it still fails, send me the address and I will tell you which step is broken.

Want the rest of your site checked after it is back? Run a free 40-point check at tinkeraudit.com.