AI, Development & Tech News

Chrome 158 stops XSLT: WordPress sitemaps appear as source code

261121 chrome xslt wordpress sitemap cover image
Skip to table of contents
Contents 4 sections
  1. What does Chrome 158 change for XML pages?
  2. What is WordPress doing with the sitemap stylesheets?
  3. What this means for you
  4. Sources

Since version 158, Chrome no longer executes XSLT stylesheets. The Chrome team released the version as a stable release on November 17, 2026. Until now, WordPress has attached such a stylesheet to its sitemaps, which displays the files in the browser as a readable overview. If you open the sitemap in Chrome 158, you will see source code instead.

According to the description of the WordPress commit, only the display in the browser stops working; the sitemap remains an XML file with addresses. Clients and colleagues who open it directly in the browser quickly mistake this for an error.

What does Chrome 158 change for XML pages?

Chrome removes two features: the JavaScript interface XSLTProcessor and the xml-stylesheet processing instruction, with which an XML file points to an XSLT stylesheet. The Chrome team cites security problems in the old libxslt library as the reason.

According to Chrome for Developers, XSLT is used in only about 0.02 percent of page views at all, and Firefox and WebKit also want to remove XSLT. Exceptions via a policy for corporate computers or the Origin Trial test program run until Chrome 176 on August 17, 2027; after that, XSLT is switched off for everyone.

XML with CSS is not affected: the xml-stylesheet instruction is still allowed for CSS. The Chrome team also explicitly names RSS and Atom feeds as a use case, because many of them are displayed as a readable page via XSLT. When opening such a file, Chrome shows a warning with a link through which you can search for an extension that adds XSLT support back.

What is WordPress doing with the sitemap stylesheets?

The WordPress core already reacted in October. On October 3, 2026, a commit removed the XSL stylesheets of the sitemaps from the development version, which is now available as a release candidate of WordPress 7.2.

Von Commit bis Chrome 176
Termine zu XSLT und den WordPress-Sitemaps laut Chrome for Developers und WordPress-Core
  1. 3. Oktober 2026Ein Commit entfernt die Sitemap-Stylesheets aus WordPress
  2. 17. November 2026Chrome 158 führt kein XSLT mehr aus
  3. 8. Dezember 2026WordPress 7.2 erscheint laut Zeitplan
  4. 17. August 2027Ausnahmen für Unternehmen und Origin Trial enden mit Chrome 176
Der 8. Dezember ist der Termin im Release-Zeitplan des Core-Teams, kein fester Erscheinungstag.
Quellen: Chrome for Developers, WordPress Develop, Make WordPress Core

The commit justifies the step with the phasing out of client-side XSLT in browsers and leaves the presentation to the browser in the future. Among other things, it marks the class WP_Sitemaps_Stylesheet and the filters wp_sitemaps_stylesheet_url, wp_sitemaps_stylesheet_index_url, wp_sitemaps_stylesheet_content, wp_sitemaps_stylesheet_index_content and wp_sitemaps_stylesheet_css as deprecated. The return value of the filters is ignored; they only generate notices about deprecated functions.

According to the core team's schedule, WordPress 7.2 is due to be released on December 8, 2026. Until then, the sitemaps in released versions continue to include the stylesheet, and Chrome shows source code. Sitemaps from SEO plugins follow their own rules. Whether they use an XSLT stylesheet can be seen in the file's source code.

What this means for you

Open your sitemap yourself once in Chrome 158 and look at the source code. If there is a line with xml-stylesheet and type="text/xsl", the file includes an XSLT stylesheet. This applies to the WordPress core sitemap as well as to that of a plugin.

Also check in Google Search Console under Sitemaps whether your file shows the status "Success". This way you can see that it can be retrieved regardless of how it is displayed in the browser.

If you look after client sites, a brief advance notice helps, because the source code looks like a defect. If your theme or plugin uses one of the filters mentioned, notices will appear in the debug log after updating to 7.2 when WP_DEBUG is enabled.

Chrome 158 was released on November 17, 2026; the WordPress commit dates from October 3, 2026.

Sources

Comments

Register and comment.

Continue reading

You might also like

View all articles →