Skip to content
Free marketing audit: find out what is holding your site back.

Technical SEO

Chrome Dropped XSLT, So Your Sitemap Looks Broken in the Browser. We Checked 28 Sites to See Who Is Affected

Chrome 158 stopped running XSLT on Nov. 17, 2026, so sitemaps from WordPress, Rank Math, All in One SEO and older Yoast versions now open as raw code with a warning. Search engines never used that styling. Here is who is affected, which plugins have switched, and a script to check your own sitemap.

A laptop showing lines of code in a dark editor beside a coffee mug

Key takeaways

  • Chrome XSLT support ended with Chrome 158, which Google scheduled for its stable release on Nov. 17, 2026, so XML files that rely on an XSLT stylesheet now show as raw code in Chrome.
  • Sitemaps from WordPress core, Rank Math and All in One SEO still point to an XSLT stylesheet, so in Chrome they open with the message "This document cannot be formatted as intended."
  • Search engines read the XML itself, not the styled view, so a sitemap that looks unstyled in Chrome still works for Google and Bing; check the Sitemaps report in Search Console rather than the browser.
  • Of 26 sitemaps we could read on Nov. 19, 2026, 7 still asked for an XSLT stylesheet, including wordpress.org, Kinsta, Search Engine Journal and Moz, and 1 (yoast.com) had already moved to CSS.
  • Yoast SEO 28.9, released Nov. 18, 2026, styles sitemaps with CSS instead of XSLT, and a WordPress core ticket to remove the XSL stylesheet is marked fixed for WordPress 7.2.

Chrome XSLT support is gone: Chrome 158, which Google scheduled for its stable release on Nov. 17, 2026, no longer runs XSLT stylesheets, according to Chrome's deprecation notice. The most visible casualty for site owners is the XML sitemap. The neat table that WordPress and most SEO plugins show when you open sitemap.xml in a browser was drawn by XSLT, and in Chrome it is now a page of raw code under a warning.

Your sitemap is not broken. Google and Bing read the XML, and the XML has not changed. We checked the sitemaps of 28 well-known sites on Nov. 19 to see who is affected, read the plugin source code to see who has already switched, and wrote a short script so you can check your own. Search Engine Journal flagged the sitemap side of this first.

What changed in Chrome?

XSLT is a 1999 language for turning XML into an HTML page. A sitemap asks the browser to use it with one line at the top, a processing instruction such as <?xml-stylesheet type="text/xsl" href="/wp-sitemap.xsl"?>.

Chrome is removing both ways a page can use XSLT, the processing instruction and the XSLTProcessor JavaScript API, for security reasons: Chrome says the library behind it, libxslt, is old C code with a history of serious vulnerabilities. The timeline from Chrome's notice:

  • Chrome 158 (Nov. 17, 2026): XSLT stops working on stable Chrome for everyone except sites in an origin trial and companies using an enterprise policy.
  • Chrome 176 (Aug. 17, 2027): the origin trial and enterprise policy end, and XSLT is off for all users.

Chrome adds that Firefox and WebKit, the engine behind Safari, have also said they plan to remove XSLT. This applies in every country; it is a browser change, not a search change.

What does a sitemap look like now?

We opened Kinsta's sitemap index (made by Yoast SEO, still on the XSLT version) in the Chromium browser in our test setup, which already refuses XSLT. Instead of a styled table, it shows this line at the top, followed by the XML tree:

This document cannot be formatted as intended. It uses XSLT, which the browser does not support.

Every <loc> and <lastmod> is still there and readable. The same happened with wordpress.org's own sitemap.

Does the Chrome XSLT removal hurt SEO?

No. The stylesheet only changes how a person sees the file in a browser. Search engines fetch the XML and read the URLs in it; they never ran the XSLT. Chrome's notice says XML itself is not being removed from the browser, only XSLT.

The right place to check a sitemap is the Sitemaps report in Google Search Console (and Sitemaps in Bing Webmaster Tools): if the status is Success and the discovered URL count looks right, you are fine. If a client or a colleague sends a screenshot of "cannot be formatted as intended," that is the browser, not Google. If Search Console does show an error, our guide to sitemap could not be read covers the real causes.

Who is affected? We checked 28 sites

On Nov. 19, 2026, we read each site's robots.txt, took the first sitemap it lists (or /sitemap.xml), and looked for an xml-stylesheet line. Two sites refused our request (The Guardian and Search Engine Land), so 26 sitemaps were checked.

ResultSites
Still asks for XSLT (7)wordpress.org, rankmath.com, aioseo.com, wpbeginner.com, kinsta.com, searchenginejournal.com, moz.com
Uses a CSS stylesheet (1)yoast.com
No stylesheet, plain XML (18)thesearchpost.com, wpengine.com, techcrunch.com, time.com, variety.com, theverge.com, nytimes.com, bbc.co.uk, seroundtable.com, ahrefs.com, semrush.com, backlinko.com, shopify.com, hubspot.com, wix.com, squarespace.com, cloudflare.com, developers.google.com

The pattern: six of the seven XSLT sitemaps come from WordPress sites or WordPress SEO plugin makers. Big publishers and hosted platforms mostly serve plain XML, and so do we.

Which WordPress plugins have switched to CSS?

A CSS stylesheet can still style an XML file in every browser, so that is where plugins are moving. What we found in each plugin's current code on WordPress.org on Nov. 19:

  • Yoast SEO: version 28.9, released Nov. 18, 2026, points sitemaps at main-sitemap.css with type="text/css"; version 28.8 still used main-sitemap.xsl. Yoast's changelog lists "Styles the XML sitemaps with a CSS stylesheet" under its next version, 29.0, dated Dec. 1, but the 28.9 code already does it. Kinsta and Search Engine Journal still serve the XSL version, which suggests they haven't updated yet.
  • WordPress core sitemaps (wp-sitemap.xml): the current release, 7.1.5, still uses XSLT. Trac ticket #65593, "Sitemaps: Remove the XSL stylesheet," is closed as fixed with the 7.2 milestone, so the change is due in WordPress 7.2.
  • Rank Math (1.0.282) and All in One SEO (5.0.5.1): both still ship an XSL stylesheet, and their own sites' sitemaps still use one.

What to do this week

  1. Nothing urgent for SEO. Don't delete your sitemap, switch plugins or install a "sitemap fix" because of how it looks in Chrome.
  2. Confirm in Search Console that each sitemap shows Success. That is the only check that matters for indexing.
  3. Update your SEO plugin as updates arrive. On Yoast, 28.9 already serves the CSS version.
  4. Tell your team and clients before they find it themselves. One sentence covers it: the browser stopped styling the file, Google still reads it.
  5. Check other XML you publish. Styled RSS feeds and any XML a customer opens in a browser (product feeds, reports) may rely on XSLT too. Chrome's notice lists ways to migrate, including doing the transformation on the server.

A script to check your own sitemap

This Node.js script (version 18 or later, no packages needed) reads a site's robots.txt, fetches the first sitemap it lists, and reports whether that sitemap asks for an XSLT stylesheet. It is the script we ran for the table above.

// check-sitemap-xslt.mjs
// Usage: node check-sitemap-xslt.mjs example.com another.com
const UA = 'Mozilla/5.0 (compatible; SitemapXSLTCheck/1.0)';
 
async function get(url) {
  const r = await fetch(url, {
    headers: { 'user-agent': UA },
    redirect: 'follow',
    signal: AbortSignal.timeout(20000),
  });
  return { status: r.status, text: await r.text() };
}
 
for (const site of process.argv.slice(2)) {
  let sitemap = `https://${site}/sitemap.xml`;
  try {
    const robots = await get(`https://${site}/robots.txt`);
    const m = robots.text.match(/^\s*sitemap:\s*(\S+)/im);
    if (m) sitemap = m[1];
  } catch {}
  try {
    const s = await get(sitemap);
    const pi = s.text.slice(0, 2000)
      .match(/<\?xml-stylesheet[^>]*href=["']([^"']+)["'][^>]*\?>/i);
    const isSitemap = /<(urlset|sitemapindex)\b/i.test(s.text.slice(0, 5000));
    console.log([site, sitemap, s.status,
      isSitemap ? 'sitemap' : 'not-a-sitemap',
      pi ? `stylesheet: ${pi[1]}` : 'no stylesheet'].join('\t'));
  } catch (e) {
    console.log([site, sitemap, 'error', e.cause?.code || e.name].join('\t'));
  }
}

An .xsl file in the stylesheet column means Chrome now shows that sitemap unstyled. A .css file or "no stylesheet" means nothing changes. The script only checks the first sitemap in robots.txt; child sitemaps from the same plugin use the same stylesheet.

What we don't know yet

  • When Rank Math and All in One SEO will switch. Neither has announced a change that we could find.
  • The release date of WordPress 7.2. The core fix is marked for 7.2; until then, wp-sitemap.xml keeps its XSLT line.
  • How Safari and Firefox will time it. Chrome says both engines plan to remove XSLT, but we found no dates.

Sources

Photo of Kiran Dasgupta

About the author

Kiran Dasgupta, Editor

Kiran runs Kihan Marketing, a web design, SEO and ads agency, and manages dozens of websites across real estate, home services and healthcare. He writes about SEO, AI search and paid ads news, and what it means for the people who run websites.