Open a styled XML sitemap in Chrome after November 17, 2026, and the neat table with clickable URLs is gone. In its place you get Chrome's raw XML tree and a short notice saying the document "cannot be formatted as intended". Nothing is broken for search engines. But if you have ever sent a client to their sitemap to show them what Google sees, the view is about to change, and plenty of people will assume something went wrong.
This article explains what Chrome is removing, what it means for WordPress sitemaps, what the core team and SEO plugins are doing about it, and what I decided for my own sites.
What Changes on November 17
Chrome 158, scheduled for stable release on November 17, 2026, turns off XSLT for everyone except sites in Chrome's deprecation trial and organizations that enable it by enterprise policy. The official announcement lists exactly what goes:
The
XSLTProcessorJavaScript API.The XSLT processing instruction, the
<?xml-stylesheet type="text/xsl" ...?>line at the top of a styled sitemap.
What stays: XML itself, and the same processing instruction when it points to a CSS stylesheet with type="text/css".
After the change, opening an XSL-styled sitemap shows Chrome's built-in XML viewer, with a warning banner explaining that the page uses XSLT and pointing to browser extensions that can restore the view. It is a plain view of the data, not an error page.
If you open your sitemap with the developer console open today, you have probably already seen the run-up: Chrome has logged deprecation warnings for XSLT since late 2025.
Why Chrome Is Doing This
Chrome's XSLT support is built on libxslt, an old C library that the Chrome team describes as "susceptible to memory safety vulnerabilities like buffer overflows". It receives far less maintenance and security scrutiny than core browser components. Meanwhile, Chrome measures XSLT use at around 0.02 percent of page loads. A rarely used feature with a long history of security bugs is an easy candidate for removal.
Firefox and Safari have not set dates. Mozilla is positive about removing XSLT but has not set a date for turning it off by default, and WebKit has signalled it would probably wait for another browser to go first. Chrome on iPhone and iPad uses WebKit under the hood, so it keeps rendering XSL stylesheets for now.
What Breaks and What Does Not
Search engines are not affected. Google, Bing and other crawlers read the XML in your sitemap, and the stylesheet line is a processing instruction outside the <urlset> or <sitemapindex> element that holds the data. Google has not published a statement about XSL specifically, so this is an inference rather than a quote, but nothing in the sitemap data changes when a browser stops applying the stylesheet. Yoast reached the same conclusion in its own tracking issue: search engines read the XML and ignore the stylesheet.
What you lose is the human view. Clickable links, URL counts, readable dates and image counts all came from the XSL file. Developers barely notice. Site owners who check their sitemap now and then will, and so will clients who were taught that the sitemap is a nice table.
If you want to verify that your sitemap itself is still valid, check the raw XML rather than the styled view. The free Sitemap Validator does that, and the guide to creating an XML sitemap search engines love covers what belongs in it.
What WordPress and the SEO Plugins Are Doing
WordPress core removed the XSL stylesheets from its built-in sitemaps on October 3, 2026. The commit message is short: "For sites including an XSL stylesheet, the display of the XML sitemaps may fail. This removes the stylesheets in favour of allowing browsers to render them as they will." The change is in development for WordPress 7.2, due in early December, and so far has only been committed to trunk, not to the 7.1 branch. Until 7.2 ships, sites on a stable release still serve wp-sitemap.xsl, so from November 17 their sitemaps switch to the raw view in Chrome.
Yoast opened an issue on October 2 to replace its XSL file with a CSS stylesheet. CSS keeps a readable layout but cannot recreate everything XSLT did: links are no longer clickable, the URL count disappears, and dates show as raw timestamps.
At the time of writing, I found no public statement from Rank Math or All in One SEO. If you rely on either, check their changelogs after November 17.
Your Options
Keep the XSL stylesheet. It costs nothing, crawlers ignore it, and browsers without the change keep the styled view. Chrome users get the raw tree with the notice.
Switch to a CSS stylesheet. Chrome users get a styled view again, but a simpler one, without clickable links or counts.
Serve a separate HTML view. Transform the sitemap on the server and offer an HTML page for humans, while the XML stays untouched for crawlers. This is the most work and the best result.
Use the polyfill. Chrome's team maintains an XSLT polyfill that runs XSLT in WebAssembly when the browser no longer does. It is well over a megabyte of JavaScript with embedded WebAssembly and has to be loaded from a script element inside the XML document. I would not put a script into a file whose only real audience is crawlers.
Join the deprecation trial. Chrome offers a trial that keeps XSLT working on your origin until August 2027. It is opt-in: you register your origin and send a token, and since an XML file has no head section, that token would have to travel as an HTTP header. Test it before you rely on it, and remember that it only buys time.
What I Am Doing
For now I am keeping the XSL stylesheet, both on signocore.com and in the sitemaps that Signocore SEO generates. The reasoning is simple: the stylesheet has no effect on how search engines read the sitemap, it still works in Firefox and Safari, and in Chrome the fallback is the raw data, which is exactly what crawlers see anyway. Rewriting a working feature into a weaker CSS version, or adding a megabyte of JavaScript to an XML file, solves a cosmetic problem with real costs.
I will revisit that when Firefox or Safari set a date, because that is when the styled view stops being useful for most people who open a sitemap. Until then, the right move is to tell clients what to expect before they notice it themselves.
The Takeaway
On November 17, styled sitemaps change how they look in Chrome, not what they say. Crawlers never saw the styling in the first place. Check that your sitemap is valid XML, decide whether the human view matters enough to rebuild, and send your clients a two-line heads-up before they open their sitemap and think the site is broken.
