A broken WordPress XML file almost always comes down to a handful of simple problems: an unescaped ampersand, an unclosed tag, a plugin or permalink conflict, or a mismatch between the file you exported and the settings you’re importing with. Find which of those you’re dealing with, apply the matching fix below, and your file will parse cleanly again — usually without touching server code. This guide walks through the two most common scenarios (sitemap errors and failed imports) and how to repair a damaged file step by step.
Key takeaways
- Most “XML sitemap could not be read” errors in Google Search Console mean the URL returned something other than valid XML — not that the file is missing.
- XML is unforgiving: one unescaped & or a single missing closing tag fails the entire document, so a repair tool is often the quickest fix.
- WordPress import failures (“failed to import post”, “failed to import media file”) usually stem from how the export was made or server limits, not a corrupt file.
- Checking the file in your browser first tells you whether the problem is the XML itself or how Google or WordPress is reaching it.
What is a WordPress XML file, and why does it break?
WordPress relies on XML in two main places. First, XML sitemaps — machine-readable files that list your URLs, when they were last updated and how they relate to each other, helping search engines crawl your site efficiently. They’re not a ranking factor in themselves, but for larger or newer sites a well-structured sitemap can mean the difference between pages being indexed promptly or sitting in the crawl queue for weeks (QualityWordPress).
Second, the WordPress export/import system under Tools → Export and Tools → Import, which packages your posts, pages and media into a single XML file (often called a WXR file) for backups or site migrations.
XML is strict by design. A minimal sitemap entry looks like this:
<url>wrapping each entry- a required
<loc>element containing the full URL - an optional
<lastmod>date, which signals to Google that content was updated and can trigger a recrawl (QualityWordPress)
Because the format is so strict, a single mistake anywhere in the file — even one pasted-in curly quote — stops the whole document from parsing.
Why does Google Search Console say my XML sitemap could not be read?
When Search Console reports “Sitemap could not be read” or an XML sitemap error, it means Googlebot visited your sitemap URL (usually yoursite.com/sitemap.xml or yoursite.com/sitemap_index.xml) and either got no response, a non-XML response, or a page with broken XML code. This is different from a 404: the URL may exist but return something Google cannot parse as valid XML (Grasp WP).
Telltale signs
- “Sitemap could not be fetched” in Google Search Console
- The sitemap URL loads a blank page or a 404 in your browser
- The URL shows raw text or HTML instead of clean XML
The good news, according to Grasp WP, is that this error almost always has a clear cause and can be fixed without touching server code — as long as you know where to look.
How do I fix a WordPress XML sitemap error step by step?
1. Check the sitemap in your browser
Open the sitemap URL directly. If it loads as clean XML, the problem is likely how Google is reaching it (or a stale submission). If you see a blank page, a 404, or an error message, you’ve found your culprit.
2. Look for plugin or permalink conflicts
Sitemap errors frequently appear after switching plugins or changing your permalink structure (Grasp WP). If you’ve recently installed or changed an SEO plugin, two plugins may both be trying to serve the sitemap, or the old sitemap URL no longer exists. Deactivate all but one sitemap-generating plugin, then re-save your permalinks (Settings → Permalinks → Save) to flush the rewrite rules.
3. Re-submit in Search Console
Once the URL loads correctly in your browser, remove and resubmit the sitemap in Google Search Console, then give it time — Google doesn’t always recheck instantly.
How do I repair a broken or invalid XML file?
If you’ve opened your XML file and it refuses to parse, an automated repair tool can save a lot of hunting. Online XML repairers detect the most common mistakes and rewrite your input into well-formed XML (xml-indent.com). The mistakes they typically fix are:
- Unescaped ampersands — a bare & in a URL becomes &, while valid entities are left untouched
- Unquoted attribute values —
<a href=x.html>becomes<a href="x.html"> - Unclosed tags — elements left open at the end of the document are closed in the correct nesting order
- Smart quotes — “curly” quotes pasted from word processors are replaced with straight quotes in markup
Paste your broken XML into the tool, let it repair and re-indent the file, then validate the result before using it again. Be aware that genuinely ambiguous problems — such as a closing tag that doesn’t match any open tag, or a tag left open in the middle of the document — are reported rather than guessed, so your data isn’t silently mangled (xml-indent.com). For those, you’ll need to find the reported line and fix it by hand.
One habit worth building: if you edit any XML by hand, avoid pasting text from Word or Google Docs. Curly quotes and stray ampersands from word processors are among the most common ways a perfectly good file gets broken.
Why does my WordPress XML import fail, and how do I fix it?
Sitemap problems get most of the attention, but the other frequent XML headache is a failed import. A real example from the WordPress.org support forums: a user exported their blog using Tools → Export with the “all content” option, then imported the file the same way — and only the users came through. Everything else showed “failed to import post” and “failed to import media file” errors (WordPress.org).
Questions to ask when an import fails
The moderator in that thread asked exactly what you should check yourself:
- Which route did you take for the export? The built-in Tools export and third-party export plugins produce different files, and mixing them with the wrong importer causes problems.
- How are you doing the import? Use the matching importer — the built-in WordPress importer for a Tools export.
- What is the exact error message? “Failed to import post” tells you far more than a generic failure notice, and the specific item name can help you see what went wrong.
Practical fixes for failed imports
- If the import reports partial failures, re-run it and check whether the same items fail again — the exact error messages will tell you what still needs fixing.
- Check that the source site is still online, since the importer fetches media files from their original URLs.
- If imports keep failing, check whether the error points to a parsing problem in the XML file itself, and validate or repair the file before trying again.
- Validate the XML file itself with a repair tool if the importer reports a parsing error rather than per-item failures.
How do I stop WordPress XML problems from coming back?
Prevention is mostly about tidiness. Keep to one sitemap plugin so nothing fights over /sitemap.xml, re-save permalinks after any structural change, and resubmit your sitemap in Search Console after major updates so Google picks up your new <lastmod> dates promptly.
For export files, always export and import through matching tools, and open the file briefly before relying on it as a backup — a file that doesn’t parse isn’t a backup. If you build content regularly, a quick XML validation after any manual edit takes seconds and catches the classic mistakes before they cause downtime.
And if your XML work is part of prepping a food or drinks blog for search — think recipe index pages and seasonal cocktail round-ups — a healthy sitemap is what gets those new posts crawled quickly. It’s the unglamorous half of getting your content seen; the fun half is what you put on the page (or in the tray).
FAQ
Is an XML sitemap a ranking factor?
No. It’s a map that helps crawlers work more efficiently rather than a ranking signal in itself, though it can speed up indexing — which matters most for larger or newer sites with fewer inbound links (QualityWordPress).
Where do I find my WordPress sitemap URL?
Most setups serve it at yoursite.com/sitemap.xml or yoursite.com/sitemap_index.xml. Your SEO or sitemap plugin’s settings page will confirm the exact address (Grasp WP).
Can I fix broken XML without installing anything?
Yes. Free browser-based repair tools fix unescaped ampersands, unquoted attributes, smart quotes and unclosed tags, and run entirely in your browser so nothing is uploaded (xml-indent.com). Ambiguous errors are reported rather than guessed, so you can fix those manually.
Why did only some of my content import from the XML file?
Common causes include using an importer that doesn’t match your export method, media files whose original URLs are no longer reachable, or server limits cutting the import short. Check the exact error messages, confirm the source site is live, and retry the import — per-item failures often resolve on a second run (WordPress.org).
Should the lastmod date be in my sitemap?
It’s optional but useful. It tells Google when content was last updated, which can trigger a recrawl for pages that have been improved (QualityWordPress). Just make sure it reflects genuine updates.
Sources
- QualityWordPress — WordPress XML Sitemaps: Find, Fix and Submit
- Grasp WP — XML Sitemap Error in WordPress: The Ultimate Troubleshooting Guide
- XML-Indent — XML Repair & Fixer
- WordPress.org Support — XML file error
Once your sitemap is healthy and your imports run clean, you’ve done the technical groundwork — now get back to the content your readers actually came for.
