Avoid unnecessary WordPress sitemap fixes when Chrome drops XSLT, and use Google Search Console to verify that raw XML still works for search crawlers.
On Nov. 17, Chrome 158 rolls out to the majority of desktop and mobile users and drops support for client-side XSLT (Extensible Stylesheet Language Transformations).
For years, WordPress core and major SEO plugins, including Yoast SEO, Rank Math, and All in One SEO (AIOSEO), have referenced an .xsl stylesheet inside their XML sitemaps. When a person opened a sitemap URL in a browser, Chrome executed that XSLT file to transform the underlying XML code into a clean, clickable HTML table.
Without XSLT support, opening a WordPress sitemap in Chrome 158 displays raw, unstyled XML markup alongside a browser console and page warning.
Search engines do not use XSLT. Googlebot, Bingbot, and other web crawlers fetch and parse the raw XML nodes (<loc>, <lastmod>) at the source. Crawlers avoid browser-side stylesheets, meaning indexing, crawl efficiency, and search rankings remain unaffected.
Because Chrome 158 lands while Google’s November core update, which began on Nov. 10, is still rolling, site owners and clients checking their domains during routine ranking audits may panic when they see raw XML in place of the familiar formatted table.
Depending on your site configuration, WordPress serves its sitemap index from one of two primary URLs:
If you open either URL in Chrome 158 or a newer release, seeing a wall of XML tags confirms the browser skipped the XSLT stylesheet, not that the sitemap file is corrupt or broken.
Source link







