Check the file and Google’s last sitemap read before changing the site. Chrome 158 shipped on 17 November 2026 and stopped running XSLT on Stable for everyone except Origin Trial and Enterprise Policy participants. XSLT can turn XML into a formatted page for people. Chrome’s change can remove that formatting while leaving the XML in place. It does not prove Google can fetch or parse your sitemap.
Check what the sitemap URL returns
Open the exact sitemap URL your site submits, such as https://example.com/sitemap.xml. In Chrome, you can also use view-source: before the URL to inspect the source. A pretty browser view proves nothing about sitemap validity either way. If you see raw text, look for a <urlset> or <sitemapindex> root and the page URLs you expect. This is a quick visual check, not validation.
The first command shows the status line and Content-Type; the second shows the first lines, where you look for an <?xml-stylesheet ...?> line and the <urlset> or <sitemapindex> root. A 404, server error, sign-in page or security challenge needs investigation even if the browser displays something that resembles XML.
curl -sI https://example.com/sitemap.xml
curl -s https://example.com/sitemap.xml | head -5
If the file points to an XSL stylesheet, Chrome’s XSLT removal guidance explains why its formatted view may disappear. Chrome is removing the browser transformation, not XML itself. Do not assume every raw-looking sitemap once used XSLT. If a plugin or CMS generates your sitemap, check for an xml-stylesheet line and ask the vendor whether it plans to change the browser view. That vendor question is a practical suggestion, not a Google statement.
Chrome says the xml-stylesheet instruction still works with type="text/css" and offers an XSLT polyfill. Those are display choices for people, not an SEO change.
What I checked on my own site
At 13:32 IST on 21 November 2026, I fetched https://seowithvishnu.com/sitemap.xml. It returned HTTP 200 with Content-Type: application/xml. Its root was <urlset> and it contained 40 <url> entries. It had no <?xml-stylesheet ...?> line, so there was nothing for Chrome to stop running on this sitemap. I also fetched https://seowithvishnu.com/robots.txt: it returned HTTP 200, Content-Type: text/plain, and contained Sitemap: https://seowithvishnu.com/sitemap.xml. These are responses at one point in time, not Search Console results.
Check what Search Console read
Open the Sitemaps report in Search Console for the correct property. Find the exact submitted sitemap URL. Record Status and Last read, including the date you checked the report. Google’s Sitemaps report help says Success means Google fetched and read the sitemap without errors. Couldn’t fetch means Google could not retrieve it; Has errors means Google fetched it but encountered errors. Open the row for details before editing the file. Last read appears only if Google could fetch the file.
The report lists sitemaps submitted through Search Console or its API. A sitemap discovered only through robots.txt will not appear there unless you also submit it in the report. You can submit it to track Google’s status and errors. An absent row is not proof that Google rejected the sitemap.
Keep sitemap health separate from page indexing
Google says a sitemap helps it discover URLs, but submission does not guarantee crawling or indexing. Search Console’s Discovered pages count is URLs parsed from the sitemap, not a count of indexed pages. To check one page’s status, inspect that page’s URL separately. If it was crawled but not indexed, use the crawled but not indexed guide for the next check. If several pages need triage, use the Search Console diagnosis guide to choose a report and next action.
If the XML is valid and Google has read it, changing sitemap markup to restore a pretty browser display is not an indexing fix. A separate human-friendly view may help your team review URLs, but that is a usability choice. If you have a real fetch or parsing error and need help isolating it, bring the report detail and sitemap URL to an SEO consulting discussion.
Reviewed 21 November 2026. Sources: Chrome for Developers XSLT removal guidance; Google Search Console Sitemaps report help; Google Search Central sitemap guidance.
