Seeing “Your Sitemap appears to be an HTML page” in Google Search Console is one of the more common sitemap errors website owners run into, and it almost always comes down to one core issue: Google’s crawlers expect your sitemap in a specific format, and something on your site is serving it incorrectly. Here’s what causes it and how to actually fix it.
What This Error Actually Means
A sitemap is a file that lists all the important content on your website — pages, videos, files, and how they relate to one another — helping search engines find, crawl, and index everything more efficiently. Google expects sitemaps in one of a handful of specific formats, with XML being by far the most common, though RSS, Atom, KML, or plain text files are also accepted. HTML isn’t on that list. When Google’s crawler requests your sitemap URL and receives an HTML page instead of properly formatted XML, it flags the mismatch with this exact error, since it can’t parse HTML the way it parses a structured sitemap file.
The Core Cause: Wrong File Format
The most straightforward explanation is also the most common one: your sitemap file is genuinely in the wrong format. If you’re submitting a URL that serves an HTML page rather than a real XML sitemap, Google will report this error every time, regardless of what the page actually contains.
A Sneakier Cause: Prettified XML That Looks Like HTML
Sometimes the sitemap actually is XML under the hood, but something makes Google mistakenly read it as HTML. Some sitemap generators create a version of the sitemap specifically formatted to be human-readable in a browser, using stylesheets that make raw XML display in a more polished, HTML-like way. The underlying source code is still XML, but browsers render it to look sort-of like HTML. This gets particularly messy on platforms that append “.html” to the end of URLs as a legacy SEO feature — when Google discovers “.html” at the end of a sitemap URL paired with this “prettified” XML rendering, it can produce a false negative, incorrectly concluding the file isn’t real XML when it actually is.
Caching Plugins Can Corrupt the File
If you’re on WordPress, caching plugins are a frequent culprit. These plugins can create an archived, cached copy of your XML sitemap that ends up served in the wrong format, causing Google to see something other than the live, correctly formatted file. If you’re using a plugin like WP Rocket, there’s typically an option in the advanced settings to exclude specific URLs from caching — adding your sitemap URL to that exclusion list prevents the cache from interfering with how Google sees the file.
How to Diagnose the Problem
Start by visiting your sitemap URL directly in a browser and checking for any strange error codes or unexpected content, since an error at the sitemap URL itself will cause Google to interpret it as an HTML page rather than valid XML. From there, log into Google Search Console, select your property, go to the “Index” section, and click “Sitemaps” to see the status of your submitted sitemap and any specific error details Google provides.
Beyond Search Console itself, dedicated XML sitemap validator tools let you paste in your sitemap URL for a more detailed check, flagging specific formatting problems along with recommendations for fixing them.
How to Fix It
The fix depends on what’s actually causing the mismatch in your specific case:
- If your sitemap genuinely isn’t XML, install a sitemap-generating plugin (Rank Math is a commonly recommended option for WordPress) to automatically create a properly formatted XML sitemap, then submit that new file’s URL — typically something like
/sitemap_index.xml — through Search Console.
- If a caching plugin is interfering, exclude your sitemap URL from caching in your plugin’s settings, or temporarily disable caching plugins one at a time using a troubleshooting mode to isolate which plugin is causing the conflict.
- If your platform appends “.html” to URLs, check whether your sitemap plugin has a “prettified” or human-readable display option, and consider disabling it or adjusting your URL structure so Google doesn’t misread the file extension.
- Make sure your sitemap URL is consistent everywhere it’s referenced — in Search Console, in your robots.txt file, and in any SEO plugins — since discrepancies between these can create confusion for both search engines and site administrators.
When to Contact Your Host
If you’ve worked through the common fixes and the error persists, reaching out to your hosting provider’s support team is a reasonable next step, since server-level configuration issues can sometimes interfere with how sitemap files are served, even when the file itself is correctly formatted on your end.
Join The Discussion
Have you run into this error on your own site, and what ended up being the actual cause — a caching plugin, a formatting quirk, or something else entirely? Did switching sitemap plugins or adjusting your caching settings resolve it right away, or did it take some troubleshooting? Share your experience, fixes, or questions about sitemap issues below.
