Chrome 158 Changes How WordPress Sitemaps Appear
Chrome 158 no longer supports XSLT, so WordPress sitemaps may appear as raw XML. Google Search Console can help verify that crawlers still read them.
WordPress sitemap pages may look different in Chrome 158 following the browser’s removal of XSLT support. Instead of a formatted view, visitors may see the sitemap’s raw XML. That change in appearance can make a working sitemap seem as though something has gone wrong.
The browser’s presentation of a sitemap and whether crawlers can read it are separate issues. The reported change concerns XSLT, which was used to display sitemap information in a more human-friendly format in the browser. Without that formatting, the underlying XML may be shown directly.
For site owners and marketing teams, seeing raw XML in Chrome is not, by itself, a reason to rebuild a sitemap or make technical changes. The visual result in a browser does not establish that the sitemap has stopped working. Making adjustments solely to restore the previous display could mean spending time on an issue that does not affect crawler access.
Google Search Console is the recommended place to check whether Google can still read a sitemap. Use it to verify crawler access rather than relying only on how the sitemap looks when opened in Chrome. This helps distinguish a browser display change from a problem with the sitemap itself.
The practical response is to treat the raw XML view as a presentation change unless Search Console indicates that crawlers cannot read the sitemap. If the tool confirms that Google can access it, the changed appearance alone does not call for a fix. Teams can then avoid unnecessary troubleshooting based only on what they see in the browser.
What this means for marketers: Check sitemap access in Google Search Console before requesting changes or investigating a possible technical issue. Chrome’s raw XML display is not, on its own, evidence that a WordPress sitemap is broken.
This is an original summary published for informational purposes; all rights to the underlying reporting belong to the source.
Put these insights into action
Running campaigns needs clean accounts: freshly registered, verified, delivered the second you pay — with a 48-hour warranty and USDT checkout.