WordPress sitemaps are about to look broken in Chrome — and search engines will not care. Google's Chrome browser will stop running XSLT on November 17, 2026, when version 158 is scheduled to reach most users. In Chrome, the sitemap built into WordPress and those of several major SEO plugins will lose their table layout, because the styled view depends on XSLT. The story was reported by MACCUS on November 6, drawing on a Chrome for Developers page dated October 29, 2025, titled Removing XSLT for a more secure browser, and on plugin makers' own statements. The key fact, repeated by every plugin maker that has commented: search engines are not affected. They read the XML and ignore the stylesheet.
Only the human-readable view breaks. A sitemap with an XSLT stylesheet renders as a neat table in the browser; without XSLT, Chrome will show the raw XML instead. The sitemap itself — the list of URLs, the last-modified dates, the structure Google reads — is unchanged. A visitor who opens a sitemap in Chrome after November 17 will see something uglier, but a crawler will see exactly what it saw before.
The plugin picture is mixed. Yoast, the company behind the Yoast SEO plugin, noted the issue in a ticket opened on October 2 to track it, and has a CSS stylesheet ready for version 28.9, which is not released yet. By November 6, The SEO Framework was the only one of four major plugins checked to ship a sitemap styled with CSS. Rank Math and All in One SEO still had the XSLT line in the sitemaps of their own websites on November 6. The gap between the plugins is a matter of weeks, not principle — CSS styling replaces XSLT, and the work is underway.
The story reached a wider audience when a banner warning prompted a thread titled This site uses XSLT Warning in Reddit's technical SEO forum on the evening of November 5. Chrome's warning is doing what it is meant to do: alerting site owners that a technology they rely on is going away. The thread is a sign that many owners had not heard about a change announced more than a year earlier — a reminder that browser changes with SEO-adjacent effects deserve attention even when they are announced on a developer blog.
Google's own documentation points the same way. Its page Build and submit a sitemap, updated in July 2026, does not mention stylesheets. It asks for a file in an accepted format, saved in UTF-8, and says submitting a sitemap is merely a hint: Google does not commit to downloading it, crawling it, or exploring the site. The styled view was always a convenience for humans, never part of the contract with search engines.
The practical risk is not to rankings but to perception. A client or a stakeholder who opens a sitemap after November 17 and sees raw XML may conclude something is broken — and the SEO's job will be to explain that nothing is. A short note to clients, sent before the change, is worth more than a reassurance sent after they panic.
The deeper lesson is to separate the human view from the machine view. Sitemaps, robots.txt files and structured data all have a human-readable layer and a machine-readable layer, and the two can change independently. The machine layer is what search engines use; the human layer is what stakeholders judge. Both deserve attention, but they should never be confused — and on November 17, Chrome is about to demonstrate the difference in public.
The episode is also a reminder of how much of the web's infrastructure depends on technologies that are quietly being retired. XSLT was once a standard way to transform XML into readable pages, and its removal from Chrome after more than a year of notice is part of a long cleanup of legacy web features. Most of those cleanups pass unnoticed, because the features they remove were already marginal. This one was noticed only because sitemaps are one of the few places where XSLT is still visible to ordinary site owners. The lesson is to keep an eye on browser deprecation announcements, even when they seem to concern developers rather than SEOs — the next one might touch something your site depends on.
Sources: MACCUS, November 6, 2026, reporting Chrome for Developers (October 29, 2025).
Related reading on this site: election-day-news-clicks-8x-no-ai-overviews, geo-referral-data-misses-buying-decisions, Early-November Google Volatility Hits 9.4 Out of 10 — With No Update Confirmed, ChatGPT Ads Switch to Target Bidding on November 9 — Max Bid Retires January 1, Google AI Mode Now Books Home Services — Angi, Thumbtack, Jobber and Housecall Pro, and Google AI Mode Now Shows Up to Four Ads Under a Single Answer.
Linkbaits helps you create content that earns citations and backlinks. Start with the free tools and build your first linkable asset this week.
Start free trial