Website owners do not need to make urgent changes to their WordPress sitemaps following Chrome’s decision to drop support for XSLT. Although XML sitemaps may now look different when opened in the browser, search engines can still access and process them as normal. Google Search Console can be used to confirm that submitted sitemaps are working correctly.

WordPress and several popular SEO plugins, including Yoast SEO, Rank Math and All in One SEO (AIOSEO), have traditionally used an XSL stylesheet to make XML sitemaps easier for people to read.

When someone opened a sitemap in Chrome, the browser used this stylesheet to turn the underlying XML data into a formatted table containing clickable links. This made it easier to browse the URLs included on a website.

However, following the removal of XSLT support in Chrome 158, visitors opening a sitemap may now see unformatted XML code instead. The browser may also display a warning on the page and in its developer console.

This change affects how sitemaps appear to people, rather than how they work for search engines.

Googlebot, Bingbot and other search crawlers do not depend on XSLT to read sitemap files. They access the original XML data and process elements such as <loc> and <lastmod> directly. As a result, the browser change does not affect indexing, crawling or search rankings.

The timing may cause some confusion, particularly as Google’s November core update, which began on 10 November, is still rolling out. Website owners and clients carrying out routine ranking checks may mistake the unfamiliar sitemap display for a technical problem.

How to Check Which Sitemap Your Website Uses

WordPress websites generally use one of two main sitemap addresses, depending on their configuration and whether an SEO plugin controls the sitemap.

  • WordPress Core Sitemap: yourdomain.com/wp-sitemap.xml. This is the standard address when a third-party SEO plugin has not replaced the default sitemap.
  • SEO Plugin Sitemap: yourdomain.com/sitemap_index.xml for plugins such as Yoast SEO, Rank Math and AIOSEO. Some websites may use yourdomain.com/sitemap.xml, which redirects to the sitemap index.

Opening either address in Chrome 158 or a later version may show a page of XML tags instead of the familiar formatted table. This indicates that the browser is no longer applying the XSLT stylesheet. It does not mean the sitemap is damaged or unavailable.

How to Check Sitemap Status in Google Search Console

Website owners can use Google Search Console to confirm that Google is still reading their XML sitemap correctly. This is also a useful way to reassure clients who are concerned about the change.

Follow these steps:

  1. Sign in to Google Search Console and select the relevant website property.
  2. Open Indexing > Sitemaps from the navigation menu.
  3. Find the submitted sitemap in the table and check its status.

A green Success status indicates that Google has processed the sitemap without reporting an error. The table also shows when Google last read it and how many URLs were discovered.

If the sitemap is marked as successful, there is no reason to assume that Chrome’s display change has affected Google’s ability to read it.

WordPress and SEO Plugin Updates

The response to Chrome’s XSLT removal varies between WordPress and the major SEO plugins.

Provider or plugin XSLT status and planned changes Impact
WordPress Core Current versions include XSLT styling. WordPress 7.2, scheduled for release on 8 December, is expected to remove the core XSLT stylesheet. No SEO impact. Sitemaps may appear as raw XML in Chrome until the update is released.
Yoast SEO Version 28.9 is planned to replace XSLT with CSS styling. As of 17 November, version 28.9 had reached RC5, while 28.8 remained the stable release. The formatted sitemap view should return once version 28.9 becomes generally available.
Rank Math The team confirmed through its support channels on 4 November that the issue affects the visual presentation of sitemaps only. Its latest changelog did not list a replacement stylesheet. No SEO impact. Chrome displays the raw XML instead of a formatted table.
AIOSEO The plugin continues to use XSLT-styled sitemaps, with no announced plans for an alternative stylesheet. Crawling and indexing continue as usual, despite the change in browser display.

What Does This Mean for Website Owners?

No Impact on Rankings or Indexing

XML sitemaps are primarily designed to help search engines discover website URLs. Crawlers read the underlying XML structure, including the <urlset> and <sitemapindex> elements, rather than relying on how a browser presents the information.

Removing XSLT therefore does not affect URL discovery, crawl efficiency or search visibility. There is no need to change sitemap settings simply because Chrome now displays the file differently.

More Questions From Clients During the Core Update

The timing of Chrome 158 may lead to unnecessary concerns among clients and website owners. With Google’s November core update taking place at the same time, some may associate an unfamiliar sitemap display with ranking drops or a technical issue.

SEO teams and account managers should explain that this is an expected browser change, not evidence of a website failure.

Browser Warnings May Affect Website Checks

Chrome’s developer tools can display a deprecation warning when a page attempts to use an XSL stylesheet. Automated website checks and quality assurance tools that monitor browser console messages may also flag sitemap URLs.

These warnings relate to the stylesheet reference rather than an issue with the underlying XML file.

Browsing Sitemaps Becomes Less Convenient

Some editors and marketing teams use sitemap URLs as a quick way to browse a website’s pages. Without the formatted table, this is no longer as straightforward in Chrome.

Users can temporarily switch to browsers such as Firefox or Safari, which continue to support XSLT at the time of writing. Another option is to create a dedicated HTML sitemap that provides a readable list of website pages.

What Should Website Owners Do?

Since search engines do not rely on XSLT, most websites do not need immediate technical changes. The appropriate response will depend on whether the sitemap is used by search engines alone or whether people also need an easy way to browse its contents.

Recommended steps include:

  • Leave existing production sitemaps unchanged. For most websites, the best approach is to keep the current XML sitemap configuration. Wait for WordPress 7.2 or the relevant SEO plugin updates rather than making unnecessary changes.
  • Explain the change to clients and internal teams. Let stakeholders know that seeing raw XML in Chrome is expected and does not indicate a broken sitemap. Google Search Console’s successful status provides a straightforward way to confirm that Google can process the file.
  • Create a separate HTML sitemap if needed. If clients, editors or visitors need a readable directory of website pages, consider creating a dedicated page such as /sitemap/. WordPress blocks such as Page List, Categories and Latest Posts can help display the content without depending on XML stylesheets.
  • Remove the XSLT reference from WordPress Core sitemaps if necessary. Website administrators who want to prevent the deprecated stylesheet from being called can use a small must-use plugin. This is optional and is not required to protect search performance.

For websites using the built-in WordPress sitemap, the following code can be added to a PHP file named disable-sitemap-xsl.php inside the wp-content/mu-plugins/ directory:

<?php

/**

 * Plugin Name: Disable Sitemap XSL

 */

add_filter( ‘wp_sitemaps_stylesheet_url’, ‘__return_false’ );

add_filter( ‘wp_sitemaps_stylesheet_index_url’, ‘__return_false’ );

The first filter removes the stylesheet reference from individual sitemaps, while the second applies to the sitemap index.

The sitemap will still appear as plain XML in Chrome, but the stylesheet warning should no longer appear. This produces the same display outcome expected from WordPress 7.2.

Once the website has been updated to WordPress 7.2, the temporary plugin should be removed. The release is expected to remove the stylesheet and deprecate both filters, meaning the custom plugin will no longer be needed and could generate additional deprecation notices.

What Should You Tell Clients?

The main point to communicate is that Chrome 158 has changed the way XML sitemaps are displayed, not how they function.

Search engines continue to process the original XML data without relying on browser-based stylesheets. Website crawling, indexing and organic rankings are therefore unaffected by the change.

WordPress 7.2 is expected to remove the core stylesheet reference, while Yoast SEO 28.9 plans to use CSS to maintain a formatted sitemap view. Rank Math and AIOSEO have yet to announce equivalent changes.

For now, website owners should avoid unnecessary sitemap fixes and use Google Search Console to check that their submitted files are being read successfully.

 

More Digital Marketing BLOGS here: 

Local SEO 2024 – How To Get More Local Business Calls

3 Strategies To Grow Your Business

Is Google Effective for Lead Generation?

What is SEO and How It Works?

How To Get More Customers On Facebook Without Spending Money

How Do I Get Clients Fast On Facebook?

How Do I Retarget Customers?

How Do You Use Retargeting In Marketing?

How To Get Clients From Facebook Groups

What Is The Best Way To Generate Leads On Facebook?

How Do I Get Leads From A Facebook Group?

>