4 Checks That Prove Your Sitemap Still Works in Chrome 158

My sitemap is fine. Yours probably is too. Chrome 158 stopped applying the stylesheet that made the XML look like a table, so from 17 November 2026 anyone opening a WordPress sitemap in that browser sees a page of code instead of a list of links.

Nothing in the file moved. What moved is the browser. I ran four checks on my own sitemap this morning and none of them needed a fix, so here is the short version for the call you are about to get from a client.

What Chrome 158 actually took away

I went on Dan Taylor’s report on Search Engine Journal, published 19 November 2026. Chrome 158 reached most desktop and mobile users from 17 November 2026 and dropped client-side XSLT, which is the language a browser uses to reshape one document into another before showing it to you.

WordPress core and the three big SEO plugins have pointed their sitemaps at an .xsl stylesheet for years. That stylesheet is what draws the table, with the URL and the last modified date in neat columns. The sitemap underneath it is plain XML, one location and one date per post.

The stylesheet was never part of the sitemap

Googlebot fetches the sitemap and reads the location and lastmod entries inside it. It does not open a browser window, and it has never run that stylesheet. Bingbot behaves the same way.

So discovery, crawl paths and rankings did not change on 17 November. This landed while the November core update, which started on 10 November 2026, was still rolling, which is why a raw XML page in the middle of a ranking wobble looked like a cause. It is not one.

I keep the server and plugin work in one place, and a question about a stylesheet belongs in the same pile, so it sits with the other maintenance notes in WordPress Care.

4 checks I ran on my own site this morning

The first check is the URL. My site runs Rank Math, so the sitemap index sits at siddharthvira.com/sitemap_index.xml and answers 200. The WordPress core path, wp-sitemap.xml, answers 301 and redirects to it. Both of those predate Chrome 158, so a redirect there is not new damage.

The second check is the second line of the file. Mine still carries the stylesheet reference, pointing at main-sitemap.xsl. That is the line Chrome now skips, and it is the exact line WordPress 7.2 removes. Seeing it is normal today.

The third check is what the browser itself prints. Mine is on Chrome 156 and already shows a red strip across the top of the sitemap. The strip says the site uses XSLT and that the feature is being removed from this browser very soon. That banner comes from the browser, not from the site.

The fourth check is a second browser. Open the same URL in Firefox or Safari and the table comes back, because both still support XSLT for now. Two windows side by side is the fastest way to show a client that only the styling changed.

Who has fixed it and who has not

WhereWhat it doesStatus
WordPress 7.2Removes the stylesheet reference, so core sitemaps ship as plain XMLPlanned for 8 December 2026
Yoast SEO 28.9Rebuilds the styled view using CSS instead of XSLTAnnounced, no date in the report
Rank Math and All in One SEONo change to the sitemap stylesheetNot announced
Plugin status as reported by Search Engine Journal on 19 November 2026.

What I would tell the client on the phone

Wait for the release. There is nothing on the server to patch, and a small filter to hide the stylesheet only removes a warning from a developer console. If the sitemap has to look clean in a report this week, take the screenshot in Firefox.

The thing actually worth checking is monitoring. Site health tools that scan for browser console errors will start flagging sitemap URLs, and an alert that fires every week on a working file teaches everyone to ignore the next real one. Point that tool away from XML files, or ignore the sitemap URL by name.

One more small thing. Chrome logs a deprecation warning in DevTools every time a page loads an .xsl stylesheet, so a QA pass over the site will now report console noise on URLs nobody changed. I would rather explain that to a client once than have them find it themselves during a core update.

Sources

Dan Taylor’s report on Search Engine Journal, 19 November 2026. WordPress.org release post for 7.1.5, 18 November 2026, for the 8 December date on 7.2.

Also read: 4 Checks Before You Add Noindex to a Page, WordPress 7.2 Ships 1 Bare Default Theme and a 50-Pattern Flagship and Error Establishing a Database Connection: 5 Checks in Order.

Scroll to Top