Does Chrome's XSLT removal hurt your WordPress sitemap's SEO?

What does Google read in a WordPress sitemap?

The XML itself: the loc address of each page and, if it is accurate, its lastmod date. Google’s sitemap documentation says that it ignores priority and changefreq, and that it uses lastmod only when the date is consistently and verifiably accurate. None of this depends on a stylesheet. Your server sends the same file whether Chrome applies the stylesheet or not.

Chrome stops applying XSL stylesheets from version 158, on 17 November 2026. The full XSLT removal schedule covers the two exceptions, the origin trial and the enterprise policy, which both end in August 2027.

Our guide to finding a WordPress sitemap shows where WordPress, Yoast SEO and Rank Math publish theirs, and how to read a sitemap index.

What does the XSL file in a WordPress sitemap do?

It turns the XML into a page that people can read, with a title, a short explanation and a table of links. WordPress core has shipped these stylesheets since version 5.5, according to its announcement. The file asks for its stylesheet in a processing instruction near the top. These are the first three lines of the sitemap index of a WordPress 7.1.3 test site, with the test address replaced by example.com:

<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" href="https://example.com/wp-sitemap-index.xsl" ?>
<sitemapindex xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">

The sitemaps listed in the index point to /wp-sitemap.xsl in the same way. WordPress builds these addresses from the site’s home URL, as its code reference shows. Yoast SEO, whose index is at /sitemap_index.xml, also links its sitemaps to an XSL file, according to its developer specification. For any other plugin, look at the source of the sitemap: a line that starts with <?xml-stylesheet and contains type="text/xsl" means that the file uses XSL.

In every case, the stylesheet is a separate file, and the list of addresses stays in the XML.

What will my sitemap look like in Chrome without XSLT?

Raw XML under a warning, if the sitemap links to an XSL stylesheet. We tested this in Chromium 156 with its XSLT feature turned off, as it will be for most users in Chrome 158. A sitemap linked to an XSL stylesheet showed this line at the top of the page:

“This document cannot be formatted as intended. It uses XSLT, which the browser does not support. You might be able to install a browser extension that allows you to view it.”

The words “install a browser extension” link to a Chrome Web Store search for XSLT Polyfill: this is the warning banner that Chrome’s announcement describes. Below it came the source of the file: the processing instruction, then every url, loc and lastmod element as plain text. The file itself was intact; only the table was gone.

A sitemap with no stylesheet at all gets Chrome’s tree view instead, under the line “This XML file does not appear to have any style information associated with it. The document tree is shown below.” It is not an error, and it will look the same after 17 November. Our guide to opening XML files explains what that message means. A broken file, for example one with an unclosed tag, shows a third message: “This page contains the following errors”, with the line and column where Chrome stopped reading.

None of these messages tells you how Google sees the file.

How do I check that my sitemap is valid and read by Google?

Use the Sitemaps report in Search Console. It shows what Google actually fetched, whatever any browser displays.

1. Open Search Console for your site. According to Google’s help, you need owner permissions on the property to submit a sitemap.
2. Open the Sitemaps report.
3. In the “Add a new sitemap” box, enter the URL of your sitemap index, for example https://example.com/wp-sitemap.xml, or https://example.com/sitemap_index.xml with Yoast SEO or Rank Math. Then click “Submit”.
4. Read the Status column.

The help page defines three statuses. “Success” means that the sitemap was loaded and processed with no errors. “Has errors” means that Google fetched it but found one or more errors; the URLs it could parse are still queued for crawling. “Couldn’t fetch” means that Google could not retrieve the file.

For each file, the report also shows its type (sitemap or sitemap index), the date Google last read it and the number of discovered pages. Compare that number with the number of addresses you expect your sitemap to list.

A file that opens in Chrome can still break the rules. MDN explains that a correct XML document must be well-formed and must also follow the rules set in its schema or DTD; Chrome only checks the first part. For sitemaps, those rules come from the sitemaps protocol, which requires UTF-8 encoding and limits a single sitemap to 50,000 URLs or 50MB uncompressed. Google’s documentation repeats these limits.

Search Console does the work of an XML validator for these rules. Its list of errors includes “Parsing error”, when Google could not parse the XML, often because of an unescaped character in a URL, and “Incorrect namespace”, when the namespace of the root element is missing, wrong or misspelled. These errors affect how Google reads your sitemap; a missing XSL layout does not.

To read the sitemap yourself in Chrome after 17 November, install XSLT Polyfill, the extension that Chrome’s announcement links to. Its Store page says that it applies an XSLT polyfill to all XML documents, so your sitemap gets its table back. XMLNest (on the Chrome Web Store) also shows it as a sitemap table you can filter, sort and export to CSV or JSON. Neither extension changes your site: from 17 November, visitors who have neither installed will see the raw XML.