Chrome 158’s scheduled XSLT removal took effect on November 17, 2026, and Search Engine Journal reported that the rollout began that day. WordPress sitemaps that rely on XSLT to create a human-readable browser view may now appear as raw XML in Chrome. The change affects how the sitemap is displayed; Chrome still supports XML and CSS styling for XML. Chrome’s XSLT deprecation documentation

XSLT is a language for transforming XML into another format, often a formatted page. Chrome’s change removes the browser’s XSLTProcessor API and its support for XML processing instructions that invoke XSLT, such as <?xml-stylesheet type="text/xsl" ...?>.

Why a WordPress sitemap may look different

A sitemap is an XML file listing URLs for search engines. WordPress core and SEO plugins have used XSLT to turn that data into a table that people can browse. If a sitemap’s presentation depends on browser-side XSLT, Chrome may show the underlying XML without that formatted view, as Search Engine Journal reported.

Search Engine Journal also reported that crawlers read the sitemap XML directly and that this browser presentation change does not affect crawling, indexing, or rankings. In Google Search Console, the practical check is the submitted sitemap’s processing status—not whether Chrome displays it as a polished table.

If a sitemap looks different in Chrome, check its processing status in Google Search Console before changing the site’s sitemap setup.

How to check Google’s sitemap processing

In Google Search Console, select the relevant property, then open Indexing > Sitemaps. Find the submitted sitemap and review its status, last-read date, and discovered URL count. Search Engine Journal reports that a Success status means Google parsed the sitemap without an error.

What XML and CSS still do in Chrome

The removal is specific to browser-side XSLT: XML remains supported, and Chrome continues to support CSS styling for XML. A CSS-based view can therefore style XML without using the removed XSLT mechanisms.

Styling does not necessarily reproduce every feature of an XSLT-generated page. A Yoast developer issue describing a proposed CSS migration says its CSS-only view would not make XML URLs clickable or dynamically add a URL-count sentence, reformat last-modified dates, or show image counts for each row. Those are limitations described for that proposal. Yoast developer issue on the proposed CSS migration

Chrome cites security concerns in aging XSLT-processing libraries and low usage as reasons for the change. Its documentation puts XSLT use at about 0.02% of page loads and use of XSLT processing instructions below 0.001%. Chrome’s schedule allows Origin Trial participants and enterprise-policy users to retain the exceptions through Chrome 176, with their scheduled end on August 17, 2027.

Search Engine Journal reported on November 19, 2026, that WordPress 7.2 was scheduled for December 8, 2026, and expected to remove WordPress Core’s sitemap XSLT stylesheet.