Chrome 158 drops XSLT: WordPress sitemaps now show as raw XML

Chrome 158 Drops XSLT: WordPress Sitemaps Now Show as Raw XML, Indexing Unaffected

SEONovember 20, 2026
By Antonio Fernandez

TL;DR

  • Google's Chrome 158, scheduled for Stable on 17 November 2026, removes XSLTProcessor and the XSLT processing instruction; CSS stylesheets on XML still work.
  • Google says only about 0.02% of page loads use XSLT, and cites libxslt memory-safety bugs such as CVE-2025-7425 as the reason for removal.
  • An Origin Trial and Enterprise Policy keep XSLT alive until Chrome 176 on 17 August 2027, when it is disabled for every user.
  • WordPress's 7.2 development code deprecates the wp_sitemaps_stylesheet_url filters; make.wordpress.org lists the 7.2 release for 8 December 2026.

Chrome 158, which Google scheduled for Stable release on 17 November 2026, no longer runs XSLT, the stylesheet language that turns XML into a formatted page in the browser. For website owners the visible result is that XML sitemaps styled with an XSL stylesheet, which includes the default sitemaps of WordPress and of several SEO plugins, now open in Chrome as raw XML instead of a clickable table. The sitemap file itself has not changed, and search engine crawlers read the XML, not the styled view, so this is a display change in one browser rather than a crawling or indexing problem.

What Chrome removed in version 158

Google set out the plan on its Chrome for Developers page Removing XSLT for a more secure browser. Two things are going: the XSLTProcessor JavaScript class, and the XSLT processing instruction, the xml-stylesheet line at the top of an XML file that points the browser to an XSLT stylesheet. According to that page, from Chrome 158 XSLT stops functioning on Stable releases for everyone except sites enrolled in an Origin Trial and organisations using an Enterprise Policy.

Chrome is keeping two things that matter here. XML itself is still supported, and so is the xml-stylesheet processing instruction when it points to a CSS stylesheet (type="text/css") rather than an XSL file. That second point is the escape route that some sitemap tools are now taking.

Google gives two reasons on the page. The first is security: Chrome's XSLT support relies on libxslt, an older C and C++ codebase that Google describes as prone to memory-safety bugs, and the page cites CVE-2025-7425 and CVE-2022-22834 as examples. The second is usage: Google says about 0.02% of page loads use XSLT, and fewer than 0.001% use XSLT processing instructions.

The Chrome XSLT removal timeline

The removal was announced well in advance and rolled out in stages. The dates below come from Google's Chrome for Developers deprecation page.

The Chrome XSLT removal timeline
Chrome version and dateWhat happens
Chrome 142, 28 Oct 2025Early-warning console messages
Chrome 143, 2 Dec 2025Official deprecation, with warnings in the console and Lighthouse
Chrome 146, 10 Mar 2026Enterprise Policy available to disable XSLT early or keep it after removal
Chrome 152, 25 Aug 2026Origin Trial available so sites can keep XSLT after removal
Chrome 158, 17 Nov 2026XSLT stops working on Stable, except Origin Trial and Enterprise Policy users
Chrome 176, 17 Aug 2027Origin Trial and Enterprise Policy end; XSLT disabled for all users

So sites have one more escape hatch, the Origin Trial, until August 2027. After Chrome 176 there is no way to keep XSLT running in Chrome. Google's page also says the Firefox (Gecko) and WebKit projects have indicated plans to remove XSLT, so the current situation, where Firefox and Safari still render XSL-styled sitemaps, should not be treated as permanent.

Why WordPress sitemaps now look broken in Chrome

XML sitemaps are written for machines. To make them readable for people who open them in a browser, WordPress core has, since version 5.5, added an xml-stylesheet line that points to an XSL file. The browser used that file to draw the familiar table of URLs with headings and links. Several SEO plugins do something similar for their own sitemap index files.

With XSLT gone, Chrome 158 ignores that instruction and shows the underlying XML: the urlset or sitemapindex wrapper, then each entry with its loc and lastmod values. Search Engine Journal, in an article published on 19 November 2026 on the change, notes that Chrome also logs a deprecation warning in DevTools when a page calls an .xsl stylesheet. For anyone used to the styled table, the plain XML can look like an error. It is not one.

What the WordPress code says

The stable WordPress 7.1 branch still emits an xml-stylesheet instruction of type text/xsl for both the sitemap index and individual sitemaps. In the WordPress development code that will become version 7.2, the sitemap renderer no longer sets up stylesheets. The two filters that controlled the stylesheet URLs, wp_sitemaps_stylesheet_url and wp_sitemaps_stylesheet_index_url, are marked as deprecated in 7.2.0, and the code comment says their output is ignored "following the deprecation of XSLT by browser manufacturers". WordPress's own 7.2 release page on make.wordpress.org lists 8 December 2026 as the release date, after a first release candidate on 17 November. Until a site upgrades, it keeps serving the XSL reference that Chrome now ignores.

Where the SEO plugins stand

Search Engine Journal compiled the status of the main WordPress SEO plugins. Its reporting says Yoast SEO 28.9 replaces XSLT with CSS styling, but that 28.9 was still at release candidate 5 on 17 November, with 28.8 as the stable version. Yoast's own sitemap index on yoast.com, checked on 20 November, already points to a CSS stylesheet. For Rank Math, the article says support channels confirmed on 4 November that the change affects visual display only, and that recent changelogs list no replacement. For All in One SEO, it says the plugin continues to serve XSLT-styled sitemaps and has announced no alternative. Plugin versions move quickly, so check your own plugin's changelog rather than relying on this snapshot.

Crawling, indexing and rankings

The question most site owners will ask is whether this hurts search performance. Based on how sitemaps work, it should not. A sitemap is consumed by crawlers as XML data. Googlebot and Bingbot fetch the file and read the URL entries and dates; they do not render it through a browser's XSLT engine. The stylesheet line has always been a presentation hint for humans, and removing it, or having a browser ignore it, leaves the data the crawler reads exactly as it was.

Search Engine Journal reaches the same conclusion and says indexing, crawl efficiency and rankings are unaffected. To be precise about sourcing: that is the article's reasoning, not a statement from Google Search or Bing. Google's Chrome deprecation page does not mention sitemaps at all. The analysis is still sound, because nothing in the change touches the XML that search engines parse, but it is worth confirming in your own data rather than taking on trust.

What to check on your own site

The fix list is short, and for most sites it means confirming nothing is wrong.

  • Open your sitemap URL in Chrome. On core WordPress this is usually /wp-sitemap.xml; plugin sitemaps often sit at /sitemap_index.xml or /sitemap.xml. If you see XML with your URLs in it, the file is being served correctly and only the styling was skipped.
  • In Google Search Console, go to Indexing, then Sitemaps, and confirm the status reads Success with a recent last-read date and a discovered URL count close to what you expect. This is the check that answers the SEO question.
  • If you use a site audit or QA crawler that flags console errors, expect sitemap URLs to show up with a deprecation warning. Mark them as known and move on.
  • If staff or clients relied on the styled sitemap to browse pages, consider a separate HTML sitemap page built in the block editor. That serves people, while the XML file keeps serving crawlers.
  • Keep WordPress and your SEO plugin updated. The WordPress 7.2 code drops the XSL stylesheet, and plugins that switch to CSS styling will render a readable sitemap in Chrome again.

Search Engine Journal also describes an optional step for sites on core sitemaps that want the warning gone before 7.2: a small must-use plugin that returns false on the wp_sitemaps_stylesheet_url and wp_sitemaps_stylesheet_index_url filters, so WordPress stops printing the XSL line. Because those filters are deprecated in the 7.2 code, any such file should be removed after upgrading. Most sites do not need it, since the warning has no effect on crawling.

Do not change robots.txt, resubmit sitemaps in a panic, or swap sitemap plugins because of the raw XML view. None of those actions fixes anything, and some can create real problems.

Timing with the November core update

Search Engine Journal points out an awkward overlap. Google's November 2026 core update began on 10 November and, according to the article, was still rolling out when Chrome 158 reached users. Site owners watching rankings move may open their sitemap, see raw XML, and link the two. They are unrelated. Ranking changes during a core update come from Google's systems reassessing content, and the sitemap view is a browser display change. Keeping the two apart in reporting will save time.

What the source did not say

Google's deprecation page is written for web developers and never mentions sitemaps, WordPress or SEO plugins. It does not say whether Googlebot uses XSLT (it has no reason to), and it gives no date for Firefox or Safari removal beyond saying those projects have indicated plans. The plugin status above comes from trade reporting and plugin channels, not from Google, and may change within days.

What this means for Thai marketers

Thai business websites built on WordPress with an SEO plugin will show the same raw XML in Chrome, and site owners or marketing staff who open the sitemap may report it as broken. The answer is to check Search Console, confirm the sitemap status is Success, and explain that the raw XML is how the file always looked underneath. If a site has wider technical problems, a proper SEO audit is a better use of time than chasing the sitemap view. For ongoing search work, see RA's SEO services in Thailand, and if a site needs a rebuild or theme work that includes an HTML sitemap page, the web design team can scope it.

Frequently asked questions

Is my WordPress sitemap broken in Chrome 158?

No, the sitemap is not broken; Chrome 158 stopped applying the XSL stylesheet that made it look like a table, so you now see the raw XML. The file, its URLs and its dates are unchanged.

Will the Chrome XSLT removal affect my Google rankings or indexing?

It should not, because search engine crawlers read the sitemap as XML and do not use XSLT. Search Engine Journal says indexing, crawling and rankings are unaffected; Google has not published a statement on sitemaps specifically, so confirm the Success status in Search Console.

Do I have to do anything?

For most sites, no action is needed beyond checking Search Console and keeping WordPress and your SEO plugin updated. The WordPress 7.2 code, due on 8 December 2026, removes the XSL stylesheet from core sitemaps.

Why do Firefox and Safari still show the styled sitemap?

Firefox and Safari still support XSLT for now, but Google's deprecation page says the Gecko and WebKit projects have also indicated plans to remove it. Treat the styled view in those browsers as temporary.

Can I keep XSLT working in Chrome?

Only temporarily, through Chrome's Origin Trial or an Enterprise Policy, and both stop working in Chrome 176 on 17 August 2027. For a sitemap, switching to CSS styling or simply accepting the raw XML view is the practical route.

The short version

Chrome 158 removed XSLT on 17 November 2026, and XSL-styled sitemaps now display as plain XML in Chrome. Search engines read the same file they always did. Check Search Console, update WordPress and your SEO plugin when new versions ship, and keep the raw sitemap view out of any discussion about ranking changes. If you want a second pair of eyes on a site's technical setup, RA's search team can help.

Antonio Fernandez

Antonio Fernandez

Founder and CEO of Relevant Audience. With over 15 years of experience in digital marketing strategy, he leads teams across southeast Asia in delivering exceptional results for clients through performance-focused digital solutions.

Share to:
Copy link:

Read us often? Add Relevant Audience as a preferred source so our articles surface more in your Google results.