If you opened your site's sitemap in Chrome this week, at an address ending in wp-sitemap.xml or sitemap_index.xml, you probably saw a block of tags where a tidy table used to be. The browser changed, not your site. On 17 November 2026 Chrome 158 started reaching most desktop and mobile users, and with it an old technology called XSLT stopped working. XSLT is what turns a data file into a styled page.
Why the table disappeared
A sitemap is a file that lists every page on a site so search engines can find them. It is written in XML, a format meant for machines. WordPress and SEO plugins such as Yoast attach an instruction to that file telling the browser to render the list as a table with columns and links. That instruction is written in XSLT.
According to the Chrome team's deprecation page, from version 158 the stable browser no longer runs it. Two temporary exceptions remain: sites enrolled in an origin trial, and organisations that switched on a dedicated enterprise policy. Both end in Chrome 176, scheduled for 17 August 2027. The sitemap file itself is exactly as it was. Only the way Chrome displays it to a person has changed.
Chrome's own figures put XSLT at roughly 0.02% of page loads, and WordPress sitemaps are one of the few places an ordinary site owner meets it. RSS feeds styled the same way are affected too. Firefox and Safari's WebKit engine have also said they plan to drop XSLT, without a date.
Google reads the list, not the styling
Google reads sitemaps according to the sitemaps protocol, which means the list of URLs inside the file. The styling instruction for browsers is not part of that list, so a raw view in Chrome says nothing about indexing.
The way to confirm it is Google Search Console. Under Indexing, then Sitemaps, each submitted file shows a status and the date Google last read it. If the status is Success and the number of discovered pages looks right, the sitemap is fine. If organic visits have been sliding for a month, the cause lies elsewhere, and the guide on a website that brings no leads is a better place to start.
Yoast and WordPress are removing the styling themselves
Yoast released version 28.9 on 18 November. Its changelog says it removes the stylesheet from XML sitemaps because browsers are dropping XSLT support. After the update the sitemap looks raw in every browser, by design.
WordPress 7.2, whose first release candidate came out on 17 November, is scheduled for 8 December, and the plan is for it to drop the stylesheet from the built-in sitemap as well. Rank Math and AIOSEO had not listed a fix in their changelogs at the time of writing.
Leave the file, update the plugin
Leave the sitemap file alone. Deleting it or changing settings to "fix" the display can damage what Google reads, while the display itself has no effect on Google. If someone else maintains your site, a one-line message explaining that Chrome changed how the sitemap looks can save them an afternoon of debugging.
While you are in the dashboard, update Yoast to 28.9 and use the same screen to confirm the WordPress 7.1.5 security release is installed. For a business in Israel, or anywhere, that wants customers to see a readable list of pages, an ordinary HTML sitemap page linking the key sections does the job and does not depend on any browser feature.