Skip to main content

Chrome 158 reached stable on 17 November, and client-side XSLT is now gone for everyone who is not covered by an Origin Trial token or an Enterprise Policy. In October we probed 174 Irish domains and simulated the removal with a feature flag. This week we downloaded the real Chrome 158, pointed it at the Irish web again, and checked who had done anything about it in the meantime.

Almost nobody had. What did change came from a plugin vendor, not from site owners, and it changed in a way that turns a cosmetic sitemap stylesheet into a public version number.

TL;DR

  • We re-probed 183 Irish domains on 22 November 2026. 38 still serve an <?xml-stylesheet?> XSLT instruction, and none of the 38 sends the Origin Trial header that would keep it working.
  • In real Chrome 158, 0 of 37 measurable sites transform. 31 fall back to Chrome’s raw XML viewer and 6 render a completely blank page, including the Data Protection Commission, the National Library and ComReg.
  • All 8 blank documents carry <xhtml:link hreflang> alternates and no other document went blank, which confirms the mechanism we predicted in October.
  • Yoast SEO 28.9 (18 November) quietly dropped its XSLT stylesheet. Every Yoast site still serving main-sitemap.xsl is therefore on 28.8 or older, a version from before 28.9’s fix for private post content leaking through REST endpoints.
  • All In One SEO, Squirrly SEO, Drupal’s simple_sitemap and WordPress core (until 7.2) still emit XSLT in their latest releases. If you run one of those, no released update fixes it for you yet.

What we measured

The corpus was 183 Irish domains: commercial sites, regulators, local authorities, universities, charities and our own four properties. For each we read robots.txt, tried eleven conventional sitemap and feed paths, followed one level into sitemap indexes, and recorded every XSLT instruction and its response headers.

142 domains answered, 125 served at least one XML document, and 38 ship an XSLT instruction. We then rendered all 72 distinct affected documents in Chrome for Testing 158.0.8127.36, the same build as current stable. As a control, we rendered the same documents again with XSLT forcibly re-enabled; 97 of 105 page loads transformed, so the pipeline works and the failures are Chrome’s, not ours. The exceptions were dcu.ie, too slow to load with XSLT on, and comreg.ie, covered in the caveats.

Nobody took the escape hatch

Google offered a way out: an Origin Trial keeps XSLT working on a registered origin until Chrome 176 in August 2027. A sitemap has no <head> for a meta tag, so the token must arrive as an Origin-Trial HTTP header.

Zero of the 38 send one. For a sitemap, doing nothing is defensible, since crawlers never read the stylesheet. But it should be a choice, and October showed most of these sites never saw the warning.

The blank page is no longer a prediction

In October we showed, with synthetic files on localhost, that documents containing <xhtml:link hreflang> elements render as an empty white page rather than Chrome’s XML viewer once XSLT is off. Real Chrome 158 now confirms it on the live web: all 8 documents in the corpus that carry XHTML alternates render blank, and none of the other 64 do.

Six domains serve at least one of those blank documents: dataprotection.ie, nli.ie, qqi.ie, galwaycity.ie, comreg.ie and creativeireland.gov.ie. All six are public bodies. Four carry Irish-language alternates; QQI and Creative Ireland emit English-only hreflang tags, which is enough to trigger it. The other 31 sites show Chrome’s message, “This document cannot be formatted as intended”, followed by a suggestion to install a browser extension. Not advice a public body wants to give.

The October list, five weeks on

We named eight sites in October whose own templates swallowed Chrome’s on-page deprecation warning: the Data Protection Commission, HIQA, the National Library, Sport Ireland, the ESRI, Dublin City Council, the University of Limerick and the Irish Cancer Society. All eight still ship the stylesheet. This run also turned up four more public bodies on the same Drupal module: Fingal County Council, Galway City Council, Limerick City and County Council and QQI.

Two October stories did resolve. dcu.ie’s 17,162-URL sitemap, which would not load with XSLT on, now opens in under eight seconds. And barnardos.ie, which was already broken in October because its stylesheet pointed at a different host from its sitemap, is now clean. The cross-origin bug was never fixed directly. Barnardos updated Yoast, and the stylesheet went with it.

Yoast fixed it for you, and now your stylesheet is a version number

Yoast SEO 28.9 shipped on 18 November, the day after Chrome 158. Under “Other” in its changelog: “Removes the stylesheet from the XML sitemaps as browsers drop XSLT support.” We downloaded 28.8 and 28.9 from wordpress.org and diffed the renderer. 28.8 emits type="text/xsl" pointing at main-sitemap.xsl. 28.9 emits no stylesheet at all, with a source comment saying it was “removed temporarily, to be restored in a future release”. The development branch shows what replaces it: version 29.0, dated 1 December, styles sitemaps with plain CSS, which Chrome still supports.

That has a consequence nobody announced. Yoast’s sitemap is public, and the stylesheet line is in its first 200 bytes. If it still references main-sitemap.xsl, the site is running Yoast 28.8 or older. The same 28.9 release also carried this fix: “Fixes a bug where the head REST endpoints exposed the content of private posts and pages to visitors who could not read them.”

In our corpus, 23 sites expose a Yoast version. The seven on 28.9 ship no stylesheet. Of the 15 Yoast sites still serving XSLT, 14 also print their version in the page source, and every one is between 25.1 and 28.8, which corroborates the fingerprint. Two are on releases from May and September 2025. We are not naming them; a four-day lag is normal. The point is that anyone can now read your patch status from /sitemap_index.xml, and that this arrived silently through a browser change.

Everyone else is still waiting on you

Yoast is the exception. We checked the latest release of every other generator in the corpus:

  • All in One SEO 5.0.5.1 (13 November) still writes type="text/xsl". chambers.ie runs that exact version and serves it today.
  • Squirrly SEO 14.2.12 (20 November) still writes it whenever its sitemap styling option is on.
  • Drupal simple_sitemap 4.2.3, the current release, ships with xsl: true as the install default. Thirteen of the 38 sites run it, and it is behind four of the six blank-page sites.
  • WordPress core drops its sitemap stylesheets in 7.2 (“Stylesheets are no longer supported”), but 7.2 is still at release candidate 2. Every live 7.1 site using core sitemaps still emits them.

By generator, the 38 break down as Yoast 15, simple_sitemap 13, All in One SEO 2, WordPress core 2, Squirrly 2, SmartCrawl 1 and three we could not identify. For the 23 that do not run Yoast, no released update removes it today. Someone has to change a setting.

We are still on the list, and a correction

reptile.haus and blog.satosh.ie both run Squirrly and both still serve the stylesheet. praguers.com runs WordPress core sitemaps and does too. All three now show Chrome’s XML viewer rather than a blank page, because none carries hreflang alternates.

We also owe a correction. In October we wrote that blog.satosh.ie did not ship the instruction. It did: the Wayback Machine has it in a capture from 12 October. This time our first pass also missed isme.ie and chambers.ie, whose stylesheet URLs contain a query string our pattern choked on. Spot-checking known names caught it. A probe that quietly undercounts looks exactly like good news.

What to do this week

Start with one line: curl -s https://yoursite.ie/sitemap.xml | head -c 300. If you see xml-stylesheet type="text/xsl", then:

  • Yoast: update to 28.9 or later. That removes the stylesheet and picks up the REST fix in one step.
  • WordPress core sitemaps on 7.1 or earlier: two filters remove it (7.2 ignores them and needs nothing).
    add_filter( 'wp_sitemaps_stylesheet_url', '__return_false' );
    add_filter( 'wp_sitemaps_stylesheet_index_url', '__return_false' );
  • Drupal simple_sitemap: turn off the XSL styling option in the module’s settings, or set xsl: false in simple_sitemap.settings and export your config. If you publish hreflang alternates, this is the difference between a blank page and a readable one.
  • Squirrly and All in One SEO: disable sitemap styling in the plugin settings, then re-check the live output. Caching layers will happily keep serving the old header.
  • XSLTProcessor in application code: this is what actually breaks products. Move the transform server-side, where XSLT is unaffected, or register for the Origin Trial, remembering that XML responses need the header.

Method and caveats

Single-vantage measurements from 22 November 2026. 41 of 183 domains refused us or timed out, so 38 is a floor. olympics.ie served a bot challenge and is excluded from the render figures. comreg.ie’s stylesheet sits behind a WAF JavaScript challenge, so it failed even with XSLT re-enabled; a returning visitor with the challenge cookie may have fared better before 17 November. Yoast versions come from the plugin’s own HTML comment.

REPTILEHAUS builds and maintains WordPress, Drupal and custom platforms, and an output-first audit like this is how we start every takeover. If you want it run across your estate, or would rather someone else kept the plugins current, get in touch.

📷 Photo by Pict4life on Unsplash