AI NewsInfrastructureAnnouncement
Chrome 158 drops XSLT and WordPress sitemaps now show as raw XML
Chrome 158 released on 17 November and turned off XSLT. The visible result for an SEO team is that a WordPress sitemap now renders as raw XML in the browser. Crawlers still read it.

Why it mattersAn SEO team seeing a raw XML sitemap this week has not broken anything. The site is fine. Showing a client the Search Console coverage number is the fastest way to prove it.
Chrome 158 reached stable on 17 November 2026 and turned off XSLT. The Chrome team's deprecation page names the exact Chrome build and the exact date. The authors are Mason Freed and Dominik Röttsches. The removal covers two APIs. One is the XSLTProcessor class. The other is the <?xml-stylesheet?> processing instruction. Both let a browser turn XML into HTML on the client.
The visible result for an SEO team is simple. An XML sitemap now renders as raw XML markup in a browser window. The nice table view is gone. WordPress sitemaps are the common case. The core WordPress sitemap carries an XSL stylesheet to style the XML for a human reader.
Why Chrome removed it
The Chrome team gives two reasons on the page. The first is security. The libraries that do XSLT in Chrome include libxslt. The Chrome team calls them "complex, aging C/C++ codebases" with a history of buffer overflows. A buffer overflow in the browser can lead to arbitrary code execution. The second reason is use. Chrome measured that about 0.02% of page loads use XSLT at all. Less than 0.001% of page loads use XSLT processing instructions.
Chrome 142 began printing a console warning on 28 October 2025. Chrome 143 added an official deprecation message on 2 December 2025. Chrome 158, the stable release this week, removes the feature. An Origin Trial and an Enterprise Policy give a site two ways to keep XSLT running. Chrome lists both options expiring in Chrome 176 on 17 August 2027.
What this changes for a sitemap
Nothing changes for a crawler. Googlebot, Bingbot and the AI retrieval crawlers read the XML directly. They never ran XSLT in a browser. Search Engine Journal says the same in its 19 November 2026 write-up by Dan Taylor: crawlers avoid browser-side stylesheets, so indexing, crawl rate and rankings stay the same.
The change is only in what a person sees when they open the sitemap URL. The raw XML looks broken next to the old pretty table. On an audit call, a client who opens their sitemap in Chrome 158 may now call it a bug.
What to do this week
The Chrome page lists three migration paths that keep the pretty view. Serve the sitemap from a server-side transform that returns HTML. Load the Saxonica JavaScript XSLT library on the page, which runs XSLT 3.0 in the browser. Install the Chrome team's own WebAssembly polyfill, which keeps old XSLT files working.
The faster answer, for a team that is not running a special sitemap workflow, is to leave the sitemap alone. The crawlers still read it. The Search Console Index Coverage report shows the same green "Success" badge it showed last week. A short note in the client's audit log, pointing at this Chrome release, is enough.
Source
This item was written by an AI system from the linked source. Reveneau is responsible for what it publishes.
Get AI News in your inbox
New developer tools, model and agent releases, and how teams are actually using them to release software. Short, and only when there is something worth reading.

